[osg-users] CMake Search Paths ?
Hi, This may be an issues with the developers of cmake but I've had a difficult experience building OSG 2.2 official release on IRIX 6.5 using the cmake build process. Problems namely with specifying my own /include /lib paths. it seems to want to ignore any arguments I pass to it , I don't think Cmake even reads the PATH env variable . To solve this I've had to hard code the paths in CMakeCache and CmakeLists.txt and other areas in order for OSG to build with the headers and libs I want. Even using the SET command in CmakeLists.txt doesn't seem to fix the problem. It seems to me that Cmake has a set of hardcoded directories that it will search. Is there a simpler way to give cmake user defined search paths? Other modules I had to alter to make cmake search the directories I specify: In CmakeModules/ for all search paths: FIND_LIB /usr/nekoware/lib /usr/freeware/lib64 FIND_INCLUDE /usr/nekoware/include /usr/freeware/include /src/osgPlugins/jpeg/CMakeFiles/osgdb_jpeg.dir added: /usr/nekoware/lib/libjpeg.so I also wonder if cmake builds osg on 64 bit platforms in 64 bit? or does it build in 32 bit? How can you tell or know what cmake is doing? Regards Paul IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] CMake Search Paths ?
There are a bunch of ways to deal with this. You shouldn't modify the CMakeCache directly. And you really shouldn't need to modify the CMakeLists.txt. 1) Use the ccmake instead of cmake. It exists for this very reason and is the easiest, most reliable answer. (I constantly beg people to use this so we don't get these kinds of questions over and over.) 2) Define the CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH environmental variables. See the CMake documentation, but essentially: export CMAKE_LIBRARY_PATH=/usr/nekoware/lib 3) Define the OSGDIR environmental variable or OSG_ROOT environmental variable. This is something we put in, though I'm not sure if it is consistently applied everywhere yet. 4) Not recommended, but still better than editing the CMakeCache (but not by much), use the cmake -D := switch to explicitly set values. See the CMake documentation. -Eric On 11/19/07, Paul Pocock <[EMAIL PROTECTED]> wrote: > Hi, This may be an issues with the developers of cmake but I've had a > difficult experience building OSG 2.2 official release on IRIX 6.5 using > the cmake build process. Problems namely with specifying my > own /include /lib paths. > > it seems to want to ignore any arguments I pass to it , I don't think > Cmake even reads the PATH env variable . To solve this I've had to hard > code the paths in CMakeCache and CmakeLists.txt and other areas in > order for OSG to build with the headers and libs I want. Even using the > SET command in CmakeLists.txt doesn't seem to fix the problem. It seems > to me that Cmake has a set of hardcoded directories that it will search. > > Is there a simpler way to give cmake user defined search paths? > > > Other modules I had to alter to make cmake search the directories I > specify: > > In CmakeModules/ for all search paths: > > FIND_LIB /usr/nekoware/lib > > /usr/freeware/lib64 > > FIND_INCLUDE /usr/nekoware/include > > /usr/freeware/include > > /src/osgPlugins/jpeg/CMakeFiles/osgdb_jpeg.dir > > added: /usr/nekoware/lib/libjpeg.so > > > I also wonder if cmake builds osg on 64 bit platforms in 64 bit? or does > it build in 32 bit? How can you tell or know what cmake is doing? > > Regards > > Paul > > > > IMPORTANT: This email remains the property of the Australian Defence > Organisation and is subject to the jurisdiction of section 70 of the CRIMES > ACT 1914. If you have received this email in error, you are requested to > contact the sender and delete the email. > > > ___ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] CMake Search Paths ?
Hi Eric, "E. Wing" wrote: > 1) Use the ccmake instead of cmake. It exists for this very reason and > is the easiest, most reliable answer. (I constantly beg people to use > this so we don't get these kinds of questions over and over.) Well, this is the old story we've already had before the 2.0 release: I guess quite a lot of people build stuff like OSG as part of a batch or at least using a predefined script. If you disallow these people to modify the required flags on the 'cmake' command line, then you force all these people to create their very private hack and it's no surprise that people ask why they have to do so . So, telling people about the shiny world of 'ccmake' and begging for procedures that are _highly_impractical_ on many people's setup is one thing, getting things with command line flags _really_ sorted out isn't a bad option either. I'm very curious to know if the solutions, which you've been proposing here, actually did the job. Cheerio, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] CMake Search Paths ?
>> Is there a simpler way to give cmake user defined search paths? > So, telling people about the shiny world of 'ccmake' and begging for > procedures that are _highly_impractical_ on many people's setup is one > thing, This strikes me as a newbie-like question, not an automation (advanced) question so ccmake is a perfectly reasonable answer. That's the reason for the tool's existence. > If you disallow these people to modify the required flags on the 'cmake' > command line, Nobody disallowed anything. I also gave 3 other perfectly good answers that are geared towards automation and command lines. -Eric ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org