Re: [Mingw-w64-public] static libgcc in multiple shared libraries

2015-04-01 Thread Yaron Keren
Hi, Having different libgcc copies used from different parts of your program may be a big problem or not, depending upon how it is used in your program. Different libgccs do not share data, so C++ exceptions will not work between different libgccs. Your C program may not care for exceptions but dy

Re: [Mingw-w64-public] static libgcc in multiple shared libraries

2015-04-01 Thread Greg Jung
My 2c, which is not authoritative but perhaps can throw a few more topics into the mix. First remember this: there are compiler-specific versions of libstdc++, incompatible but nevertheless named the same, dependent upon the exception method deployed by the compiler. AFAIK the only way to force a

[Mingw-w64-public] static libgcc in multiple shared libraries

2015-03-31 Thread Cosmin Apreutesei
Hi, I'm looking for the best way to distribute binaries for a main exe and several C and C++ plugins separately and I have a few questions about linking libgcc and libstdc++. Currently, the main exe (a C program) is linked with static-libgcc. Several C libraries that are loaded via LoadLibrary()