my stuff to work with VS2010. Great job on the
other VS2010 issues btw!
Cheers,
Anteru
___
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 c
plicate this if both debug/release are in the same folder
(symlinking on Windows requires root rights, so it's out of question.)
So what is the recommended way to set it (if there is any)? Otherwise,
where can I vote for issue #9163?
Cheers,
Anteru
OT: Just managed to build CMake
x64 Python installed. I tried used ctest --debug -VV
--force-new-ctest-process -C Debug and I also tried without
--force-new-ctest-process, but both result in CTest crashing
Cheers,
Anteru
5: Test command: D:\Dev\Current\nw\trunk\build\tools\FuncTestRunner.py
--config Debug D:/Dev/Current/nw-build/
Zschocke, Florian schrieb:
Hi Anteru!
I had the same problem. Read here:
http://www.cmake.org/pipermail/cmake/2008-March/020255.html
Thnaks for the link. But from that I gather that you can only use the
target name as an actual command and not as a parameter to the command,
e.g. when copying
ll as an added postfix for
> the Debug configuration.
I had the same problem. Read here:
http://www.cmake.org/pipermail/cmake/2008-March/020255.html
Cheers,
Anteru
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
ADD_CUSTOM_COMMAND, so I can pass MyTarget to it, which gets filled with
the right value.
ADD_EXECUTABLE(Test ${TEST_SOURCES})
SET_TARGET_PROPERTIES(Test PROPERTIES DEBUG_POSTFIX "d")
ADD_CUSTOM_COMMAND(
TARGET Test
POST_BUILD
COMMAND Test
)
works fine.
Cheers
s does solve the problem; is there
some better/cleaner solution for this? Otherwise I'll stick with it.
Leaves the other problem only, seems it has been discussed already
(http://preview.tinyurl.com/yw6vlc) without a definite answer whether it
is a bug or not.
Cheers,
Anteru
___
my custom install
script with the INSTALL command, which is really great.
Thanks for the insights into your approach, if there is indeed no better
solution I'll probably have to resort to something similar, I'm just
hoping that there is indeed a
x27;m just wondering.
* What is the recommended way to check for x64 Windows? I'm using a
custom option, but I'd like to have that fully automatic if possible. I
only found this list here
http://www.cmake.org/Wiki/CMake_Useful_Variables#System_.26_Compile
