Hi,
First good news: the Visual C++ Toolkit compiler plugin in C::B seems to work with Visual .NET 2003. I guess it would work with any version of Visual C++. That's why I think the compiler plugin may be renamed to Visual C++
During visual imports corrections, I added some options to the compiler plugin:
- a missing /Od for no optimization (debug), set by default by cl.exe.
- a bunch of options for runtime libraries linking: /MT /MTd /MD /MDd /ML /MLd (see
http://msdn.microsoft.com/library/fre/default.asp?url=/library/FRE/vccore/html/_core_.2f.MD.2c_2f.ML.2c_2f.MT.2c_2f.LD.asp) which are fundamental with Visual C++ to avoid conflicts between libraries which are compiled with different options.
However I know some of the runtime libraries are missing in the Visual Toolkit/Platform SDK: those corresponding to /MDd /MD and /MTd when we include STL (libcp*.lib msvcp*.lib conterparts). Seems that they are not downloadable separatly for free. So I don't know how to set correctly the options either in the visual importer or in the msvc compiler plugin.
- It would be could to be able to use different version of Visual C++ for extensibility purpose, so I would not modify the new options of the msvc compiler plugin
- But we may provide a way to disable the options when libraries are missing, maybe in the compiler detection ??
I cannot send the patch for the compiler plugin or the visual imports before tonight, sorry!
What is you opinion about my problem ? What should I do with those options ?