You should be able to set the variables to be "internal" cache variables
after-the-fact - see
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#section_Properties%20on%20Cache%20Entries
That would at least keep them entirely out of the gui, even in advanced
mode.
Ryan
On Thu, Mar 4, 2010 at 4:
I ended up writing my own macro to do the job:
http://code.google.com/p/soupcon/source/browse/trunk/findxul/FMP.cmake
there's also some usage example in my FindXUL module:
http://code.google.com/p/soupcon/source/browse/trunk/findxul/FindXUL.cmake
That's a bit more complex than what I described as
On 3. Mar, 2010, at 11:33 , Guillaume Duhamel wrote:
> Hi,
>
> I'm working on a new FindXXX module and I need to search for paths
> providing multiple header files, for instance path P1 could provide
> A.h and B.h while not providing C.h when path P2 provides the three of them.
> In this case, I
Hi,
I'm working on a new FindXXX module and I need to search for paths
providing multiple header files, for instance path P1 could provide
A.h and B.h while not providing C.h when path P2 provides the three of them.
In this case, I want to detect P2 only.
Does CMake has some built-in functions or
