[CMake] Forwarding parameters to cmake through cmake-gui

[physhh .]

+1 for updating cmake-gui to work equally to ccmake

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:
- Change the find-module directly so it works in the local environment
- 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.

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.



On Fri, Nov 1, 2013 at 4:56 PM, Bill Hoffman <bill.hoffman at kitware.com>wrote:

> On 11/1/2013 10:47 AM, physhh . wrote:
>
>> If cmake is used directly from the command line, it's possible to pass a
>> bunch of options
>> (http://www.cmake.org/cmake/**help/v2.8.12/cmake.html#**section_Options<http://www.cmake.org/cmake/help/v2.8.12/cmake.html#section_Options>
>> ).
>> This is nice because with this it's possible to use default settings -
>> even if the cache get deleted. I'm actually really interested in this
>> because it would be possible to set the CMAKE_MODULE_PATH variable via
>> batch file - which is neat for custom find modules in custom locations.
>>
> Branching the topic a bit.
>
> cmake-gui should most likely be updated to take the same arguments that
> ccmake and cmake take.
>
> 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).
>
> -Bill
>
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/**CMake_FAQ<http://www.cmake.org/Wiki/CMake_FAQ>
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/**support.html<http://cmake.org/cmake/help/support.html>
> CMake Consulting: http://cmake.org/cmake/help/**consulting.html<http://cmake.org/cmake/help/consulting.html>
> CMake Training Courses: http://cmake.org/cmake/help/**training.html<http://cmake.org/cmake/help/training.html>
>
> Visit other Kitware open-source projects at http://www.kitware.com/**
> opensource/opensource.html<http://www.kitware.com/opensource/opensource.html>
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/**listinfo/cmake<http://www.cmake.org/mailman/listinfo/cmake>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20131101/a640634e/attachment.htm>