Hi, I am following GCC 4.3 development and mingw and it seems that some improvments are being made that could benefit cegcc. One think I don't like with actual cegcc-mingw32ce is the fact that when you compile a C++ program, you get a huge binary because of the fact mingw is statically linked with libstdc++.Even if you use strip to reduce size , to me it's a hack and not a real solution
Things may change with new GCC 4.3.1 as you can see on the following URLS : 1) http://www.mingw.org/MinGWiki/index.php/GccStatus : # Shared libgcc: If all modules are linked with -shared-libgcc, exceptions can be thrown across DLL boundaries. # Shared libstdc++: Add -lstdc++_s to your link flags to link against a DLL version of libstdc++. # Zero cost exceptions: New exception model Dwarf only has performance penalty when being thrown. The old model, SJLJ, is no longer available. # Thread local storage support: The __thread keyword is honoured. # Improved debugging information: Dwarf-2 debugging is now the default 2)http://gcc.gnu.org/wiki/WindowsGCCImprovementsGSoC2008 I don't know how things will evolved and what is the status of "Windows GCC Improvments" but it will be interesting in a few months to try to generate a cegcc 4.3.1 and to offer possibility to use a shared version of libstdc++. Vincent R. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
