Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-20 Thread Dizzy
On Monday 19 November 2007 21:39:45 Stephen Collyer wrote: FIND_PATH(CURL_INCLUDE_DIR NAMES curl/curl.h) i.e. it hard-codes the assumption that curl.h lives in a directory called curl. In my case, it doesn't: it lives in a directory called include and no amount of adding to or subtracting

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-20 Thread Dizzy
On Monday 19 November 2007 16:00:17 Mike Jackson wrote: Actually I run into this ALL the time (tiff, expat, hdf5) and I have most of mine stored in non-Standard locations. I end up copying the the FindXXX.cmake into my local project directory and then adding some code like the following:

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-20 Thread Brandon Van Every
On Nov 20, 2007 4:34 AM, Dizzy [EMAIL PROTECTED] wrote: Yes, that is bad practice IMO. FIND_PATH() should look just for the file in some default locations it is known to be on many platforms (including registry settings on Windows if there are install packages that installs and registers

[CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Stephen Collyer
This would seem to be a very frequently asked question but I can't find it anywhere in the wiki or FAQ: how do I tell FIND_PACKAGE to search on additional paths to the default set, so I can work with packages installed in non-standard locations ? -- Regards Steve Collyer Netspinner Ltd

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread David Cole
What is wrong with explicitly specifying the non-standard locations up front so that FIND_PACKAGE has nothing to do? In other words, prime all the relevant cache variables with the non-standard locations. There are many Find* scripts in the CMake Modules directory. I think it would be difficult

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Stephen Collyer
David Cole wrote: What is wrong with explicitly specifying the non-standard locations up front so that FIND_PACKAGE has nothing to do? You assume that I considered it all. In fact, I'm far too clueless about cmake to have done that. In other words, prime all the relevant cache variables with

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread David Cole
So for the specific case you ask about, FindCURL.cmake, you would set the following advanced variables during ccmake / CMakeSetup configure through the cmake GUI:CURL_INCLUDE_DIR CURL_LIBRARY Then, with those set, the next FIND_PACKAGE(CURL) will find CURL because you've told it exactly where it

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Mike Jackson
Actually I run into this ALL the time (tiff, expat, hdf5) and I have most of mine stored in non-Standard locations. I end up copying the the FindXXX.cmake into my local project directory and then adding some code like the following: SET(EXPAT_INCLUDE_SEARCH_DIRS

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Christian Ehrlicher
Mike Jackson schrieb: Actually I run into this ALL the time (tiff, expat, hdf5) and I have most of mine stored in non-Standard locations. I end up copying the the FindXXX.cmake into my local project directory and then adding some code like the following: SET(EXPAT_INCLUDE_SEARCH_DIRS

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Brandon Van Every
On Nov 19, 2007 9:00 AM, Mike Jackson [EMAIL PROTECTED] wrote: The important part is that I am looking for an environment variable to help find the paths/libraries. This type of thing could be added the the FindXXX.cmake files so if someone has their libs installed in non-standard locations

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Alexander Neundorf
On Monday 19 November 2007, Christian Ehrlicher wrote: Mike Jackson schrieb: Actually I run into this ALL the time (tiff, expat, hdf5) and I have most of mine stored in non-Standard locations. I end up copying the the FindXXX.cmake into my local project directory and then adding some code

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Stephen Collyer
David Cole wrote: So for the specific case you ask about, FindCURL.cmake, you would set the following advanced variables during ccmake / CMakeSetup configure through the cmake GUI:CURL_INCLUDE_DIR CURL_LIBRARY Then, with those set, the next FIND_PACKAGE(CURL) will find CURL because you've

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Andreas Pakulat
On 19.11.07 19:39:45, Stephen Collyer wrote: David Cole wrote: So for the specific case you ask about, FindCURL.cmake, you would set the following advanced variables during ccmake / CMakeSetup configure through the cmake GUI:CURL_INCLUDE_DIR CURL_LIBRARY Then, with those set, the

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Brandon Van Every
On Nov 19, 2007 2:39 PM, Stephen Collyer [EMAIL PROTECTED] wrote: FIND_PATH(CURL_INCLUDE_DIR NAMES curl/curl.h) i.e. it hard-codes the assumption that curl.h lives in a directory called curl. In my case, it doesn't: it lives in a directory called include and no amount of adding to or

Re: [CMake] Add search paths for FIND_PACKAGE ?

2007-11-19 Thread Stephen Collyer
Andreas Pakulat wrote: On 19.11.07 19:39:45, Stephen Collyer wrote: I guess that solves the problem, but it seems like a hack, rather than a solution. It seems to me that the problem is that FindCURL.make does this: FIND_PATH(CURL_INCLUDE_DIR NAMES curl/curl.h) i.e. it hard-codes the