Ah, yes. If only we could add dependencies and pre-/post-build
commands to built-in CMake targets...
http://www.cmake.org/Bug/view.php?id=8438
Absent that, the best I can think of is to just write a custom command
that renames ${CMAKE_BINARY_DIR}/your_package.extension. (I don't know
of a way to q
CPack allows me to configure the basename of the package, but I would like
to be able to change the extension used. I dug around the CPack sources and
it looks like the file extension is baked into the 'virtual const char*
GetOutputExtension() { return ".sh"; }' function. It doesn't look like I
c
On Tue, May 17, 2011 at 1:30 PM, Michael Hertling wrote:
> On 05/17/2011 05:45 PM, Robert Bielik wrote:
> > Hi all,
> >
> > I'm wondering if there's a way to touch files on cached var changes.
> Let's say I have an option to enable or disable a feature
> > in my application, and depending on its s
On 05/17/2011 05:45 PM, Robert Bielik wrote:
> Hi all,
>
> I'm wondering if there's a way to touch files on cached var changes. Let's
> say I have an option to enable or disable a feature
> in my application, and depending on its setting a preprocessor macro is
> defined (or not defined) in the
I do this by making a .in file that gets configured that contains the value
of the CMake variable.
header.h.in:
===
#define FEATURE_X @FEATURE_X@
CMakeLists.txt:
===
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/header.h.in
${CMAKE_CURRENT_BINARY_DIR}/header.h
@ONLY)
include_dire
Hi all,
I'm wondering if there's a way to touch files on cached var changes. Let's say
I have an option to enable or disable a feature
in my application, and depending on its setting a preprocessor macro is defined
(or not defined) in the CMakeLists.txt file:
OPTION(FEATURE_X "Check to enable
Hi David, try to set ( CMAKE_VERBOSE_MAKEFILE true )
2011/5/17 David Aldrich :
> Hi
>
> I would like to see the exact g++ commands that are invoked by a makefile
> generated by cmake. It seems that the usual advice is to use:
>
> make VERBOSE=1
>
> However, the output is then far more verbose th
Hi
I would like to see the exact g++ commands that are invoked by a makefile
generated by cmake. It seems that the usual advice is to use:
make VERBOSE=1
However, the output is then far more verbose than just the g++ commands.
Is there a way to produce less commentary than VERBOSE=1, but mor
Hi Yuri
Thanks for your answer. I chose to use the OPTIMIZED and DEBUG keywords in
target_link_libraries for simplicity.
Best regards
David
From: Yuri Timenkov [mailto:y...@timenkov.ru]
Sent: 17 May 2011 11:57
To: David Aldrich
Cc: cmake@cmake.org
Subject: Re: [CMake] Debug / release build typ
On Tuesday 17 May 2011 14:28:30 Yngve Inntjore Levinsen wrote:
> On Tuesday 17 May 2011 14.01.00 Rolf Eike Beer wrote:
> > Yngve Inntjore Levinsen wrote:
> > > set(CTEST_BUILD_NAME "${osname}-${cpu}-prod")
> > > message("CTEST name: ${CTEST_BUILD_NAME}")
> >
> > You must set the build name before
First off, thanks for an abnormally quick reply! :)
On Tuesday 17 May 2011 14.01.00 Rolf Eike Beer wrote:
> Yngve Inntjore Levinsen wrote:
>
> > set(CTEST_BUILD_NAME "${osname}-${cpu}-prod")
> > message("CTEST name: ${CTEST_BUILD_NAME}")
> >
> > When configuring the message shows the build name
Yngve Inntjore Levinsen wrote:
> set(CTEST_BUILD_NAME "${osname}-${cpu}-prod")
> message("CTEST name: ${CTEST_BUILD_NAME}")
>
> When configuring the message shows the build name I would like to have (or,
> I would understand how to modify it to my liking), but on the CDash web
> page it still sta
Dear developers,
I apologize if this has been answered before. I have just set up CDash and I
noticed that the build name in the report is typically "Linux-c++" or similar.
Now for our project Fortran is the main language, and we want to test on many
different compilers. Hence I would prefer i
The best way is to use imported targets, specifying different locations for
each configuration (
http://www.cmake.org/Wiki/CMake/Tutorials/Exporting_and_Importing_Targets).
Or simply use OPTIMIZED and DEBUG keywords in target_link_libraries (see
command help).
On Tue, May 17, 2011 at 1:42 PM, Dav
Hi
My understanding is that cmake will automatically set the compiler flags based
on CMAKE_BUILD_TYPE. I am wondering whether there is a clean way of specifying
debug / release 'extra' libraries such that cmake will select the appropriate
library at link time?
Currently I use this code to lin
OK, thanks for the info. I think for simplicity I won't worry about
merging and just resubmit the particular test - even if it means that
test shows up twice on the dashboard.
---
Neil
On 16/05/11 22:50, David Cole wrote:
Everytime you run ctest -D ExperimentalTest, ctest writes a Test.xml
fi
Hi all,
I'm having a problem with cmake giving me an error about attempting to
add a Boost library to a target. However, I have confirmed that my
CMakeLists.txt works fine in 2.8.2 and 2.8.4; however, it doesn't work
in 2.8.0. Unfortunately, I'm trying to get it work on a machine
running on 2.8.
Hej Will,
I'm not sure if this is the proper way to reply and I haven't checked
your second mail with the attachment. But I think in #3 you're
definitely doing something wrong. It took me quite a while to figure
out, because the documentation is rather sparse, but whenever there is a
hdf5-conf
18 matches
Mail list logo
