Hi,

On Tue, 2009-06-30 at 09:19 +0200, Johannes Brunen wrote:
> Hello Gerrit,
> 
> "Gerrit Vo" <vo...@vossg.org> schrieb im 
> Newsbeitrag news:1246336792.3319.14.ca...@feynman.camtech.ntu.edu.sg...
> >
> > short question. what are the correct windows debug define settings or
> > if this is not well defined, which are the once you expect to be set ?
> >
> > Debug        -> -D _DEBUG
> > DebugOpt     -> ? never used it, does it need -D _DEBUG or -D NDEBUG ?
> > ReleaseNoOpt -> ? So far I did not use -D NDEBUG or -D _DEBUG and that
> >                  seem to work
> > Releae       -> -D NDEBUG
> >
> imho the following settings would be the way to go:
> 
> Debug                 -> /D_DEBUG   /Od  /Ob0   /RTC1 /MDd   /Zi 
> /PDB:"c:\path\to\the\dll\dir\dllname.pdb"
> DebugOpt           -> /DNDEBUG  /O2  /Ob2               /MDd   /Zi 
> /PDB:"c:\path\to\the\dll\dir\dllname.pdb"
> Release               -> /DNDEBUG  /O2  /Ob2               /MD     /Zi 
> /PDB:"c:\path\to\the\dll\dir\dllname.pdb"
> ReleaseNoOpt    -> /D_DEBUG   /Od  /Ob0   /RTC1 /MD     /Zi 
> /PDB:"c:\path\to\the\dll\dir\dllname.pdb"
> 
> Marcus, could you please verify that. I'm unsure with respect to the 
> ReleaseNoOpt configuration, because this one is new for me. Additionally, I 
> did never generate debug database files on release builds. Actuallly, I 
> didn't know that this is possible until recently. At last I'm not completely 
> confident about the inline optimization /Ob2 against its counterpart /Ob1. 
> Which one is recommendable on the microsoft compiler platform?

ok, I did the changes, could you check if they make sense for you. 
Small warning of which you most likely are aware, you have to start
with a blank/empty cache to get these changes pulled in correctly as
the compiler settings are manipulated only once in the very beginning.

I also updated the boost handling so the cmake file should respect 
Boost_USE_STATIC_LIBS as set. Another small warning I stumbled across,
the std cmake boost find mechanism only react to these settings 
(static + mt) the very first time, once Boost has been found changing
these flags/options does not change which boost libraries are used. 
So you have to delete/clean the cache to get changes in.

PDB file are generated for all targets but I made the install optional
(OSG_INSTALL_PDB_FILES). I also added an option
(OSG_USE_SEPARATE_LIBDIRS) so you can choose  where the libs are placed
during the install, the general lib dir or a target specific subdir. I
still keep both .lib and .dll files in the lib dir, windows seems more
to tend to install the .dll file in the bin dir. Would you prefer the
bin dir or is the lib dir ok ?

If you have anything else let me know. One open issue is custom
compiler flags. 

I'm also not sure all the 3rd party libs are handled correctly for
all variants. I'll try to check this but it will take a second as
windows builds are so slow ;( And I have to build the 3rd party 
lib variants ;(

kind regards,
 gerrit




------------------------------------------------------------------------------
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to