RE: libtool devel package still dll crippled.

["Ralf Habacker" <Ralf dot Habacker at freenet dot de>]

> > From: Robert Collins
> > Sent: Sunday, April 14, 2002 9:43 AM
>
> > > Again, the "...=" came from you, Rob.  So, what's the
> > > difference between
> > > "...=" and "...=no" or "...=unsupported" (or
> "...=yes", for that
> > > matter).  And which do we want/need?
> >
> > We want "...=". In both locations.
> >
> > I'll test the always_export_symbols settings
> now and send
> > another email when that build is done.
>
> I think we should leave the always_export_symbols
> as yes, but I'm not
> religious.
>
> Ralf, whats the reason to change that to no?
>
> I get better results with it set to yes, which is
> why I am asking..
>
I had recgonized problems with the
allow_undefined_flag=unsupported and have tried only with
"no", which works. Yet I have tried with "yes" it works too.
So its no problem for me to use "yes".

  _LT_AC_TAGVAR(always_export_symbols, $1)=yes

Using "yes" causes libtool to use nm to generate a symbol
list, which is avoided by setting to "no".

/usr/local/bin/nm -B  .libs/profiler.o  | sed -n -e
*[     ]\([ABCDGISTW][ABCDGISTW]*\)[   ][      ]*\(_\)\([_A-
Za-z][_A-Za-z0-9]*\)$/\
1 \2\3 \3/p' | sed 's/.* //' | sort | uniq >
.libs/libprofiler.exp

In small projects this may be no difference, but if you have
to build hundrets of dll's with thousands of symbols this
makes a difference in linking time.

Does the cygwin ld really need this way of creating symbol
lists ?

Ralf