libtool devel auto-import broken

[Stephano Mariani]

Isn't it better to have this functionality within libtool... doesn't it
exist for this purpose? Personally, I would love a tool that allows me
to build shared libs on windows/cygwin, linux, and solaris with ease.

Stephano Mariani

> -----Original Message-----
> From: Robert Collins [mailto:robert.collins@itdomain.com.au]
> Sent: Sunday, 17 March 2002 10:19 AM
> To: Stephano Mariani; Charles Wilson
> Cc: CygWin-Apps
> Subject: RE: libtool devel auto-import broken
> 
> 
> 
> > -----Original Message-----
> > From: Stephano Mariani [mailto:sk.mail@btinternet.com]
> > Sent: Sunday, March 17, 2002 9:12 PM
> > To: 'Charles Wilson'; Robert Collins
> > Cc: 'CygWin-Apps'
> > Subject: RE: libtool devel auto-import broken
> >
> >
> > I would like to test these new versions of the autotools if I
> > may. I am a very autotools dependent user and use it
> > frequently enough to warrant dissecting it and learning much
> > more about their internals :)
> >
> > I have noticed however that using automake (1.5) and libtool
> > (1.4e) there is no way to prevent symbols being exported. I
> > have therefore had to resort to patching my binutils to
> > prevent every symbol from being exported :(
> 
> There is a bin-utils export-filter command you can use instead of
> patching IIRC. Mind you, we resorted to patching binutils to get
libtool
> to do what we want :].
> 
> Rob