Brandon J. Van Every wrote:
[...]
I just checked the file doc/cmake-2.4/cmake.html in
http://www.cmake.org/files/v2.4/cmake-2.4.6-Darwin-universal.tar.gz
and it correctly documents CLEAN_DIRECT_OUTPUT.
[...]
I used the .dmg based installer instead of the tarball you examined.
Although I
Brandon J. Van Every wrote:
[...]
This capability was added relatively recently, maybe in CMake 2.4.5.
What version of CMake are you using?
[...]
Hello,
as I said in my original mail, I'm running the most recent release
available for download, which is CMake 2.4.6 at the moment. I tried
On 2007-02-24 10:00-0800 Brandon J. Van Every wrote:
Thomas Christian Chust wrote:
as I said in my original mail, I'm running the most recent release
available for download, which is CMake 2.4.6 at the moment. I tried the
setting you recommended, and it works as it should, but probably the
Thomas Christian Chust wrote:
I consider this seriously buggy behaviour. First of all I don't like it
that the build system magically wipes out one of the library targets I
ordered it to create.
See SET_TARGET_PROPERTIES in the docs.
When a library is built CMake by default generates code to
Brandon J. Van Every wrote:
Thomas Christian Chust wrote:
I consider this seriously buggy behaviour. First of all I don't like it
that the build system magically wipes out one of the library targets I
ordered it to create.
[...] This can be prevented by setting the
CLEAN_DIRECT_OUTPUT
