Hello Marcus, Ok, I understand. But then it is desirable that the DEBUG_OPTIMIZED variant is added too. This one is typically used (at least by me) for application development.
Regards, Johannes "Marcus Lindblom" <[email protected]> schrieb im Newsbeitrag news:[email protected]... > > > 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. :) > > Hence my suggestion for naming the /MD /Od build RELEASE_NOOPT. > > Cheers, > /Marcus > > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
