Hi Philip, I'm not a Windows developer so I can only take a stab at the build problem. My guess is that you've built only the static targets of Producer, but osgconv is attempting to link against the dynamic one, or something similar.
The range of the build options while helping a wide range of users, does make it more difficult to manage, or more precisely VS just isn't geared up to managing a large number of separate projects and targets. I would like to see the build easier to set up and configurable but this will probably take a new build system to make it possible. Robert. On 11/19/06, Philip Taylor <[EMAIL PROTECTED]> wrote:
Would someone please enlighten me with the Windows OSG build philosophy. The core OSG builds just fine as do several other DLLs, bur other fial because the required DLL has not been built. For example, Application osgconv fails to build because it lacks Producerd.lib. When I look at Producer, I find that it has in fact built Producerd_s.lib. (This is not an attack on Producer, give the recent Producer postings. but just an example that has occurred now that I try to build a CVS download dated 23 Oct 2006.) It maybe that this issue has been completely resolved and that a CVS refresh will fix my problem. I can fix my build problem, but I keep seeing reports of successful builds straight from the CVS, so am I missing something really basic? My build environment is WinXP SP2 (Home) with VS 2005 Express. PhilT _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
