Andreas Zieringer wrote:
> Hi,
>
>   
>> Hi,
>>
>>     
>>> I guess the answer to Windows users is to use the DebugRT build instead 
>>> of Debug, and just move all the libs to the "/lib" dir... even though I 
>>> dislike having to diverge from the "official standard".
>>>       
>> the difference for debug and debugrt is that debug does not require your
>> support libs to use the debug crt. And this can be quite important if
>> for example you have third party stuff that does not come with proper
>> dbg libs. Also it saves you the pain from building support-libs twice.
>>     
> yes using the debug crt is really painfull and sometimes not possible 
> because of third party libs. I actually compile my apps fully optimized 
> but with debug information in extra pdb files. So I don't need to switch 
> any libs as I can debug my release version.
>   
The point of the debug libs on windows is that you can get better memory 
tracking (find leaks and bad handling, as it allocates barriers and fill 
allocated/deallocated/destructed memory with various patterns, such as 
0xcdcdcdcd, 0xfeeefee, etc.)

It's a good thing to have when you need it, trust me, but I do agree 
that having non-optimized opensg linked to release runtime is a very 
good thing too, especially for developers that don't want or simply 
can't build debug-runtime versions of their thirdparty libs.

Cheers,
/Marcus

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core

Reply via email to