Re: [CMake] Cross Compiling
On 4. Jan, 2010, at 19:15 , Alexander Neundorf wrote: [snip] - There is no distinction between install prefixes for the target and the host. Sometimes I'd like to put various build tools on the host system at the same time as libs and binaries on the target root. In CMake one build tree uses one toolchain. So in one build tree you can only create executable which run either for the target, of for the host, not both in one go. So if you need first to create host build tools, and later on use them for the actual cross compile, you need two build trees. I would recommend to export the executable and import them again in the cross build. If this is not your problem, but really just the install location, you can set the install location of every install() command separately, this is completely independent from the cross compiling support. To automate this you can use the ExternalProject.cmake that comes with CMake-2.8 to build the host tools. You can then use add_executable(tool IMPORTED) and set_target_properties(tool PROPERTIES IMPORTED_LOCATION ...) to import the tool target into the cross-compiling project. Michael ___ 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
[CMake] Does Cmake add 'standard' include paths ?
Generally I am using CMake successfully, and am generating makefiles for Linux, Solaris, and Visual Studio 9. I recently used the Eclipse CDT4 - NMake Makefiles generator, and then loaded the resulting project into my Eclipse environment under Windows XP. Eclipse then complains about missing include paths. The problem is that I have not specified these 'missing' paths in my CMakeLists.txt, or any file included by them. Does Cmake automatically add PROJECT\include to every project include paths with the Eclipse generator ? If so, is there a way to suppress this behavior ? ___ 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
[CMake] Compiler Test Failing on Windows 7
After upgrading to windows 7, I'm getting errors when trying to run the cmake project generation step. It seems as though I'm unable to copy a file. I have the directory as a subdirectory of my users folder, so I didn't think it would be a permissions issue. Here is the error: CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:69 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) Even though the path says AMD64, it's doing a 32-bit build. The path is made from a batch script, and cmake is hardcoded to use 32bit on windows in the build scripts. Any ideas on what the problem might be? Thanks, Joe ___ 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
Re: [CMake] Compiler Test Failing on Windows 7
Do you have a stale CMakeCache.txt file somewhere ? It's *usually* perfectly safe to delete all occurrences of CMakeCache.txt within a project and have CMake regenerate them. I say usually, because I have no idea if you are modifying that file for some reason, although the practice is not recommended. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Joe L Sent: Tuesday, January 05, 2010 2:09 PM To: cmake@cmake.org Subject: [CMake] Compiler Test Failing on Windows 7 After upgrading to windows 7, I'm getting errors when trying to run the cmake project generation step. It seems as though I'm unable to copy a file. I have the directory as a subdirectory of my users folder, so I didn't think it would be a permissions issue. Here is the error: CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:69 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) Even though the path says AMD64, it's doing a 32-bit build. The path is made from a batch script, and cmake is hardcoded to use 32bit on windows in the build scripts. Any ideas on what the problem might be? Thanks, Joe ___ 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
Re: [CMake] Compiler Test Failing on Windows 7
I deleted the whole build directory before running the build. There isn't any modifying of the CMakeCache.txt as far as i know. Joe From: Smith Jack (Ext. - UGIS - UniCredit Group) jack.smith.ext...@unicreditgroup.de To: cmake@cmake.org cmake@cmake.org Sent: Tue, January 5, 2010 8:24:51 AM Subject: Re: [CMake] Compiler Test Failing on Windows 7 Do you have a stale CMakeCache.txt file somewhere ? It's *usually* perfectly safe to delete all occurrences of CMakeCache.txt within a project and have CMake regenerate them. I say usually, because I have no idea if you are modifying that file for some reason, although the practice is not recommended. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Joe L Sent: Tuesday, January 05, 2010 2:09 PM To: cmake@cmake.org Subject: [CMake] Compiler Test Failing on Windows 7 After upgrading to windows 7, I'm getting errors when trying to run the cmake project generation step. It seems as though I'm unable to copy a file. I have the directory as a subdirectory of my users folder, so I didn't think it would be a permissions issue. Here is the error: CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:69 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) Even though the path says AMD64, it's doing a 32-bit build. The path is made from a batch script, and cmake is hardcoded to use 32bit on windows in the build scripts. Any ideas on what the problem might be? Thanks, Joe ___ 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
Re: [CMake] Compiler Test Failing on Windows 7
The path is made from a batch script, and cmake is hardcoded to use 32bit on windows in the build scripts. I'm no expert, but it seems like you must have something wrong in the 'batch script' (or your environment). It looks like cmake thinks it's running on a AMD64 based system. I think the OS architecture is *normally* auto-detected, and to mistake a 32 bit OS for a 64 bit one seems like a pretty big error. Have you examined the script to be sure it's not misbehaving under Windows 7 - perhaps a list of known OSes doesn't include Win7 ? From: Joe L [mailto:superist_...@yahoo.com] Sent: Tuesday, January 05, 2010 2:44 PM To: Smith Jack (Ext. - UGIS - UniCredit Group); cmake@cmake.org Subject: Re: [CMake] Compiler Test Failing on Windows 7 I deleted the whole build directory before running the build. There isn't any modifying of the CMakeCache.txt as far as i know. Joe From: Smith Jack (Ext. - UGIS - UniCredit Group) jack.smith.ext...@unicreditgroup.de To: cmake@cmake.org cmake@cmake.org Sent: Tue, January 5, 2010 8:24:51 AM Subject: Re: [CMake] Compiler Test Failing on Windows 7 Do you have a stale CMakeCache.txt file somewhere ? It's *usually* perfectly safe to delete all occurrences of CMakeCache.txt within a project and have CMake regenerate them. I say usually, because I have no idea if you are modifying that file for some reason, although the practice is not recommended. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Joe L Sent: Tuesday, January 05, 2010 2:09 PM To: cmake@cmake.org Subject: [CMake] Compiler Test Failing on Windows 7 After upgrading to windows 7, I'm getting errors when trying to run the cmake project generation step. It seems as though I'm unable to copy a file. I have the directory as a subdirectory of my users folder, so I didn't think it would be a permissions issue. Here is the error: CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:69 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) Even though the path says AMD64, it's doing a 32-bit build. The path is made from a batch script, and cmake is hardcoded to use 32bit on windows in the build scripts. Any ideas on what the problem might be? Thanks, Joe ___ 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
Re: [CMake] Compiler Test Failing on Windows 7
I wrote the batch script that Joe is using - the AMD64 in the build directory path is just a consequence of using %PROCESSOR_ARCHITECTURE% to create the build directory from the batch script and is purely a cosmetic issue. The CMake generator is what selects whether the build is 32-bit or 64-bit, and we definitely use the 32-bit Visual Studio 2005 generator. Since CMake is a 32-bit process, it sees the system as being 32-bit when processing CMakelists.txt, and is definitely using our configuration settings for 32-bit Windows. I'm especially puzzled by this behavior because the same project builds successfully in 64-bit Vista. Gregory Peele, Jr. Applied Research Associates, Inc. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Smith Jack (Ext. - UGIS - UniCredit Group) Sent: Tuesday, January 05, 2010 8:51 AM To: cmake@cmake.org Subject: Re: [CMake] Compiler Test Failing on Windows 7 The path is made from a batch script, and cmake is hardcoded to use 32bit on windows in the build scripts. I'm no expert, but it seems like you must have something wrong in the 'batch script' (or your environment). It looks like cmake thinks it's running on a AMD64 based system. I think the OS architecture is *normally* auto-detected, and to mistake a 32 bit OS for a 64 bit one seems like a pretty big error. Have you examined the script to be sure it's not misbehaving under Windows 7 - perhaps a list of known OSes doesn't include Win7 ? From: Joe L [mailto:superist_...@yahoo.com] Sent: Tuesday, January 05, 2010 2:44 PM To: Smith Jack (Ext. - UGIS - UniCredit Group); cmake@cmake.org Subject: Re: [CMake] Compiler Test Failing on Windows 7 I deleted the whole build directory before running the build. There isn't any modifying of the CMakeCache.txt as far as i know. Joe From: Smith Jack (Ext. - UGIS - UniCredit Group) jack.smith.ext...@unicreditgroup.de To: cmake@cmake.org cmake@cmake.org Sent: Tue, January 5, 2010 8:24:51 AM Subject: Re: [CMake] Compiler Test Failing on Windows 7 Do you have a stale CMakeCache.txt file somewhere ? It's *usually* perfectly safe to delete all occurrences of CMakeCache.txt within a project and have CMake regenerate them. I say usually, because I have no idea if you are modifying that file for some reason, although the practice is not recommended. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Joe L Sent: Tuesday, January 05, 2010 2:09 PM To: cmake@cmake.org Subject: [CMake] Compiler Test Failing on Windows 7 After upgrading to windows 7, I'm getting errors when trying to run the cmake project generation step. It seems as though I'm unable to copy a file. I have the directory as a subdirectory of my users folder, so I didn't think it would be a permissions issue. Here is the error: CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin cannot be read. Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:69 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) CMake Error: Could not COPY_FILE. OutputFile: '' copyFile: 'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin' Unable to find executable for try_compile: tried C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec.exe and C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeTmp/Development/cmTryCompileExec.exe. CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:40 (FILE): file STRINGS file
Re: [CMake] Compiler Test Failing on Windows 7
Am Dienstag 05 Januar 2010 14:09:00 schrieb Joe L: C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) You might want to avoid instal cmake in a path with spaces. I install software with unix layout to C:\local HS ___ 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
Re: [CMake] Compiler Test Failing on Windows 7
On Tue, Jan 5, 2010 at 12:38 PM, Hendrik Sattler p...@hendrik-sattler.dewrote: Am Dienstag 05 Januar 2010 14:09:00 schrieb Joe L: C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) You might want to avoid instal cmake in a path with spaces. I install software with unix layout to C:\local Nonsense. CMake works fine in a directory that has spaces in its name. We wouldn't make the default installation directory on Windows have spaces in it if it did have problems... There must be something else going on here. ___ 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
Re: [CMake] CUDA, CMAKE, and an attempt to build nbody
I ask my self two questions:
1) Why is CUDA_NVCC_FLAGS not set to some default build setting that would
just work out of the box? - I get the answer to this question when I turn on
CUDA_VERBOSE_BUILD_MODE - It is being set under the hood.
I guess I don't understand your question. The CUDA_NVCC_FLAGS are the flags
used by all targets all the time. Occasionally additional flags are added
(such as -fPIC on certain systems as well as other flags) that make it work
based on your individual project configuration. It does work out of the box
for many applications.
2) There is a CUDA_TOOLKIT_INCLUDE, but no CUDA_SDK_INCLUDE (or _LIB)...
why? (this would prevent ${CUDA_SDK_ROOT_DIR}/common/inc - see below)
As you found out the include directories for the CUDA SDK are not supported
by FindCUDA. Those libraries and headers are designed to be used by the
SDK, and not particularly by external packages. That doesn't prevent you
from doing so, but it was decided that because the CUDA SDK won't maintain
backward compatibility and is only designed for the SDK that external use
would not be supported by FindCUDA. As a compromise I chose to have as a
bare minimum a path to the SDK be supported for those who wished to poke in
the SDK to find things such as libraries or header files. There is
documentation in the help files and in the FindCUDA.cmake file as well as
examples of what to do with the CUDA_SDK_ROOT_DIR variable.
Maybe these guys could answer question 2:
James Bigler, NVIDIA Corp (nvidia.com - jbigler)
This is me. Abe has a job at Apple, and doesn't have much time to maintain
this anymore.
Abe Stephens, SCI Institute --
http://www.sci.utah.edu/~abe/FindCuda.htmlhttp://www.sci.utah.edu/%7Eabe/FindCuda.html
A request here would be to seperate FindCUDA into :
FindCUDA
and
FindNVIDIACUDASDK
and add include and lib dirs environment vars.
I welcome any volunteers to maintain a FindCUDASDK. I don't plan on ever
supporting this.
So I then add to my CMakeLists.txt file (I think in a vain attempt to make
it work):
INCLUDE_DIRECTORIES( ${CUDA_SDK_ROOT_DIR}/common/inc )
Yes, this in the right thing to do.
So I add:
link_directories( ${CUDA_SDK_ROOT_DIR}/common/lib )
You might want to do what I suggest in FindCUDA.cmake and do the following
(copied from FindCUDA.cmake):
# Example of how to find a library in the CUDA_SDK_ROOT_DIR
# # cutil library is called cutil64 for 64 bit builds on windows. We don't
want
# # to get these confused, so we are setting the name based on the word size
of
# # the build.
# if(CMAKE_SIZEOF_VOID_P EQUAL 8)
# set(cuda_cutil_name cutil64)
# else(CMAKE_SIZEOF_VOID_P EQUAL 8)
# set(cuda_cutil_name cutil32)
# endif(CMAKE_SIZEOF_VOID_P EQUAL 8)
# find_library(CUDA_CUT_LIBRARY
# NAMES cutil ${cuda_cutil_name}
# PATHS ${CUDA_SDK_SEARCH_PATH}
# # The new version of the sdk shows up in common/lib, but the old one is
in lib
# PATH_SUFFIXES common/lib lib
# DOC Location of cutil library
# NO_DEFAULT_PATH
# )
# # Now search system paths
# find_library(CUDA_CUT_LIBRARY NAMES cutil ${cuda_cutil_name} DOC Location
of cutil library)
# mark_as_advanced(CUDA_CUT_LIBRARY)
# set(CUDA_CUT_LIBRARIES ${CUDA_CUT_LIBRARY})
Then do things like target_link_libraries(nbody ${CUDA_CUT_LIBRARIES})
You shouldn't need to create imported libraries through add_library and
set_properties.
James
___
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
Re: [CMake] Does Cmake add 'standard' include paths ?
On Tuesday 05 January 2010, Smith Jack (Ext. - UGIS - UniCredit Group) wrote: Generally I am using CMake successfully, and am generating makefiles for Linux, Solaris, and Visual Studio 9. I recently used the Eclipse CDT4 - NMake Makefiles generator, and then loaded the resulting project into my Eclipse environment under Windows XP. Which version of CMake, and which version of Eclipse and CDT are you using ? Eclipse then complains about missing include paths. The problem is that I have not specified these 'missing' paths in my CMakeLists.txt, or any file included by them. About which missing include paths does it complain ? About include dirs you did not specify ? Does Cmake automatically add PROJECT\include to every project include No. paths with the Eclipse generator ? If so, is there a way to suppress this behavior ? Can you create a small example project which shows this issue ? Then I could check whether I can reproduce it under Linux. 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
Re: [CMake] Does Cmake add 'standard' include paths ?
On Tuesday 05 January 2010, Smith Jack (Ext. - UGIS - UniCredit Group) wrote: Generally I am using CMake successfully, and am generating makefiles for Linux, Solaris, and Visual Studio 9. I recently used the Eclipse CDT4 - NMake Makefiles generator, and then loaded the resulting project into my Eclipse environment under Windows XP. Which version of CMake, and which version of Eclipse and CDT are you using ? Eclipse then complains about missing include paths. The problem is that I have not specified these 'missing' paths in my CMakeLists.txt, or any file included by them. About which missing include paths does it complain ? About include dirs you did not specify ? Does Cmake automatically add PROJECT\include to every project include No. paths with the Eclipse generator ? If so, is there a way to suppress this behavior ? Can you create a small example project which shows this issue ? Then I could check whether I can reproduce it under Linux. 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
Re: [CMake] Cross Compiling
On Tuesday 05 January 2010, Michael Wild wrote: On 4. Jan, 2010, at 19:15 , Alexander Neundorf wrote: [snip] - There is no distinction between install prefixes for the target and the host. Sometimes I'd like to put various build tools on the host system at the same time as libs and binaries on the target root. In CMake one build tree uses one toolchain. So in one build tree you can only create executable which run either for the target, of for the host, not both in one go. So if you need first to create host build tools, and later on use them for the actual cross compile, you need two build trees. I would recommend to export the executable and import them again in the cross build. If this is not your problem, but really just the install location, you can set the install location of every install() command separately, this is completely independent from the cross compiling support. To automate this you can use the ExternalProject.cmake that comes with CMake-2.8 to build the host tools. Maybe, I haven't tried to combine this yet. You can then use add_executable(tool IMPORTED) and set_target_properties(tool PROPERTIES IMPORTED_LOCATION ...) to import the tool target into the cross-compiling project. That's not necessary to do manually. You can use the EXPORT feature for the necessary executables, something like this: If you don't want to install the project first, you can add an if(NOT CMAKE_CROSSCOMPILING) export(TARGETS ... ) endif(NOT CMAKE_CROSSCOMPILING) to create such a export file in the buildtree. 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
Re: [CMake] Cross Compiling
On 5. Jan, 2010, at 19:55 , Alexander Neundorf wrote: On Tuesday 05 January 2010, Michael Wild wrote: On 4. Jan, 2010, at 19:15 , Alexander Neundorf wrote: [snip] - There is no distinction between install prefixes for the target and the host. Sometimes I'd like to put various build tools on the host system at the same time as libs and binaries on the target root. In CMake one build tree uses one toolchain. So in one build tree you can only create executable which run either for the target, of for the host, not both in one go. So if you need first to create host build tools, and later on use them for the actual cross compile, you need two build trees. I would recommend to export the executable and import them again in the cross build. If this is not your problem, but really just the install location, you can set the install location of every install() command separately, this is completely independent from the cross compiling support. To automate this you can use the ExternalProject.cmake that comes with CMake-2.8 to build the host tools. Maybe, I haven't tried to combine this yet. You can then use add_executable(tool IMPORTED) and set_target_properties(tool PROPERTIES IMPORTED_LOCATION ...) to import the tool target into the cross-compiling project. That's not necessary to do manually. You can use the EXPORT feature for the necessary executables, something like this: If you don't want to install the project first, you can add an if(NOT CMAKE_CROSSCOMPILING) export(TARGETS ... ) endif(NOT CMAKE_CROSSCOMPILING) to create such a export file in the buildtree. Alex I thought of that too, but then you have to run CMake a second time after the first build failed because the export file won't be created until build-time. Chicken-egg thing again :-( Michael ___ 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
Re: [CMake] Compiler Test Failing on Windows 7
David Cole wrote: On Tue, Jan 5, 2010 at 12:38 PM, Hendrik Sattler p...@hendrik-sattler.de mailto:p...@hendrik-sattler.de wrote: Am Dienstag 05 Januar 2010 14:09:00 schrieb Joe L: C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62 (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT) You might want to avoid instal cmake in a path with spaces. I install software with unix layout to C:\local Nonsense. CMake works fine in a directory that has spaces in its name. We wouldn't make the default installation directory on Windows have spaces in it if it did have problems... There must be something else going on here. This has nothing to do with copy file not working. The copy file is not working because no executable was generated for some reason. You should look in CMakeError.log and CMakeOutput.log. If that fails to show anything, then run cmake --debug-trycompile, then go into the CMakeFiles directory and run the build tool by hand and figure out why it is not producing executable files. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 ___ 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
Re: [CMake] mingw crosscompile error: invalid option `macosx-version-min=10.5' ?
Hi Alex,
I have used this system_name because I found this file:
claus-kleins-macbook-pro:Platform clausklein$ grep -iw mingw *.cmake
Windows-gcc.cmake:SET(CMAKE_EXTRA_LINK_EXTENSIONS .lib) # MinGW can
also link to a MS .lib
Windows-gcc.cmake:IF(MINGW)
Windows-gcc.cmake:ENDIF(MINGW)
Windows-gcc.cmake:IF(MSYS OR MINGW)
Windows-gcc.cmake:ENDIF(MSYS OR MINGW)
Windows-gcc.cmake:IF(MSYS OR MINGW)
Windows-gcc.cmake:ENDIF(MSYS OR MINGW)
WindowsPaths.cmake: # MinGW (useful when cross compiling from linux
with CMAKE_FIND_ROOT_PATH set)
WindowsPaths.cmake:# mingw can also link against dlls which can also
be in /bin, so list this too
claus-kleins-macbook-pro:Platform clausklein$ ls -l $PWD/Windows-gcc*
-rw-r--r-- 2 root admin 4097 13 Nov 19:32 /opt/local/share/
cmake-2.8/Modules/Platform/Windows-gcc.cmake
claus-kleins-macbook-pro:Platform clausklein$
Note: I was crosscompiling for MinGW
//regards
Claus
On 04.01.2010, at 19:22, Alexander Neundorf wrote:
On Sunday 03 January 2010, Claus Klein wrote:
I have problems to crosscompile on MAC-OS for MinGW.
How kann I prevent this strange compiler flag on a Darwin Plattform?
Thanks
Claus
-
cmake -DCMAKE_C_COMPILER=i386-mingw32-gcc -DCMAKE_CXX_COMPILER=i386-
mingw32-g++ --debug-trycompile --debug-output -
DCMAKE_SYSTEM_NAME=Windows-gcc ..
CMAKE_SYSTEM_NAME should be set to Windows, not Windows-gcc,
because there
is not operating system Windows-gcc in cmake (it tries to load
Modules/Platform/${CMAKE_SYSTEM_NAME}.cmake).
In this case it should not load Darwin.cmake at all.
Does it work better if you do this ?
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
[CMake] xxxxxSPAMxxxxx Simple Question Regarding Link Libraries on Linux
How do I link a *.a file that doesn't start with "lib" to an executable? For example, if I have a library named foo.a with a function called getnum, how do I link to foo.a in CMakeLists.txt?If my executable file is---main.cpp---extern int getnum();int main(int, char**) { cout getnum() endl;}and my CMakeFile is---CMakeLists.txt---PROJECT(TESTPROJECT)ADD_EXECUTABLE(test main.cpp foo.a)---I'll get an error about an undefined reference to getnum when I run the makefile.If I use TARGET_LINK_LIBRARIES(test foo), I'll get an error about not begin able to find the library, since it's using the -l flag for the linker. I'd rather not have to rename foo.a, because it will affect other existing software.Thanks,-Ed
___
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
[CMake] runtime error of ctest in windows VS2005
Dear all,
Im using Windows and the compiler is VS2005. I wrote a CMakeLists.txt file to
run a image registration program, which generates a executable named as
FFD_3D_mask.exe. This executable takes some arguments as names of input and
output files. The CMake file is written as the following, and it runs properly
and the generated executable also works fine by inputing the arguments manually
in the command window.
-cmake_minimum_required(VERSION 2.8)
PROJECT(FFD_3D_mask)
FIND_PACKAGE(ITK)
IF(ITK_FOUND) INCLUDE(${ITK_USE_FILE})ELSE(ITK_FOUND) MESSAGE(FATAL_ERROR
ITK not found. Please set ITK_DIR.)ENDIF(ITK_FOUND)
ADD_EXECUTABLE(FFD_3D_mask FFD_3D_mask.cxx )
TARGET_LINK_LIBRARIES(FFD_3D_mask ITKCommon ITKIO ITKNumerics ITKStatistics)
Then I tried to automatically run the executable, without having to type the
arguments manually everytime. Then I added the following lines. I build the
executable first, and then build the RUN_TEST. The test is failed, and the
error message is attached. I am not sure whether the code I wrote was wrong, or
didnt build the test properly?
--
ENABLE_TESTING()
SET(IMAGE_DIR C:/MRI/Images/MHD)
ADD_TEST(RUN_TEST FFD_3D_mask.exe ${IMAGE_DIR}/fixed.mhd
${IMAGE_DIR}/flirt.mhd ${IMAGE_DIR}/output.mhd ${IMAGE_DIR}/mask_fix.mhd
${IMAGE_DIR}/mask_moving.mhdDiffAfter.mhd DiffBefore.mhd
DeformationField.mhd1 1 TransformationParas.txt 5
IdenTransform.tfm)
The error msg
1-- Build started: Project: RUN_TESTS, Configuration: Debug Win32 --1
1Performing Post-Build Event...1Test project
C:/MRI/ITK/test/Registration/Deformable/3D_mask/build1Start 1:
RUN_TEST11/1 Test #1: RUN_TEST .***Failed7.47
sec10% tests passed, 1 tests failed out of 11Total Test time (real) = 7.50
sec1The following tests FAILED:1 1 - RUN_TEST (Failed)1Errors while
running CTest1Project : error PRJ0019: A tool returned an error code from
Performing Post-Build Event...1Build log was saved at
file://c:\MRI\ITK\test\Registration\Deformable\3D_mask\build\RUN_TESTS.dir\Debug\BuildLog.htm1RUN_TESTS
- 1 error(s), 0 warning(s)== Build: 0 succeeded, 1 failed, 0
up-to-date, 0 skipped ==
_
Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail
you.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010___
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
Re: [CMake] xxxxxSPAMxxxxx Simple Question Regarding Link Libraries on Linux
Whoever developed foo.a should call it libfoo.a instead so it meets
standards. All libraries on Linux are supposed to start with lib
with the possible exception of dynamically loaded shared libraries
(i.e. plugins).
If you still can't rename it, you can do target_link_libraries(bar
/full/path/to/foo.a).
To get the full path of your source tree you can use
${CMAKE_CURRENT_SOURCE_DIR}.
On Tue, Jan 5, 2010 at 5:57 PM, ed.j...@agileplanet.com wrote:
How do I link a *.a file that doesn't start with lib to an executable?
For example, if I have a library named foo.a with a function called getnum,
how do I link to foo.a in CMakeLists.txt?
If my executable file is
---main.cpp---
extern int getnum();
int main(int, char**) { cout getnum() endl;}
and my CMakeFile is
---CMakeLists.txt---
PROJECT(TESTPROJECT)
ADD_EXECUTABLE(test main.cpp foo.a)
---
I'll get an error about an undefined reference to getnum when I run the
makefile.
If I use TARGET_LINK_LIBRARIES(test foo), I'll get an error about not begin
able to find the library, since it's using the -l flag for the linker. I'd
rather not have to rename foo.a, because it will affect other existing
software.
Thanks,
-Ed
___
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
--
Philip Lowman
___
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
Re: [CMake] Mediawiki CMake syntax highlighting
On Mon, Nov 30, 2009 at 8:17 AM, David Cole david.c...@kitware.com wrote: I forwarded it along... We'll see if it works good and let you know. Just following up - any luck with this? Thanks, David ___ 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
Re: [CMake] runtime error of ctest in windows VS2005
2010/1/6 Xi LIANG liangxi1986...@hotmail.com:
Dear all,
Im using Windows and the compiler is VS2005. I wrote a CMakeLists.txt file
to run a image registration program, which generates a executable named as
FFD_3D_mask.exe. This executable takes some arguments as names of input and
output files. The CMake file is written as the following, and it runs
properly and the generated executable also works fine by inputing the
arguments manually in the command window.
-
cmake_minimum_required(VERSION 2.8)
PROJECT(FFD_3D_mask)
FIND_PACKAGE(ITK)
IF(ITK_FOUND)
INCLUDE(${ITK_USE_FILE})
ELSE(ITK_FOUND)
MESSAGE(FATAL_ERROR
ITK not found. Please se t ITK_DIR.)
ENDIF(ITK_FOUND)
ADD_EXECUTABLE(FFD_3D_mask FFD_3D_mask.cxx )
TARGET_LINK_LIBRARIES(FFD_3D_mask ITKCommon ITKIO ITKNumerics ITKStatistics)
Then I tried to automatically run the executable, without having to type the
arguments manually everytime. Then I added the following lines. I build the
executable first, and then build the RUN_TEST. The test is failed, and the
error message is attached. I am not sure whether the code I wrote was wrong,
or didnt build the test properly?
First I would avoid calling your test RUN_TEST knowing that the
CMake generated
target is called RUN_TESTS this can lead to confusion at most.
May be GenMaskTest or something more meaningfull would be good.
However this shouldn't be the problem root.
The default behavior of ctest is to check the returned value of the executable
is your executable returning something different from 0 when it succeed?
You said the test is failing but from what you give us we can only tell that
C Test believe the test is failing, however could you check whether if the test
is producing the expected files?
Did you look at the failed log inside
build\RUN_TESTS.dir\Debug\?
I don't know how to do it from within Visual Studio but if you open a
command line prompt
and change dir to you build dir:
file://c:\MRI\ITK\test\Registrati on\Deformable\3D_mask\build
you may try to run ctest manually with verbose option:
ctest -VV
this should show you more details on the execution.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
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
