[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libmicrohttpd] W32: remove dependency on libgcc dll with latest GCC
From: |
LRN |
Subject: |
Re: [libmicrohttpd] W32: remove dependency on libgcc dll with latest GCC |
Date: |
Wed, 16 Apr 2014 04:38:26 +0400 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0a1 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 15.04.2014 19:00, Evgeny Grin wrote:
> 15.04.2014, 18:53, "LRN" <address@hidden>:
>> How about making static libgcc linking optional
>> (W32_SHARED_LIB_EXP is true basically always for W32 builds, as
>> all its prerequisites are available)? And/or maybe separate
>> static libgcc linking into separate option.
> libgcc contains only internal routines and only 3 of them are used.
> Libs on Win32 are distributed usually in binary form and with
> libgcc dll this dll must be distributed with lib dll. Don't see any
> real reason for making it dynamic Did I miss something?
>
Whether to link statically or dynamically is packager's choice. Don't
take it away just because *you* think static linkage is OK. If static
linking makes a lot of sense, make libmicrohttpd *default* to linking
libgcc statically, and require --enable-shared-libgcc configure option
to override that.
- --
O< ascii ribbon - stop html email! - www.asciiribbon.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
iQEcBAEBAgAGBQJTTdECAAoJEOs4Jb6SI2CwWbsH/0HuvZRkct5eQs471WASlCDf
HxJZcPCa696TYJZWt9J4XGuBCILHc8y3zBkUtlow6NYoxzCgBshiQ5ZRD54DnxKR
Fymvga7Csrh46XxjtyE/gJb6JQz9Ea57GVh1mJCFFSive63n4dVrFVY+HW7Ki9QY
kRg/mWe2zQvpS35NtiGylXPlzhizV5mQScFhGRIe7FOtHtgaQDG1q18dzFvFSqSm
aY/8hwNn4MNffUjxeSkiUCbMiv/qIRHKYSTsCt1LnM+nYcUP/zrdK+kiTeCi58TG
+sbBsXU3w47l3qop7KKXF5/PxRjdJVdiEvD8xMn4yFOOwawOuiY6HshdxpN5FHE=
=8uBl
-----END PGP SIGNATURE-----