Notes |
|
(0035442)
|
Eric NOULARD
|
2014-03-20 03:45
|
|
Hi Daniel,
Have a look at related bug 0006672 you'll see this is a long-running well-known issue. |
|
|
(0035443)
|
Eric NOULARD
|
2014-03-20 03:49
|
|
The reason is stated in cmake command line help:
$ cmake --help
Usage
cmake [options] <path-to-source>
cmake [options] <path-to-existing-build>
in order to support
cmake [options] <path-to-existing-build>
in a backward compatible way the behavior you observe should be kept.
CMake consider the source dir as an existing build dir precisely because
there is a CMakeCache.txt ini it. |
|
|
(0035455)
|
Daniel Hasemann
|
2014-03-20 10:52
|
|
Ok, backwards compatibility is one of the most important things. Is it possible to force out-of-source builds or to deny in-source builds with a cmake option or an environment variable? |
|
|
(0035473)
|
Ben Boeckel
|
2014-03-21 13:59
|
|
There is 'if ("${ParaView_SOURCE_DIR}" STREQUAL "${ParaView_BINARY_DIR}")' that ParaView does to detect and error if so, but that won't get you anywhere. The CMakeCache.txt needs to be moved out of the way for CMake to continue with the out-of-source build (since by the time you detect the error, the build directory has already been determined). |
|
|
(0042511)
|
Kitware Robot
|
2016-06-10 14:29
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
|