On Fri, May 30, 2008 at 1:59 PM, Jason Daly <[EMAIL PROTECTED]> wrote:
> Robert Osfield wrote: > >> The new code is in OpenSceneGraph/CMakeLists.txt is: >> >> #use pkg-config to find various modues >> FIND_PACKAGE(PkgConfig) >> >> IF(PKG_CONFIG_FOUND) >> ... >> >> > > Yes, as I said, that code is in the version I have. Yeah sorry about that, that's completely my bad. I copied that CMake code from somewhere in a project and clearly it was never tested in that project and I wasn't thinking when I submitted that code. It doesn't fix the problem because there is no FindPkgConfig.cmake file shipped with CMake < 2.4.7 so it results in yet another error. The posted workaround of checking the version number will work fine, alternatively one could replace FIND_PACKAGE(PkgConfig) with INCLUDE(FindPkgConfig OPTIONAL) Which eliminates the error message (and I have verified this on CMake 2.4.6 =) ) > As for the statement "Red Hat Enterprise 5 won't be able to generate >> Makefiles", I think this is rather overblown. First up there is >> nothing stopping you downloading and installing a more up to date >> version of CMake. >> > > I could easily do that on one workstation, yes. It's more of an issue when > you're dealing with a lab of several dozen workstations. This is why we pay > to run Red Hat Enterprise. > > > You can even not bother installing it and just set >> your PATH/LD_LIBRARY_PATH to pick up on a local install. >> >> > > pkg-config is in my path, what else do I need to do? What Robert is getting at here is you can download a newer version of CMake from their website, add the "bin" directory to the front of your PATH and simply start configuring new builds with that newer version of CMake instead. There is no need to set your LD_LIBRARY_PATH because CMake is statically linked. There is no reason to fear screwing up old build directories configured with CMake 2.4.x since CMake stores the absolute path to it's own binary on an initial configuration of a build tree. Provided you don't remove the old version of CMake none of your old build trees need to be regenerated and you can start using new builds with the new CMake. Incidentally, CMake has no requirement to be in your PATH either. At the moment since I'm in between versions I've actually removed CMake from my path and I specify the version I want explicitly since not all of my projects have been ported to work under CMake 2.6.x. ~/cmake-2.4.8-linux-i386/bin/cmake . ~/cmake-2.6.0-linux-i386/bin/cmake . etc. To edit cache, use "make edit_cache" not "ccmake ." -- Philip Lowman
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
