Re: [CMake] Configuration issues on AIX

2018-02-28 19:04 GMT+01:00 Brad King : > On 02/28/2018 12:59 PM, Jakob Reschke wrote: >> Yes, I have seen the builds mentioned somewhere, which gives me hope >> that it could be fixed on our machines. > > You could also try bootstrapping CMake from source. Doing so with >

Re: [CMake] Configuration issues on AIX

On 02/28/2018 12:59 PM, Jakob Reschke wrote: > Yes, I have seen the builds mentioned somewhere, which gives me hope > that it could be fixed on our machines. You could also try bootstrapping CMake from source. Doing so with GNU on AIX is supported. -Brad -- Powered by www.kitware.com Please

Re: [CMake] Configuration issues on AIX

2018-02-28 13:22 GMT+01:00 Brad King : > On 02/27/2018 11:30 AM, Jakob Reschke wrote: >> I followed this up to the file(STRING ...) command ... seems >> unable to grep any strings out of any file: > > Strange. That will need to be solved before anything can be > expected to

Re: [CMake] Configuration issues on AIX

On 02/27/2018 11:30 AM, Jakob Reschke wrote: > I followed this up to the file(STRING ...) command ... seems > unable to grep any strings out of any file: Strange. That will need to be solved before anything can be expected to work. Where did you get the CMake binary? FYI we've had nightly

Re: [CMake] Configuration under CMake 3.10.1 fails but succeeds with 3.9.6

On 2017-12-14 13:51-0500 Michael Jackson wrote: I just tried out the latest CMake release 3.10.1 and it fails to configure (from a clean build directory) our project where CMake 3.9.x and below (down to CMake 3.7.x) configures it completely and correctly. The configure error I get is" --

Re: [CMake] configuration packages, IMPORTED targets, and global scope

Thanks, I am watching that discussion and will try to contribute where I can. On Thu, Sep 7, 2017 at 4:02 AM, Deniz Bahadir wrote: > Am 06.09.2017 um 20:24 schrieb Robert Dailey: >> >> So it took me a while to figure out why find_package() calls I was >> making (with CONFIG)

Re: [CMake] configuration packages, IMPORTED targets, and global scope

Am 06.09.2017 um 20:24 schrieb Robert Dailey: So it took me a while to figure out why find_package() calls I was making (with CONFIG) option were not accessible outside of the directory in which it was invoked. I realized that all targets seem to be global by default except IMPORTED targets

Re: [CMake] Configuration packages & versioning for parallel installations

Hi, On Thu, Sep 7, 2017 at 12:26 AM, Robert Dailey wrote: > First obvious question is: Should this even be a concern? Yes, definitely! > The > cmake-packages documentation doesn't really touch on versioning, but > there are a couple of concerns I see when you

Re: [CMake] Configuration dependent link

Hey all, I have a few more findings about this before I finally give up and resort my old self made approach: It looks to me like the imported target mechanism is not propagating properties the way it could and probably should. Es specially not like it is described here:

Re: [CMake] Configuration dependent link

I have investigated further into this and still have no solution, but a hint, which anyone may be able to confirm. It appears like I was led astray by a number of bugs in target_link_libraries() which I was mistaking for intentional behavior and so I started to re-create the behavior manually.

Re: [CMake] Configuration specific COMPILE_FLAGS?

Giordano Khouri wrote: I'm surprised to see that there's no configuration specific COMPILE_FLAGS. Please correct me if I'm wrong. Correct, but not the whole story. When you upgrade to CMake 2.8.12 you can use the COMPILE_OPTIONS target property.

Re: [CMake] Configuration specific COMPILE_FLAGS?

On 10/10/2013 09:19 PM, Giordano Khouri wrote: I'm surprised to see that there's no configuration specific COMPILE_FLAGS. Please correct me if I'm wrong. *Khouri Giordano* Software Technology Researcher Nikon Inc. 1300 Walt Whitman Road Melville NY 11747-3064 Office:

Re: [CMake] configuration of VTK 5.8 using cmake 2.6 on 64-bit windows 7

On Thu, Dec 8, 2011 at 10:51 PM, rakesh patil prakeshoffic...@gmail.com wrote: Hello, I want to compile VTK 5.8 for 64bit windows machine. I have cmake 2.6 for 32-bit windows. I downloaded vtk source code from www.vtk.org website. While configuring, I select Visual Studio 9(64) and continued

Re: [CMake] configuration of VTK 5.8 using cmake 2.6 on 64-bit windows 7

Ok fine.. anyways, with _WIN64 flag mpistub.lib is not being generated in VTK .. so I have no option then to use win32 flag.. But what about my first question? can i use 32bit version of cmake on 64-bit windows to configure 64bit mode of VTK ??? Thanks On Fri, Dec 9, 2011 at 9:25 AM, John

Re: [CMake] configuration of VTK 5.8 using cmake 2.6 on 64-bit windows 7

Sorry!! Pardon me.. I didnt read the reply completely.. Answer lies in there itself... :) Thanks... On Fri, Dec 9, 2011 at 9:25 AM, John Drescher dresche...@gmail.com wrote: On Thu, Dec 8, 2011 at 10:51 PM, rakesh patil prakeshoffic...@gmail.com wrote: Hello, I want to compile VTK 5.8

Re: [CMake] configuration based add_custom_command

Michael Wild skrev 2011-08-23 11:29: The easiest way around this I can see is to wrap the command in a CMake-script like this: add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/someFile.txt COMMAND ${CMAKE_COMMAND} -DCONFIG=$CONFIGURATION

Re: [CMake] configuration based add_custom_command

On 08/24/2011 11:04 AM, Robert Bielik wrote: Michael Wild skrev 2011-08-23 11:29: The easiest way around this I can see is to wrap the command in a CMake-script like this: add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/someFile.txt COMMAND ${CMAKE_COMMAND}

Re: [CMake] configuration based add_custom_command

Michael Hertling skrev 2011-08-24 13:13: Suppose ADD_CUSTOM_COMMAND(OUTPUT source.c CONFIGURATION Release COMMAND ...) ADD_EXECUTABLE(main ... source.c) and then: cmake -DCMAKE_BUILD_TYPE=Debugpath/to/source How would you like this case to be handled by CMake? Note that with multi-config

Re: [CMake] configuration based add_custom_command

Robert Bielik skrev 2011-08-24 13:43: Michael Hertling skrev 2011-08-24 13:13: Suppose ADD_CUSTOM_COMMAND(OUTPUT source.c CONFIGURATION Release COMMAND ...) ADD_EXECUTABLE(main ... source.c) and then: cmake -DCMAKE_BUILD_TYPE=Debugpath/to/source How would you like this case to be handled by

Re: [CMake] configuration based add_custom_command

On Wed, Aug 24, 2011 at 7:47 AM, Robert Bielik robert.bie...@xponaut.se wrote: Robert Bielik skrev 2011-08-24 13:43: Michael Hertling skrev 2011-08-24 13:13: Suppose ADD_CUSTOM_COMMAND(OUTPUT source.c CONFIGURATION Release COMMAND ...) ADD_EXECUTABLE(main ... source.c) and then: cmake

Re: [CMake] configuration based add_custom_command

On 08/24/2011 01:47 PM, Robert Bielik wrote: Robert Bielik skrev 2011-08-24 13:43: Michael Hertling skrev 2011-08-24 13:13: Suppose ADD_CUSTOM_COMMAND(OUTPUT source.c CONFIGURATION Release COMMAND ...) ADD_EXECUTABLE(main ... source.c) and then: cmake

Re: [CMake] configuration based add_custom_command

Michael Hertling skrev 2011-08-24 14:49: Anyway, I didn't want to discuss this particular detail; my point is: Configuration-selective custom commands possibly have far-reaching consequences which should be carefully reasoned out. I see your point. This would be a good thing to do, however, as

Re: [CMake] configuration based add_custom_command

On Wed, Aug 24, 2011 at 10:39 AM, Robert Bielik robert.bie...@xponaut.se wrote: Michael Hertling skrev 2011-08-24 14:49: Anyway, I didn't want to discuss this particular detail; my point is: Configuration-selective custom commands possibly have far-reaching consequences which should be

Re: [CMake] configuration based add_custom_command

On Tue 23 Aug 2011 11:21:07 AM CEST, Robert Bielik wrote: I'm trying to setup a custom command to be executed during Release build only (Xcode) using CMake 2.8.4, but I cannot find any configuration based options to ADD_CUSTOM_COMMAND ? Workarounds ? TIA /Rob The easiest way around this I

Re: [CMake] Configuration environment variable for VS

I discovered at least for a custom command that ${CMAKE_CFG_INTDIR} expanded to $(OutDir) not $(IntDir). Interestingly enough $(OutDir) was Debug and $(IntDir) was project.dir/Debug. At any rate, I think what I wanted was this: # Figure out which configure we will use and pass that in as an

Re: [CMake] Configuration environment variable for VS

On Fri, May 15, 2009 at 1:59 AM, James Bigler jamesbig...@gmail.com wrote: Is there a configuration environment variable for VS that I could use to change the behavior of an add_custom_command based on whether I'm building a debug or release build? I want something like this:

Re: [CMake] Configuration environment variable for VS

If you use ${CMAKE_CFG_INTDIR} in a custom command it should show up as $(Config) in the generated VS vcproj files... Does this do what you want? add_custom_command(${OUTPUT_FILE} COMMAND ${CMAKE_COMMAND} ARGS -DCONFIG:STRING=${CMAKE_CFG_INTDIR} -P ${my_custom_script} ) For makefile based

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND

Sendt: ti 11-03-2008 16:54 Til: cmake@cmake.org Emne: Re: [CMake] configuration specific ADD_CUSTOM_COMMAND Yes just use something like: IF ( ${CMAKE_BUILD_TYPE} STREQUAL Debug ) ENDIF ( ${CMAKE_BUILD_TYPE} STREQUAL Debug ) For generation Makefiles this could work. But what about MSVS project

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Lütken The problem I suppose is that CMake is running before MSVC and thus have no way of knowing which configuration you will choose unless you tell so when generating the project. Actually I consider this a bug, or a

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND

Zschocke, Florian wrote: From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Lütken The problem I suppose is that CMake is running before MSVC and thus have no way of knowing which configuration you will choose unless you tell so when generating the project. With the use

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND

From: Bill Hoffman [mailto:[EMAIL PROTECTED] With the use of CMAKE_CFG_INTDIR, you should be able to get to the targets you need inside custom commands with the multiconfiguration build systems. Have you tried CVS CMake, I think that the LOCATION of the target includes CMAKE_CFG_INTDIR in

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND

Zschocke, Florian wrote: From: Bill Hoffman [mailto:[EMAIL PROTECTED] With the use of CMAKE_CFG_INTDIR, you should be able to get to the targets you need inside custom commands with the multiconfiguration build systems. Have you tried CVS CMake, I think that the LOCATION of the target

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND (was: Target properties LOCATION and DEBUG_POSTFIX)

Hi! I'm trying this again from a different angle: Is it possible to add a custom command only for a specific configuration, i.e. build type? So I could add a certain command only for DEBUG and a different one for RELEASE? Thanks, Florian Zschocke -Original Message- From: [EMAIL

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND (was: Target properties LOCATION and DEBUG_POSTFIX)

Yes just use something like: IF ( ${CMAKE_BUILD_TYPE} STREQUAL Debug ) ENDIF ( ${CMAKE_BUILD_TYPE} STREQUAL Debug ) IF ( ${CMAKE_BUILD_TYPE} STREQUAL Release ) ENDIF ( ${CMAKE_BUILD_TYPE} STREQUAL Release ) -Martin Lutken On Tuesday 11 March 2008 10:16:32 Zschocke, Florian wrote: Hi! I'm

Re: [CMake] configuration specific ADD_CUSTOM_COMMAND

Yes just use something like: IF ( ${CMAKE_BUILD_TYPE} STREQUAL Debug ) ENDIF ( ${CMAKE_BUILD_TYPE} STREQUAL Debug ) For generation Makefiles this could work. But what about MSVS project files? My understanding was that this wouldn't work since the CMAKE_BUILD_TYPE will not be used in

Re: [CMake] Configuration

Camek, Alexander a écrit : Hi Alex, In my configure.h.cmake: #cmakedefine SYSTEM_NAME In my ... Did you have a look at ${CMAKE_SYSTEM_NAME} ? Yes I had, but when I write in the configure.h.cmake #cmakedefine ${CMAKE_SYSTEM_NAME} then the result after the configure_file is this:

RE: [CMake] Configuration

Thanks to all. Yes I had, but when I write in the configure.h.cmake #cmakedefine ${CMAKE_SYSTEM_NAME} then the result after the configure_file is this: /* #undef Windows */. You have to do: #cmakedefine CMAKE_SYSTEM_NAME But I think you want this: #define THE_SYSTEM_NAME

Re: [CMake] Configuration

On Thursday 26 July 2007 10:43, you wrote: Hi Alex, In my configure.h.cmake: #cmakedefine SYSTEM_NAME In my CMakeLists.txt: CHECK(system SYSTEM_NAME) CONFIGURE_FILE(configure.h.cmake configure.h) Is something like this possible? Did you have a look at

RE: [CMake] Configuration

Hi Alex, In my configure.h.cmake: #cmakedefine SYSTEM_NAME In my CMakeLists.txt: CHECK(system SYSTEM_NAME) CONFIGURE_FILE(configure.h.cmake configure.h) Is something like this possible? Did you have a look at ${CMAKE_SYSTEM_NAME} ? Yes I had, but when I

Re: [CMake] configuration input to cmake

Thanks for the pointers. It makes a lot of sense to me. Jun On Sat, May 12, 2007 at 10:09:15AM +0200, Eric Noulard wrote: 2007/5/12, Jun Sun [EMAIL PROTECTED]: On Fri, May 11, 2007 at 01:38:26PM -0400, Bill Hoffman wrote: Guilherme Balena Versiani wrote: Jun Sun escreveu: My build

Re: [CMake] configuration input to cmake

Hello Jun Sun, I hope now I understood your question. First, let compare auto-tools to cmake: the three main steps involved in building the system are about the same (though the cmake seems to use a better cache system than 'configure' and it generates a something optimized set of GNU

Re: [CMake] configuration input to cmake

2007/5/12, Jun Sun [EMAIL PROTECTED]: On Fri, May 11, 2007 at 01:38:26PM -0400, Bill Hoffman wrote: Guilherme Balena Versiani wrote: Jun Sun escreveu: My build process involves a configuration stage. It roughly looks like this: * Generate cmakefile.inc and config.h from .config file

Re: [CMake] configuration input to cmake

AFAIK using cmake involves basically two steps: 1) something like configure generate build files (GNU Makefile, MSVC, KDevelop3, XCode, etc). For a tipical 'out-of-source' building: # mkdir build_dir # cmake ../source_dir 2) build software: # make Optionally, you can have a 'make

Re: [CMake] configuration input to cmake

Guilherme Balena Versiani wrote: Jun Sun escreveu: My build process involves a configuration stage. It roughly looks like this: * Generate cmakefile.inc and config.h from .config file You may also want to look at the configure_file command. -Bill

Re: [CMake] configuration input to cmake

Thanks for the pointer. But I was referring to the configuration for the cmake itself. For example, one build may include module A and another build may not include module B instead. Now thing about it, what is the recommanded way of achieving this goal? I can thinking of two ways: 1. Pass

Re: [CMake] configuration input to cmake

On Fri, May 11, 2007 at 01:38:26PM -0400, Bill Hoffman wrote: Guilherme Balena Versiani wrote: Jun Sun escreveu: My build process involves a configuration stage. It roughly looks like this: * Generate cmakefile.inc and config.h from .config file You may also want to look at the