On 07-May-15 00:00, Tamás Kenéz wrote:
Hi,
The search path rule #5 reads:
Search project build trees recently configured in a cmake-gui(1). This can be
skipped if
NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is
building
multiple dependent projects one after another. (This step is implemented only
on Windows.)
I think this rule, while having the best intentions, is error prone
(speaking from experience).
There are great and proper ways to use the products of a project in a
dependent project. Opening the project in cmake-gui to expose the
byproduct of a config-module configuration+installation process in the
binary dir, is not of them.
What do you think, would it be wise to disable this rule with a new
policy? Would anybody miss it?
Tamas
Totally agree, since I am a reporter of this bug:
http://public.kitware.com/Bug/view.php?id=14781
As far as I know it works only for GUI version and only on Windows. So
does anybody really use such workflow regularly?
Ruslo
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
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
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
