From: Earnie B. <ea...@us...> - 2008-08-15 12:21:26
|
Quoting Brian Dessent <br...@de...>: > fo...@sm... wrote: > >> 1) With mingw I think that when you compile a C++ application, you are >> statically linked with libstdc++, is it still true ? >> If yes what are the reasons ... > > The default is still static libstdc++ but you can link to shared > libstdc++ in the 4.2 and later MinGW gcc versions with -lstdc++_s (and > sometimes -D_DLL, see release notes.) The reason is simple: people have > come to expect MinGW to produce standalone executables that don't > require third party runtime DLLs. > >> 2) There were also limitations about exception not passing Dll boundaries, >> still true ? > > This was not true in the past and not true now. MinGW gcc 3.x contained > a patch that allowed it to work with static libgcc. With gcc 4.x that > patch no longer exists, but it's still possible to support this with > -shared-libgcc. > > Brian > Brian, do you have time to review the documentation at www.mingw.org for gcc/g++/library use and update what is wrong/out of date? Earnie |