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
Message-ID:	<20000913134359.8676.qmail@web118.yahoomail.com>
Date:	Wed, 13 Sep 2000 06:43:59 -0700 (PDT)
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Subject:	Re: libtool
To:	Robert Collins <robert DOT collins AT itdomain DOT com DOT au>, cygwin AT sources DOT redhat DOT com
MIME-Version:	1.0

--- Robert Collins <robert DOT collins AT itdomain DOT com DOT au> wrote:
> ----- Original Message -----
> From: "Chris Faylor" <cgf AT cygnus DOT com>
> To: <cygwin AT sources DOT redhat DOT com>
> Sent: Friday, September 08, 2000 8:14 AM
> Subject: Re: libtool
> 
> 
> > On Fri, Sep 08, 2000 at 08:02:46AM +1100, Robert Collins wrote:
> > >I played around last night... pity I don't know dlls that well :-]
> > >
> > >1) the ltdll.c header seems unneeded with current gcc
> >
> >gcc -shared -g -O2 -Wall,--enable-auto-image-base,--out-imp-lib=.libs/libna
> m
> > >e.dll.a -o .libs/libname.dll -export-dynamic a.lo b.lo c.lo
> > >
> > >built a dll quite happily from standard sources except there were no
> > >exports...
> > >I presume that's what the sed and DLLTOOL scripts in the current libtool
> are
> > >all about? generating a .def file to explicitly list the exports?
> > >
> > >2) the .def files format was broken
> > >-> I haven't looked at this yet
> > >
> > >3) the .def file had many un-related symbols pulled via dlltool and sed.
> > >(i.e. printf as an export from glib...)
> > >I'm kicking around using NM and searching for T entries in the .lo files
> > >rather than libtool --export-all
> > >
> > >comments anyone?
> >
> > What about 'D' entries?
> 
> Thank you.. I've realised I probably asking the wrong question...
> 
> is there an existing tool that will pull the following symbols from a
> collection of .lo files:
> * explicitly _declspec(dllexport) symbols
> * any symbols that could be linked to the .lo files if they were collected
> into a static library. (phrased badly I know)
> currently libtool uses dlltool --export-all -z mydeffile.def a.lo b.lo ...
> d.lo where the .lo files are what will be linked to created the .dll
> 
> the symbols are used to created import and export .def files so that the .h
> files do not need to explicitly use declspec(dllimport) etc.
> 
> if there is no existing tool... can anyone recommend documentation that
> might help me specify what said tool needs to do to get only those symbols?
> there are T (haven't looked at D yet) symbols that are part of core system
> libraries (to pick two of them T _malloc or T _strcmp). I don't think glib
> (my test libtooled library overrides those function itself).
> 

Anders Norlander had created a pexports process that would create the .def from
the supplied headers and the .dll.  Is there a link to this at http://sources.redhat.com/cygwin/?

=====
--- <http://earniesystems.safeshopper.com> ---
   Earnie Boyd: <mailto:earnie_boyd AT yahoo DOT com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://gw32.freeyellow.com/>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -