Re: MSW DLLs support in libtool

[Evgeny Grin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11.02.2016 2:38, Bob Friesenhahn wrote:
> On Wed, 10 Feb 2016, Evgeny Grin wrote:
>> As result - "-no-undefined" is used only on W32 without any practical
>> benefit: if lib have some undefined symbols, it will not be build on W32
>> as shared lib regardless of "-no-undefined" flag. And conditionally used
> 
> The "-no-undefined" option is not actually Win32 specific.  IBM's AIX
> has build configurations which benefit from it.
OK. So porting something to AIX will result in conditional
"-no-undefined" for AIX too. But again, why we need to signal this for
libtool on W32? Is it required only for automatic fallback to static
instead of shared?

> Also, "-no-undefined" does not indicate if the library has undefined
> symbols (many DLLs have undefined symbols).  It indicates that the build
> configuration has agreed to supply any additional dependency libraries
> if there otherwise would be undefined symbols.

On W32 this looks like "-no-missing-headers" for precompile/compile
mode. Linker will fail anyway if some symbol is not resolved.

Is it required for automatic fallback to static? Even if so, isn't it
better to try to link at first and fallback to static only if linker failed?
I'm not talking currently about reasonability of such fallback.

- -- 
Best Wishes,
Evgeny Grin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWvGgAAAoJEL96xKXqwrr0MbwIAMGM7TcWamoel1hG/aAXiz//
ImZRpcw4cwRpmJnh0j7V3Zw8nkpoaMZcXRSmql+7xlDpLu++Scv55TTFckKcYU8V
90GlqtmcbHLsU4DGyqtwlEG0ah4kopsQUrQlfyZ2+LiSx/8a7yiEn/5YOQRmMsOU
wN7f2Va2m2HTesMG+E2rNzrEMVyWaiRII62sjLXvVXDyap3/7LENybC69ru3LkrE
Qkq9l3e61aci0/pES13Y/lmylPzYMoQYDbGkthdnLWKa+W3Byt9hRKeGr+SyCXX6
r8r0saBnQp5H57Ma5IAKFNAMIMVPbb7SRJM2LEa/uUQ4eDe1aOVl4bvLIzXPTRU=
=84n8
-----END PGP SIGNATURE-----