<div class="gmail_quote">On Mon, Mar 2, 2009 at 9:59 AM, Adolfo Rodríguez <span dir="ltr"><<a href="mailto:dofo79@gmail.com">dofo79@gmail.com</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;">
Hi all,<br><br>After reading the recently added wiki <a href="http://www.cmake.org/Wiki/CMake:Improving_Find*_Modules" target="_blank">doc</a> about improving CMake Find* modules, I have a style question. In the section that discusses finding packages in unusual locations, it is suggested that "Each module should have an environment variable that is looked at first... Once the module finds the package based on the environment variable, a
CMake cache variable of the same name should be created". Is there a naming convention for this environment variable?. I was thinking that <PackageName>_ROOT would be a good idea, since it would go along nicely with existing CMake variables such as BOOST_ROOT.<br>
<br>I'm currently overhauling a bunch of custom-made Find* packages, and would like to adhere as much as possible to the existing naming conventions.</blockquote><div><br>There is a <PackageName>_ROOT_DIR in the official readme.txt although usage is somewhat split, many modules use <PackageName>_ROOT including CMake itself.<br>
</div></div><br>See the Modules/readme.txt file for other variables:<br><a href="http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/readme.txt?root=CMake&view=markup">http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/readme.txt?root=CMake&view=markup</a><br>
<br>-- <br>Philip Lowman<br>