Hi J-S, Great then!
But will there be a problem in MSVC when building the "package-XYZ" target? I mean if you build it in release, that's easy to say it depends on the release build for binaries (ALL_BUILD target for instance), but how can you say it also depends on the debug builds of the same targets? As far as I know, it is impossible to do that under MSVC. So maybe we'll be forced to have separate debug and release packages... and what about those who build "MinSizeRel" or "RelWithDbgInfo" targets? Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ Le Wed, 17 Dec 2008 03:41:18 +0100, Jean-Sébastien Guay <[email protected]> a écrit: > 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 _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
