Hello Roger,
Keep in mind I didn't design the CMake project files, so I'm writing
from my own understanding of things. But for me it has all been pretty
straightforward.
So if I understand correctly the new CMake build system requires that I have
to have a a duplicate set of OSG specific static libraries, include files,
and dynamic link libraries in order for things to work.
I have always used the includes and libs from the 3rdParty zip file,
even before the change to CMake, when building OSG. It's not related
to the build system change. On the other hand, perhaps setting
include/lib directories for dependencies was "easier" (read: we didn't
have to learn a new way of doing it) with the old build system, and
now since the build system has changed, it has to be done in another
way...
Using the 3rdParty zip file is easier, but if you want to use your own
versions of these dependencies, look at the file
CMakeModules/Find3rdPartyDependencies.cmake to see if you can't
specify an alternate path for the dependencies. If it's possible, it's
always better to use environment variables or "-D" command-line
arguments to CMake, but you could also modify the file itself so it
finds your includes/libs. If you do, and the change is general enough,
please submit it back to be merged.
Good luck,
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://whitestar02.webhop.org/
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
