<div class="gmail_quote">On Fri, Jan 30, 2009 at 12:08 AM, Tyler Roscoe <span dir="ltr"><<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'll spend some more time reading FindQt4.cmake at work tomorrow, but I<br>
wanted to post this while I'm thinking about it.<br>
<br>
I would like to tell find_package where my third-party libraries are (Qt<br>
specifically). Since I know where the libraries are, I could manually<br>
add paths to INCLUDE_DIRS and LINK_LIBRARIES, but FindQt4 already knows<br>
how to do all of that so why duplicate the effort?<br>
<br>
This is for an internal build system, so I want to use a specific<br>
version of Qt installed on a networked filesystem to prevent any<br>
weirdness caused by a developer compiling against some random Qt that<br>
she might have on her dev machine.<br>
<br>
This seems like a common situation, so surely there's a CMake way to<br>
handle it? I was hoping the PATHS parameter would do what I want but<br>
it's for specifying the path to the FindXXX modules.</blockquote><div><br>Read the documentation for the find_path() and find_library() commands. Setting the variable CMAKE_PREFIX_PATH (or environment variable) will likely be of tremendous help to you.<br>
</div></div><br>-- <br>Philip Lowman<br>