U++ forum: Welcome to the forum

Re: shared libraries for debug, static for release ? [message #10228 is a reply to message #10223]

Tue, 26 June 2007 09:47

mirek
Messages: 14265
Registered: November 2005

Ultimate Member

pvozenilek wrote on Mon, 25 June 2007 18:19

"OTOH, you mention MSVC 7.1., which is to our knowledge the optimal compiler/linker for most of C++ stuff. With incremental linker it posses, there is a little need (except the extremely large applications, more than 2 milions of lines of C++) to use shared libraries just to speedup the build process."

Boost is the largest hog - a 1 MLOC translation unit is nothing uncommon. I do include *.cpp files into single TU (which I think Blitz does) to combat with this.

Yes, BLITZ does this ".cpp merging" automatically.

Quote:

DMC has a wrapper named cl.exe which translates MSVC options and calls dmc.exe. DMC preprocessor was fixed some half an year ago and is able to deal with Boost.Preprocessor, which is more than most other preprocessors. DMC is still not able to deal with the most tricky templates in Boost but for less ambitious projects it should be (the 8.50 beta) OK as is.

Thank you for the info, perhaps it is the time to check again...

Mirek

Report message to a moderator