Re: [CMake] escaping spaces in paths with cmake -E commands?

Now, when I had set this all up in the context of an ADD_CUSTOM_COMMAND instead of an EXEC_PROGRAM, things seemed to work -- is there automatic path escaping for args to custom commands, but not exec'd programs, in this version of CMake? (For some reason, we had to move to EXEC_PROGRAM

[CMake] escaping spaces in paths with cmake -E commands?

Hi folks, I'm using CMake 2.2-3, and have recently run into some problems with a stanza of CMake code that looks like this: SET(src "${IN_DIR}/foo.bar") SET(tgt "${OUT_DIR}/foo.bar") EXEC_PROGRAM(${CMAKE_COMMAND} ARGS -E copy_if_different ${src} ${tgt}) The problem comes when src or tgt have

Re: [CMake] CVS CMake: makefile install rule broken

Thanks, the Makefile problem is indeed fixed. Zach On Feb 28, 2006, at 6:54 AM, Brad King wrote: Zachary Pincus wrote: Just a heads up in case this isn't known (let me know if I should file a bug): I just checked out CMake from CVS and found that it generates invalid makefiles

[CMake] CVS CMake: makefile install rule broken

Just a heads up in case this isn't known (let me know if I should file a bug): I just checked out CMake from CVS and found that it generates invalid makefiles on my system. (Darwin; CMake installed to /usr/local.) Specifically, the makefiles have build rules that look like this: # Special r

[CMake] Escape/quote spaces in ARGS of EXEC_PROGRAM?

Hi folks, I'm trying to run a program via EXEC_PROGRAM, where one of the arguments contains ${CMAKE_CURRENT_BINARY_DIRECTORY}, which may of course contain spaces or other characters that need escaping or quoting. Here's what the cmake block looks like (it's trying to learn the site- packag

Re: [CMake] new rpath support

Thanks Brad for setting my head straight with regard to this (as usual). This is the problem with such a nice cross-platform development tool: though I've never developed on windows (or extensively on linux), CMake makes it so easy to get 95% of the way to a cross-platform build solution.

Re: [CMake] new rpath support

Any help at all would be appreciated. This is all in furtherance of my work in getting shiny new updates to the ITK wrappers working. Thanks again and in advance, Zach On Feb 26, 2006, at 7:46 PM, William A. Hoffman wrote: At 05:01 PM 2/26/2006, Zachary Pincus wrote: Hi folks, A quick quest

[CMake] new rpath support

Hi folks, A quick question about the support for adding custom rpaths (and on darwin, install_names) to shared libraries that Brad is adding to CMake: Is there a windows equivalent to rpaths at all? Will dlls created with these options also be loadable at that rpath? Or is it the case tah

Re: [CMake] Installed project with shared libs

Thanks everyone for your suggestions about how to deal with rpaths (aka install names for OS X dylibs) and installed shared libraries. Option A is to disable the rpaths and make sure that (1) the libraries are installed in a "standard" location, or (2) [DY] LD_LIBRARY_PATH is set to the inst

[CMake] Installed project with shared libs

Hi folks, For the first time ever, I actually installed ITK (built with shard libs) as opposed to using it from the build directory. After installing ITK, I moved the build directory and tried to build and run a project that uses ITK. The project built fine, because the linker saw the ins

[CMake] ITK wrapping: sharing symbols across shared modules

Hi folks, I've been really banging my head against an issue for a day now that I hope someone can help me with. As some may recall, I'm working on updating the wrapper system for ITK. The code is split into several shared modules, so instances created in one module need to work across mod

[CMake] turn CMAKE_SKIP_RPATHS on for one library or one subdirectory

Hi folks, I'm having trouble figuring out how to turn CMAKE_SKIP_RPATH on for a single subdirectory (or for that matter, just one library). I've tried all possible permutations of SET(CMAKE_SKIP_RPATH ON [CACHE BOOL "" [FORCE]]) at the top of the CMakeLists.txt file in my subdirectory, but al

Re: [CMake] Find out current CXX_FLAGS at build time?

CMAKE_C_FLAGS_DEBUG will be used in the Debug configuration of the IDE. So here's the issue: I want to add a custom command that (at build time) gets fed the same flags as the compiler. Say I do the following (modulo errors): ADD_CUSTOM_COMMAND( SOURCE ${input_cxx} COMMAND ${GCCX

Re: [CMake] Find out current CXX_FLAGS at build time?

I'd like to be able to determine what the current CXX_FLAGS are *at build time*. Specifically, the CXX_FLAGS used will change depending on what configuration type is selected in an IDE. Is there a variable that will expand at build time to the proper flags? Does this help ? http://www.cmake.org

[CMake] Find out current CXX_FLAGS at build time?

Hello, I'd like to be able to determine what the current CXX_FLAGS are *at build time*. Specifically, the CXX_FLAGS used will change depending on what configuration type is selected in an IDE. Is there a variable that will expand at build time to the proper flags? This is so I can manua

[CMake] get current INCLUDE_DIRECTORIES list?

Hi folks, Is it possible to get a list of the currently-defined include directories (implicitly included paths, and those explicitly added with INCLUDE_DIRECTORIES) within cmake at configure time? Or failing that, get a variable that expands to whatever make/XCode/VC++ variable stores the

Re:[CMake] CMake: Problem with reading files with semicolons

This is something that would make my life a lot easier too. Here's my use-case: I need to configure a file with a variable number of nearly-identical blocks of text. I would love to read in the "master text" with FILE(READ...), and then modify that text with STRING(CONFIGURE...) several tim

Re: [CMake] CMAKE_CONFIGURATION_TYPES -- still in use? How to use?

10:18 AM, Brad King wrote: Zachary Pincus wrote: Thanks for the explanation of the configuration types system. How does this interact with files installed with INSTALL_FILES(...)? Specifically, do I need to issue a separate INSTALL_FILES command for each configuration type (assuming that the files

Re: [CMake] Strangeness with ARGVn variables

On Jan 26, 2006, at 8:43 AM, Brad King wrote: Zachary Pincus wrote: I'm having some strange issues using the ARGVn variables in macros. Specifically, even when one of those variables has a value, they seem to fail IF tests (and similar). Perhaps this is best illustrated with an ex

[CMake] Strangeness with ARGVn variables

Hi folks, I'm having some strange issues using the ARGVn variables in macros. Specifically, even when one of those variables has a value, they seem to fail IF tests (and similar). Perhaps this is best illustrated with an example: #-- MACRO(foo) IF(ARGV0) MESSAGE("ONE ARGUMENT"

Re: [CMake] Install files at absolute position?

TIES PRE_INSTALL_SCRIPT "$ {CMAKE_CURRENT_BINARY_DIR}/some_pre_install.cmake" POST_INSTALL_SCRIPT "${CMAKE_CURRENT_BINARY_DIR}/ some_post_install.cmake") Then you can put in that file: FILE(INSTALL DESTINATION "/etc" TYPE FILE FILES "/home/andy/ MyProject/my

Re: [CMake] Install files at absolute position?

I'm wondering if there is any good way to have CMake install a particular file at an absolute position in the filesystem (not prefixed by CMAKE_INSTALL_PREFIX) during 'make install'. There is already a bug report about it: http://www.cmake.org/Bug/bug.php?op=show&bugid=2691&pos=3 The cmake de

[CMake] Install files at absolute position?

Hello again, I'm wondering if there is any good way to have CMake install a particular file at an absolute position in the filesystem (not prefixed by CMAKE_INSTALL_PREFIX) during 'make install'. It's clearly possible to send a file to any given location during the configure or build step

Re: [CMake] CMAKE_CONFIGURATION_TYPES -- still in use? How to use?

same)? Or will a command like: INSTALL_FILES(${install_dir} FILES ${whatever}/${CMAKE_CFG_INTDIR}/ source.c) work properly because it is a 'build-time' command? Thanks, Zach On Jan 17, 2006, at 6:10 AM, William A. Hoffman wrote: At 03:55 AM 1/17/2006, Zachary Pincus wrote: Hi Folk

[CMake] CMAKE_CONFIGURATION_TYPES -- still in use? How to use?

Hi Folks, Is the CMAKE_CONFIGURATION_TYPES flag and the associated logic still in use, or has it been deprecated in favor of some other build-type- selection mechanism? I can find precious little information about this online. I'm working on a cmake-driven project which I would like to be

Re: [CMake] non-canonical paths and generated files = error

Bug report filed: #2724, complete with test case. On Jan 15, 2006, at 5:55 AM, Alexander Neundorf wrote: Von: Zachary Pincus <[EMAIL PROTECTED]> No change upon updating to the latest CVS CMake. The error message is now less helpful in that this sort of line is now absent: CMake Error:

Re: [CMake] More distutils-ish FindPythonLibs.cmake?

le command-line switches (e.g. 'python -c' or windows-style switches 'python /C'? Zach On Jan 16, 2006, at 6:13 AM, Brad King wrote: Zachary Pincus wrote: I've been playing with using Python itself within a CMake file to look up include directories for pytho

[CMake] More distutils-ish FindPythonLibs.cmake?

Hi folks, I've been playing with using Python itself within a CMake file to look up include directories for python extensions. (e.g. query the Numeric module within python to find the Numeric C header file's location.) It occurred to me that this might be a better way for FindPythonLibs

[CMake] Get program output in a variable?

Hi guys, I'm trying to make a better CMake script to find the presence of the Numerical Python libraries and their include directories. The easiest way to do this in some cases (e.g. with the newest version of said libraries, now called numpy) is to query the module itself within python.

Re: [CMake] non-canonical paths and generated files = error

/./wrap_BufferConversionPython.cxx but the error remains the same. Should I file a bug? Zach On Jan 14, 2006, at 10:52 AM, Alexander Neundorf wrote: Von: Zachary Pincus <[EMAIL PROTECTED]> ... Hello again, Please try with current cvs and let us know whether it works for you. Sorry that I forgot to speci

Re: [CMake] STRING(CONFIGURE ...) problem with too-early variable substitution

Is there any good way to get the literal '@...@' or '$ {...}' (excluding the quotes) into a CMake variable? You have to escape the @ symbols with a backslash: SET(to_configure "/path/to/[EMAIL PROTECTED]@") In my hands (using a CMake CVS build from a week ago), these lines: SET(bar "baz")

Re: [CMake] non-canonical paths and generated files = error

Hello again, Please try with current cvs and let us know whether it works for you. Sorry that I forgot to specify the version of CMake I've been using. I have a CVS build from about a week ago. Should I cvs update and build it again? That is, did someone just commit a fix for this? Zach

[CMake] STRING(CONFIGURE ...) problem with too-early variable substitution

Hi again folks, I'm trying to use the CMake STRING(CONFIGURE ...) command. For reference, this should 'configure' a string the way that CONFIGURE_FILE does to a file. The general gist of what I want to do is something like SET(to_configure "/path/to/@directory@") and then in a macro: SET(di

[CMake] non-canonical paths and generated files = error

Hi folks, I've run into a minor issue with CMake when a particular file: (a) is a generated file (property explicitly set to GENERATED, or marked as the output of a custom command), (b) has a non-canonical path set (e.g. the path includes '.' or or an empty directory component, such as '/usr