That's really more of a job for source control
if you add like if( exists ) for each potential file you want
to experiment with it could be done.
On Fri, Oct 23, 2015 at 2:07 AM, Johannes Zarl-Zierl
wrote:
> Hi,
>
> For header files, that's quite a normal thing to do - you just need to add
The command "add_dependencies" [0] only works on targets.
See the CMake Tutorial for how to generate files as part of the build
that later targets rely on. [1].
[0] https://cmake.org/cmake/help/v2.8.12/cmake.html#command:add_dependencies
[1] https://cmake.org/cmake-tutorial/#s5
On Fri, Oct 23,
Hey,
I'm at a loss here:
I have a command that's run with add_custom_command(). I need to run it
before compiling a library that I add with add_library(), because it
generates some header files.
This was my first try:
file1:
{{{
add_custom_command(
OUTPUT foo.hpp
COMMAND bar
)
}}}
file
Is there a way of tracking the time individual compiles take using cmake?
What I am after is a cmake variable to set, or a cmake invocation option
that will in the end generate Makefiles that output the time it takes for
each compile/link. I am trying to track down a build performance issue and
ha
That was it, I had to replace
MAP_IMPORTED_CONFIG_COVERAGE
with
MAP_IMPORTED_CONFIG_NONE
as I have
set(CMAKE_BUILD_TYPE NONE)
I hope this is useful to others.
On Fri, Oct 23, 2015 at 9:38 AM, Tom Kacvinsky wrote:
> Here is what I tried for Qt4 (that is what I am using), using cmake
Here is what I tried for Qt4 (that is what I am using), using cmake 3.3.2
on Windows 7
find_package(Qt4 4.8.5 REQUIRED QtCore QtGui QtXml Qt3Support QtWebKit
QtSql QtSvg QtNetwork QAxContainer)
set_target_properties(Qt4::QtCore PROPERTIES MAP_IMPORTED_CONFIG_COVERAGE
"DEBUG")
set_target_pro
On 10/07/2015 12:45 PM, Orion Poplawski wrote:
> There also appears to be a similar issue with building Paraview where the
> MPI_INLCUDE_PATH is no longer being passed to the compile line.
Can you provide any more detail on this problem? There was only one
change to FindMPI between 3.3.2 and 3.4.
Hi,
For header files, that's quite a normal thing to do - you just need to add the
CMAKE_CURRENT_BINARY_DIR to your include directories.
For .cpp files, you can write your target so that it is referencing the source
file in the binary directory. I.e.:
configure_file(
${CMAKE_CURRENT_SOURCE_D
