Hi,

I've been compiling OpenSG 1.8 a couple of times now, and found a few 
small issues that I think could be improved:

Use -O in the scons.bat file? (optimize python code)

OpenSG now compiles _with_ WIN32_LEAN_AND_MEAN defined. Previously it 
"had" to be there to support htonl() (which is in winsock2.h, so you 
could have used that instead). That might cut down on compile times a 
little bit.

Using /Zi instead of /Z7 works and produces smaller obj files. This puts 
intermediate debuginfo in a vc70.idb/pdb file in the cvs root dir. On 
link, it creates per-target pdb-files as usual. It seems to be working 
even though debug/release builds use the same intermediate files.

Always using /DEBUG as link flag (to create debug). There's really no 
need for the dbgopt version, as the outputted files are pretty 
equivalent (by ignoring the PDB's, dbgopt is equivalent to opt)

Change /FORCE:MULTIPLE (not needed) to /INCREMENTAL:NO (needed due to an 
internal linker limit being reached by OSGSystem).

Always define OSG_DEBUG_FCPTR for debug-versions? It doesn't impact perf 
that much and is a great help. Add check to make sure client & lib is 
compiled with same source?

...

We should still plan on how to adress the larger compile/link time 
issues, but I think the above makes life a bit easier anyway.

Cheers
/Marcus



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to