| Thanks to everyone who helped out on this..
After a few re-installs and concentrated efforts applying everyone's advice I got it to work... So thanks, once again.. It turns out VS05 is not that dissimilar to XCode once you get into it..
My next task was to try and create my own app, or get ported apps to work.. That was relatively painless...
But in the process of trying to solve some problems I found this post in the mailing list.. I think it might be of help to others whohave been asking similar questions to me recently.. so I am quoting and linking to it here..
May I suggest that this info is appended to the 'Getting Started' info for OSG on PCs.
You need to open the project properties, open the linker options and:
- in the General tab, in Additional Library Directories, type the path to
the path where OSG puts the .lib files Mustafa mentioned earlier ( e.g.
z:\path\to\OpenSceneGraph\lib )
- in the Input tab, in Additional Dependencies, type the names of the
libraries you need to link against. Typically, those will be osg.lib,
osgDB.lib, osgUtil.lib and osgProducer.lib . Also, you can use the debug
libs when running your app in the Debug configuration (those have a trailing
d in their name just before the .lib: osgd.lib, osgDBd.lib and so on) You will also need to set the include path so that your project finds the
OSG headers. This happens in the project properties, C++ tab, in General:
set the Additional Include Directories to contain the path to the include
folder of the OSG distribution ( e.g. z:\path\to\OpenSceneGraph\include) Projects in the OSG solution from the distribution have a relative path
(../../include) to the headers and a "dependency" on the core projects. It
means that if a project is taken out of the solution, it can still find the
headers if it is in the same directory relative to the rest of the OSG, but
the dependency is broken. Hence your linking errors. Visual Studio's
dependencies are just another way of specifying the libraries a project
depends upon within a solution, that's why when creating a separate solution
you are to specify manually the import libs. As an alternative to setting the Additional Include/Libraries Directories in
the project properties, you can set them up for your whole Visual Studio
environment (not for this project only). This happens in
Tools/Options/Projects tab/VC++ directories, add your paths to the
appropriate categories. You would still have to list the libraries in the
Additional Dependencies field of the Linker/Input tab.
Kind regards, Stephen. | 