Hi All,
Marcus Lindblom wrote:
> Johannes Brunen wrote:
>
>> Hello Dirk,
>>
>> I would also go for a clear self explaining naming scheme.
>>
>> However, I'm a little puzzeled about the variants you are going to build on
>> default. Normally, I use the following variants:
>>
>> DEBUG -> /MDd /Od
>> DEBUG_OPTIMIZED -> /MDd /O2
>> RELEASE -> /MD /O2
>>
>> This gives me the opportunity to debug OpenSG (DEBUG) or to use full
>> optimized code (DEGUG_OPTIMIZED) when I'm not actively interested in
>> debugging the OpenSG details.
>>
>> Isn't generally linking debug runtime (/MDd) together with release runtime
>> (/MD) problematic and should be avoided?
>>
>> I do not understand the advantage of using the /MD runtime instead of the
>> (correct) /MDd runtime. I'm not expecting a great performance penalty in
>> this case.
>>
>
> The point was to use your app in release mode, but being able to debug
> OpenSG without rebuilding anything. It's the other way around. :)
>
Actually my understanding was that we wanted to be able to use external
libraries that might only be available in release mode (like EXR or TIFF).
The app has the same problem with those libs, you have to link to the
release runtime to use them, even if you want to debug your program.
> Hence my suggestion for naming the /MD /Od build RELEASE_NOOPT.
>
Now I see how you came up with that one. ;)
Dirk
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
