Hi Sukender,
When I build packages in debug config (VC8 SP1), I got the releases binaries
into them... did I miss something?
I hadn't tested this yet, thanks for beating me to it :-)
It should be possible to create both debug and release packages,
especially on Windows. Even if users don't want to debug into OSG from
their applications, with Visual Studio, linking a debug application to a
release library can (will) cause problems, so we really need to provide
both packages.
Perhaps the -dev packages should contain the debug DLLs + libs in
addition to the release libs and headers? Since only developers will
need the debug DLLs, and theoretically all developers will need them, I
don't see why they should be a separate package. It will just make it
easier to make the mistake of linking the release libs to a debug
application if the user just downloaded that and "didn't see" the debug
libs package...
Moreover, should not pakages mention if they are debug/release? Such as
"libopenthreads-2.7.7-win32-x86-vc80sp1-debug.tar.gz"?
I was going to suggest adding debug/release to the names too.
J-S
--
______________________________________________________
Jean-Sebastien Guay [email protected]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
