Hi all,
I just spent an hour debugging a very strange phenomenon running CMake
on Mac OS-X, which in the end turned out to be trivial, but completely
unexpected for me.
The problem was caused by the fact that CMake had accidentally been run
once from the source directory. When running CMake in
On 5. Mar, 2010, at 14:19 , Marcel Loose wrote:
Hi all,
I just spent an hour debugging a very strange phenomenon running CMake
on Mac OS-X, which in the end turned out to be trivial, but completely
unexpected for me.
The problem was caused by the fact that CMake had accidentally been
On Fri, 2010-03-05 at 14:27 +0100, Michael Wild wrote:
On 5. Mar, 2010, at 14:19 , Marcel Loose wrote:
Hi all,
I just spent an hour debugging a very strange phenomenon running
CMake
on Mac OS-X, which in the end turned out to be trivial, but
completely
unexpected for me.
The
Marcel Loose wrote:
I would definitely like to get a warning when CMake finds a cache file
in what it thinks should be the source directory. It would have saved me
an hour of debugging. OTOH, now that I know of this strange behaviour,
I might be able to tackle these kinds of problems quicker.
I recently had to help out a CMake newbie, who had run CMake in the
source directory. Then he re-read the instructions on build setup for
our programs, and did it the right way -- i.e. he configured a build
directory for an out of source build.
Problem is, if you run CMake and configure the
2010/3/5 kent williams nkwmailingli...@gmail.com:
I recently had to help out a CMake newbie, who had run CMake in the
source directory. Then he re-read the instructions on build setup for
our programs, and did it the right way -- i.e. he configured a build
directory for an out of source
