On 23. 12. 2015 7:51, Andrew Lowe wrote: > This thingy I'm setting up will contain the latest gcc & llvm amongst > other things. In doing this, I've had reason to look in the mingw64/bin > dir. The sizes of executables surprised me. I have: > > clang.exe > clang++.exe > clang.cl.exe > > all at 37MB. A lot of the other llvm apps are also monsters. In comparison: > > c++.exe > g++.exe > x86_64-w64-mingw32-c++.exe > x86_64-w64-mingw32-g++.exe > etc etc for the gcc compiler > > all come in at about 1.85MB. > > Have the clang apps been built with debug info "on" or is this how it's > meant to be? Has llvm been statically linked whereas gcc is using dll's ???
Stripping didn't make the executables smaller, so it's not debug symbols. According to ntldd, there is no clang.dll or similar loaded into the executables, so they're probably (mostly) statically linked. I remember there were some problems with building the DLL in the past. Not sure if it's still an issue, but it may just be that no-one switched the build process to make the DLL yet. > Also, while I have people's attention, I don't need all of these clangs > and gcc's do I? The doco the students will be using will explicitly say > "clang" and "gcc". Can I just delete the others or will this confuse the > packages manager? If you're really only running gcc and clang directly (not through autotools or complex makefiles), it should be okay to delete the other clones (clang++, g++, the prefixed ones...). This only applies to the contents of bin/ though. Deleting stuff from lib/ or libexec/ is not a good idea. Maybe I'm wrong and someone corrects me, but hopefully I'm not. -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
