[CMake] error in configuration process, project files may be invalid‏

Hello, I am using Microsoft visual studio 2010 professional, CMake 2.8.1 and InsightToolkit-3.16.0 in windows7. when I cmake source to binary, the following is the process: Check for working C compiler using: Visual Studio 10 Check for working C compiler using: Visual Studio 10 -- works D

[CMake] itk in windows 7

Hello, I am a beginner of ITK. Wanna know wether I can configure ITK in windows 7, bcs I use Microsoft visual studio 2010 professional, CMake 2.8.1 and InsightToolkit-3.16.0 in windows7. When I cmake the source codes, it always pop up different errors. Am I using the wrong virsion of compli

Re: [CMake] CMAKE_FIND_ROOT_PATH don't work as expected.

On Wednesday 14 April 2010, Diego wrote: > 2010/4/13 Alexander Neundorf ... > > Can you append the following code to Generic.cmake and see if it works > > then ? > > > > SET(CMAKE_SYSTEM_INCLUDE_PATH /include "${CMAKE_INSTALL_PREFIX}/include") > > SET(CMAKE_SYSTEM_LIBRARY_PATH /lib "${CMAKE_INSTAL

Re: [CMake] [PATCH] Fix for #0009721: Cpack in Macos segfaults when trying to build a NSIS (crosscompiled) package

On Wednesday 14 April 2010, Gerald Hofmann wrote: > Hi *, > > attached please find a patch for #0009721. I would be happy if someone > feels to accept it. > > The version string output obviously is different to the NSIS dist binary > when built from Macports. > > > makensis -VERSION > > < v25-Feb-2

[CMake] ExternalProject module -- questions

I'm trying to come up with a workable 'super build' for our programs, using the ExternalProject module. I'm using CMake 2.8.0 -- not sure if there's any substantive improvements in ExternalProject.cmake in 2.8.1 or CMake CVS. In short, I want to build Tcl, Tk, VTK, ITK (with WrapITK), CableSwig (

Re: [CMake] Two issues...

>> >> This CMAKE installation steps seem to be unix-centric, in expecting to >> target a consistant /usr/local/bin or /usr/bin etc for installation >> targets.   This particular tree that I'm slowly migrating actually has >> about a dozen individual targets, and each final installation needs to >>

Re: [CMake] Correct syntax for CPACK_NSIS_CREATE_ICONS [SOLVED]

Another way to do this without the insane \ stuff, is to use a configured file like CMake does: CONFIGURE_FILE("${CMake_SOURCE_DIR}/CMakeCPackOptions.cmake.in" "${CMake_BINARY_DIR}/CMakeCPackOptions.cmake" @ONLY) SET(CPACK_PROJECT_CONFIG_FILE "${CMake_BINARY_DIR}/CMakeCPack

Re: [CMake] CMAKE_FIND_ROOT_PATH don't work as expected.

2010/4/13 Alexander Neundorf > On Tuesday 13 April 2010, Diego wrote: > > Hello, > > I'm trying to cross-compiling a library for the PSP platform, this is my > > toolchain: > > > > *# The name of the target operating system. > > set(CMAKE_SYSTEM_NAME Generic) > > > > # Which compilers to use for

[CMake] [PATCH] Fix for #0009721: Cpack in Macos segfaults when trying to build a NSIS (crosscompiled) package

Hi *, attached please find a patch for #0009721. I would be happy if someone feels to accept it. The version string output obviously is different to the NSIS dist binary when built from Macports. > makensis -VERSION < v25-Feb-2010.cvs Version checking in cmCPackNSISGenerator.cxx fails indefi

[CMake] Project dependencies

Hello, we are using CMake to build different binaries which depend on some libraries, that we develop ourselves. At the moment we export the settings from the build directories of the libraries using export(... lib-build.cmake ...). The CMakeLists.txt of a binary uses an own CMake module using

Re: [CMake] Xcode generator linker flags

On 14. Jan, 2010, at 16:46 , Michael Wild wrote: > > On 14. Jan, 2010, at 16:18 , Michael Wild wrote: > >> Hi all >> >> I think that the Xcode generate is buggy as the linker flags are not >> inherited from the compile flags as they do in the Unix Makefile generator. >> Is this known/fixed/i

Re: [CMake] Correct syntax for CPACK_NSIS_CREATE_ICONS [SOLVED]

Hi Droscy, > Hi, probably you need to escape the backslashes 3 times, because when > cmake passes the option to cpack, it removes one escape, and cpack does > the same when creating nsis file. And you can also use single quote mark > in order to get the quotation on the final nsis file. > > So yo