Dirk Reiners wrote: > Hi All, > > Marcus Lindblom wrote: >> Johannes Brunen wrote: >> >>> 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).
I was thinking about an earlier discussion when you talked about simply chaning LD_LIBRARY_PATH and get debuggable libs instead. > 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. Ok. Thats a good reason too. :) >> Hence my suggestion for naming the /MD /Od build RELEASE_NOOPT. >> > Now I see how you came up with that one. ;) Yup. Most (if not all) windows developers usually connect Release & Debug to different runtime libs, not whether it has debug symbols (which should always be present, IMO) and/or is optimized (which is nice to have variations of to better read call stacks and variables). 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 _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
