Yes, I did it again and again with rm -rf build.
Same result!
As I said: "The problem occurs always when I run cmake again, no
matter of Windows or Windows-gcc is used."
Claus
On 06.01.2010, at 20:23, Alexander Neundorf wrote:
On Wednesday 06 January 2010, Claus Klein wrote:
Hi Alex,
The problem occurs always when I run cmake again, no matter of
Windows
or Windows-gcc is used.
But I found in CMakeCache.txt this UNINITIALIZED values.
claus-kleins-macbook-pro:build clausklein$ grep UNINITIALIZED
CMakeCache.txt
CMAKE_CROSSCOMPILING:UNINITIALIZED=1
CMAKE_SYSTEM_NAME:UNINITIALIZED=Windows-gcc
claus-kleins-macbook-pro:build clausklein$
Perhaps this his the reason?
You need to start from a fresh build tree from scratch.
And you need to use "Windows" as system name, otherwise it cannot
work.
Alex
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
