[CMake] Remove a library from linking which was added with target_link_libraries

Dear CMake-users, is it possible to remove a library which is linked to a target. The library linkage was added with the target_link_libraries command. Because of that this command gets called by a third party cmake script removing the command call is not an option. Do you have any ideas? Than

Re: [CMake] configuration based add_custom_command

On Wed, Aug 24, 2011 at 10:39 AM, Robert Bielik 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 carefully reasoned out

Re: [CMake] Error running link command: Bus error

On Tue, Aug 23, 2011 at 5:48 AM, Patrick Gampp wrote: > What is your environment like? The Tutorial steps run on all of our > CMake dashboards, and we have several "Unix Makefiles" dashboards > running on various Macs. We do not see this error anywhere... > > > Mac Hardware: >   Model Name: Mac mi

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

[CMake] WORKING_DIRECTORY from add_custom_target() not setting current directory on windows

Hi all, the WORKING_DIRECTORY from add_custom_target() does change the current directory properly on windows, if the current directory and the directory specified in WORKING_DIRECTORY reside on different drives. I experienced that with the following command: add_custom_target(doc echo "***

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 -DCMAKE_BU

Re: [CMake] configuration based add_custom_command

On Wed, Aug 24, 2011 at 7:47 AM, 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: >>> >>>

Re: [CMake] [CMAKE] Problem when moving an executable with a shared library

On 08/23/2011 06:11 PM, Renato Utsch wrote: > Hello CMake Experts! > > I don't know if it's here that I have to ask, so if I'm wrong, please tell > me. > > > I'm having a problem with CMake. Let me explain: > > I use CMake to build a program and a shared library (let me say, "hello" and > "libh

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=Debug How would you like this case to be handled by CMake? Note th

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=Debug How would you like this case to be handled by CMake? Note that with multi-config generators, the bu

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} >> -DCONFI

Re: [CMake] INSTALL and Up-to-date problem

On 08/24/2011 11:00 AM, Florian Stinglmayr wrote: > Hello List! > > I have a rather unusual setup of graphic files: > > someexe/gfx/ > -- *.png > -- variant1 > -- -- subvariant1 > -- -- -- *.png > -- variant1 > -- -- subvariant2 > -- -- --*.png > -- variant2 > etc. > > So I have a general graphi

[CMake] cdash e-mail configuration

Dear all, I feel a bit ignorant for asking this, but how do I get cdash to send e-mails? In the installation instructions it only states how to change default sent- from and reply-to addresses, but what do I need to actually configure on the server? My server is not sending out anything :( Than

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=$ -DOUTPUT=${CMAKE_CURRENT_BINARY_DIR}/someFile.txt

[CMake] INSTALL and Up-to-date problem

Hello List! I have a rather unusual setup of graphic files: someexe/gfx/ -- *.png -- variant1 -- -- subvariant1 -- -- -- *.png -- variant1 -- -- subvariant2 -- -- --*.png -- variant2 etc. So I have a general graphics folder, and for specific variants of the software -- and its sub variants -- sp

Re: [CMake] CDT4 generator: source path configured incorrectly

On 23.08.2011 18:50, Alexander Neundorf wrote: > Please create an entry in the cmake bug tracker at > http://public.kitware.com/Bug Thanks, Simon ___ Powered by www.kitware.com Visit other Kitware o