<div dir="ltr"><div><div><div><div>+1 for updating cmake-gui to work equally to ccmake<br><br></div>But my opinion regarding CMAKE_MODULE_PATH is different. The problem is that alot of the default find-modules don't work because the dependency is not in the location where the find-module expects it. Currently there are only two workarounds:<br>
</div>- Change the find-module directly so it works in the local environment<br></div>- Change the CMakeLists.txt of the project - which is bad because it's just a LOCAL problem and the CMakeLists should be mostly independent of the environment.<br>
<br></div>With the command-line option it's possible to setup a custom cmake-gui batch file once per computer which sets e.g. the CMAKE_MODULE_PATH to a directory with customized find modules. If one doesn't want to use custom find modules that's fine too but I think everyone should have the option to place dependent libraries wherever she/he wants.<br>
<div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 1, 2013 at 4:56 PM, Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 11/1/2013 10:47 AM, physhh . wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If cmake is used directly from the command line, it's possible to pass a<br>
bunch of options<br>
(<a href="http://www.cmake.org/cmake/help/v2.8.12/cmake.html#section_Options" target="_blank">http://www.cmake.org/cmake/<u></u>help/v2.8.12/cmake.html#<u></u>section_Options</a>).<br>
This is nice because with this it's possible to use default settings -<br>
even if the cache get deleted. I'm actually really interested in this<br>
because it would be possible to set the CMAKE_MODULE_PATH variable via<br>
batch file - which is neat for custom find modules in custom locations.<br>
</blockquote></div>
Branching the topic a bit.<br>
<br>
cmake-gui should most likely be updated to take the same arguments that ccmake and cmake take.<br>
<br>
However, if you are setting CMAKE_MODULE_PATH, the best place to do it is in the CMake code of your project. That way your project will stand on its own and not require special command line options to build (which is bad IMO).<span class="HOEnZb"><font color="#888888"><br>
<br>
-Bill</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/<u></u>CMake_FAQ</a><br>
<br>
Kitware offers various services to support the CMake community. For more information on each offering, please visit:<br>
<br>
CMake Support: <a href="http://cmake.org/cmake/help/support.html" target="_blank">http://cmake.org/cmake/help/<u></u>support.html</a><br>
CMake Consulting: <a href="http://cmake.org/cmake/help/consulting.html" target="_blank">http://cmake.org/cmake/help/<u></u>consulting.html</a><br>
CMake Training Courses: <a href="http://cmake.org/cmake/help/training.html" target="_blank">http://cmake.org/cmake/help/<u></u>training.html</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/<u></u>opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/<u></u>listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>