Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Apparently-From: <earnie?boyd AT yahoo DOT com>
Message-ID: <3AB4E4A4.8ED61ACE@yahoo.com>
Date: Sun, 18 Mar 2001 11:39:00 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: Earnie Boyd <cygwin AT cygwin DOT com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
CC: nate AT rootlabs DOT com, cygwin AT cygwin DOT com
Subject: Re: Building non-cygwin DLL with cyg-gcc
References: <20010318064139 DOT 88232 DOT qmail AT rootlabs DOT com> <3AB463ED DOT FF93B53F AT ece DOT gatech DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Charles S. Wilson" wrote:
> 
> nate AT rootlabs DOT com wrote:
> [snip]
> > And of course, this makes sense because ld seems to be trying to export all
> > symbols.  I have my own .def file with the desired exports listed, but I can't
> > figure out how to get ld to use it.  It seems like ld has no equivalent of
> > the --def switch of dlltool (shown in the UG method).
> >
> > Is it possible to get ld to reference an exports file using the ML method?  If
> > not, what's the recommended method for building a non-cygwin DLL using cyg gcc?
> 
> just put the .def file in with the list of .o's to be included in the
> dll.
> 
> > BTW, I still can't figure out the difference between mingw, w32api, and
> > -mno-cygwin.  I assume they're all different pieces of the same codebase.
> 
> w32api is the place where Win32-specific #include files are stored.
> Cygwin puts them there to keep the separate from the 'cygwin' #include
> files.  These files are used by cygwin gcc, cygwin-gcc with -mno-cygwin
> switch, and by mingw gcc (although the mingw distro puts them somewhere
> else).
> 
> -mno-cygwin turns the cygwin gcc into a cross-compiler,
> host=i686-pc-cygwin and target=i686-pc-win32.
> 

Just a few nit-picks.  Change the win32 to mingw32, that's what the
target is.

> mingw is a totally native version of gcc for win32.  Not even gcc.exe
> from the mings distro depends on cygwin1.dll.  Thus, host=i686-pc-win32
> and target=i686-pc-win32.
> 

Again change the win32 to mingw32.  I'm nit-picking because that's what
autoconfiguration expects.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple