[CMake] Accessing source directory of a target

Hello, Is there a SOURCE_DIR property for targets? I wasn't able to find anything in the documentation on this, however I thought I saw something similar to this a few years ago. I'm using CMake 3.2. Basically I want the equivalent of CMAKE_CURRENT_SOURCE_DIR, but for a specific project. Document

Re: [CMake] output of add_custom_command as target in Makefile

Hooray! Thanks! Could a future version of cmake provide a nicer way to do this, without these error messages? 0 Fri 12:29:25 yost DaveBook ~/p/c++/cmake/custom-command-target/build 391 Z% make foo.cc Scanning dependencies of target foo.cc make[3]: Circular CMakeFiles/foo.cc <- foo.cc dependency

[CMake] option for gcov coverage and overriding optimization flag

I’m having trouble determining the right way to enforce `-O0` optimization level when the user selects a boolean cache entry to enable code coverage with gcov. I tried something like: if ( ENABLE_CODE_COVERAGE ) set ( CMAKE_Fortran_FLAGS “${CMAKE_Fortran_FLAGS} -fprofile-arcs -ftest-coverag

Re: [CMake] Installing systemd service files that point to my installed location

Am 12. Juni 2015 16:46:47 MESZ, schrieb Matthew Karas : >This is probably and XY problem but... > >I'm trying to install a systemd file in my cmake. > >The service file needs to point at the installed destination of my >build after I "make install". > >I was trying to use "CONFIGURE_FILE" > >Whe

Re: [CMake] output of add_custom_command as target in Makefile

If you run "make help" it will list targets it understands. And as you pointed out there is no target for foo.cc. You can "make foo" but if you really want a target for foo.cc you can add one yourself: cmake_minimum_required(VERSION 3.0.0) project(custom-command-target) add_custom_command (

[CMake] Installing systemd service files that point to my installed location

This is probably and XY problem but... I'm trying to install a systemd file in my cmake. The service file needs to point at the installed destination of my build after I "make install". I was trying to use "CONFIGURE_FILE" When I tried to do this - the variable is blank because the configure f

Re: [CMake] output of add_custom_command as target in Makefile

I’m not doing it wrong. Remember, this is a simplified example. We want to be able to make foo.cc so we can look at it and compare it. Yes, we could make foo and then look at foo.cc, but until foo.cc is right, we will suffer a lot of compiler error clutter. When foo.cc looks right, then we will

Re: [CMake] [cmake-developers] Virtual folders in Visual studio get expanded on reload

@kgt: Thank you for this great hint. :-) I had overlooked this button in Visual Studio @mjklaim: I didn't see this behavior in older CMake versions. Roman > -Ursprüngliche Nachricht- > Von: Thompson, KT [mailto:k...@lanl.gov] > Gesendet: Dienstag, 02. Juni 2015 15:52 > An: Roman Wüger; C

[CMake] Problems when creating config files and add_dependencies

Hello, short description: I want to have a configuration header file per unit test. For this purpose I wrote the following function, which creates a header file in “${CURRENT_BINARY_DIR}” and copy all test files into the binary directory. Howewer, I got it to work when I use add_custom_tar

Re: [CMake] output of add_custom_command as target in Makefile

You’re doing it all wrong. You do not name source files as make targets, but the target name (or project name, I have no idea, because it rarely makes sense to name them differently). Try simply “foo” or “custom-command-target”. You would never say “make foo.cpp”, not even in an ordinary GNU Mak