15.04.2014, 18:53, "LRN" <[email protected]>: > 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?
Best Wishes, Evgeny
