Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » shared libraries for debug, static for release ?
Re: shared libraries for debug, static for release ? [message #10223 is a reply to message #10220] Tue, 26 June 2007 00:19 Go to previous messageGo to previous message
pvozenilek is currently offline  pvozenilek
Messages: 14
Registered: June 2007
Promising Member
"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.



"If I remember well Digital Mars has MSVC compatibility mode via some switch. My interest about this compiler dropped at the moment when I have found it has not even achieved C preprocessor compatibility (unable to interpret some of U++ macros)."

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.
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Mixing C and C++ files (windows with MinGW compiler)
Next Topic: Linking with usb library
Goto Forum:
  


Current Time: Tue Jul 15 23:32:42 CEST 2025

Total time taken to generate the page: 0.03448 seconds