On Thu, Dec 18, 2008 at 2:37 PM, Hendrik Sattler <span dir="ltr"><<a href="mailto:post@hendrik-sattler.de">post@hendrik-sattler.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Am Thursday 18 December 2008 20:03:25 schrieb Philip Lowman:<br>
<div class="Ih2E3d">> Could you try the following beta FindGTK2 module?<br>
><br>
> Set CMAKE_MODULE_PATH prior to calling FIND_PACKAGE(GTK2 COMPONENTS gtk)<br>
> See the module for details<br>
<br>
</div>Some notes: you should make better use of path suffixes in find_file instead<br>
of repeating standard paths. Additionally, you should prefer the directory of<br>
the glib library + include/ for finding glibconfig.h.</blockquote><div><br>Thanks for the pointers. I've switched to path suffixes for the include paths (it's not any more readable but it cuts down on the number of lines in the file). I also fixed a lot of other stuff.<br>
<br>One question for you, however. Is the module picking up glibconfig.h in the wrong directory? If so, what directory, what version of GTK, etc.? In other words, is the current hack I have in there about searching all of the relative directories causing problems for you? I've been meaning to modify my header file searching macro to limit the find_path() search to just the proper relative include directory. I will probably fix this at some point in the near future.<br>
<br>Also, this module eagerly awaits wildcard support for find_library(). GTK also uses blasted version numbers encoded in the filename (like FindBoost).<br><br></div></div>-- <br>Philip Lowman<br>