Thanks! That's clearer now. I guess using a separate build
subdirectory has an advantage in that if something goes wrong you can
just scrub that whole subdirectory and try again.
a couple of dead links from http://www.cmake.org/Wiki/CMake#Tutorials
- the following give 404:
http://snikt.net/index
On 08/24/2012 11:09 AM, Andreas Pakulat wrote:
> Hi,
>
> On Fri, Aug 24, 2012 at 7:27 PM, Adam B wrote:
>> Hello all,
>>
>> I'm relatively new to CMake but I've encountered some unexpected behavior.
>> Perhaps it's by design or perhaps it's a bug - you tell me. The short story
>> is this:
> It is
2012/8/24 Russell Wallace :
> Hi,
>
> I'm trying to get up and running with CMake for a project I'm working
> on. The online documentation seems to describe how to write the
> script/configuration files; I'm trying to first get my head around a
> more basic overview.
There several CMake tutorials
On Friday 24 August 2012, Russell Wallace wrote:
> Hi,
>
> I'm trying to get up and running with CMake for a project I'm working
> on. The online documentation seems to describe how to write the
> script/configuration files; I'm trying to first get my head around a
> more basic overview.
>
> Supp
Hi,
I'm trying to get up and running with CMake for a project I'm working
on. The online documentation seems to describe how to write the
script/configuration files; I'm trying to first get my head around a
more basic overview.
Suppose I have a minimal project called foo, that just consists of a
Hi,
On Fri, Aug 24, 2012 at 7:27 PM, Adam B wrote:
> Hello all,
>
> I'm relatively new to CMake but I've encountered some unexpected behavior.
> Perhaps it's by design or perhaps it's a bug - you tell me. The short story
> is this:
It is a bug, but not in CMake, its in your cmake code.
> It ap
Adam B wrote:
> Hello all,
>
> I'm relatively new to CMake but I've encountered some unexpected behavior.
> Perhaps it's by design or perhaps it's a bug - you tell me. The short
> story is this:
>
> It appears that add_custom_command() is ignored if the only OUTPUT is a C
> header file (.h). T
Hello all,
I'm relatively new to CMake but I've encountered some unexpected behavior.
Perhaps it's by design or perhaps it's a bug - you tell me. The short story is
this:
It appears that add_custom_command() is ignored if the only OUTPUT is a C
header file (.h). The generated makefiles do n
On Fri, Aug 24, 2012 at 10:42 AM, David Cole wrote:
> On Fri, Aug 24, 2012 at 9:46 AM, Davide Mancusi wrote:
>>
>> Hello everyone,
>>
>> I have tried asking this question on stackoverflow [1] without much
>> luck, so here we go:
>>
>> My project links to a third-party library that comes with a va
On Fri, Aug 24, 2012 at 9:46 AM, Davide Mancusi wrote:
>
> Hello everyone,
>
> I have tried asking this question on stackoverflow [1] without much
> luck, so here we go:
>
> My project links to a third-party library that comes with a valgrind
> suppression file, as well as a CMake script. The scri
2012/8/24 Jason T. Slack-Moehrle :
> Hi Eric,
>
>>> OS X 10.8, CMAKE 2.8.9.
>>>
>>> In CMAKE 2.8.9 it seems that CMAKE_FILES_DIRECTORY
>>>
>>> SET( PROJECT_BINARY_DIR "." )
>>> SET( CMAKE_FILES_DIRECTORY ${PROJECT_BINARY_DIR}/output/CMakeFiles )
>>> SET( EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR
Hi Eric,
>> OS X 10.8, CMAKE 2.8.9.
>>
>> In CMAKE 2.8.9 it seems that CMAKE_FILES_DIRECTORY
>>
>> SET( PROJECT_BINARY_DIR "." )
>> SET( CMAKE_FILES_DIRECTORY ${PROJECT_BINARY_DIR}/output/CMakeFiles )
>> SET( EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}/bin )
>>
>> I dont see an 'output/CMakeFile
Then I cannot use the subproject separation, right?
It seems this is "feature" that got lost with the new style:
http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Continuous_Builds_.28old_Style.29
Michele
On Fri, Aug 24, 2012 at 3:51 PM, David Cole wrote:
> On Fri, Aug 24, 2012 at 9:45 AM, Mi
Hello everyone,
I have tried asking this question on stackoverflow [1] without much
luck, so here we go:
My project links to a third-party library that comes with a valgrind
suppression file, as well as a CMake script. The script stores the
location of the suppression file in a CMake cache variab
On Fri, Aug 24, 2012 at 9:45 AM, Michele Dolfi wrote:
>
>
> On Fri, Aug 24, 2012 at 3:24 PM, David Cole wrote:
>
>>
>>> On Aug 24, 2012, at 9:01, Michele Dolfi wrote:
>>>
>>> > Hi all,
>>> >
>>> > I started using CMake, CTest and CDash, with the simple targets
>>> Nightly, Continuous and Experim
On Fri, Aug 24, 2012 at 3:24 PM, David Cole wrote:
>
>> On Aug 24, 2012, at 9:01, Michele Dolfi wrote:
>>
>> > Hi all,
>> >
>> > I started using CMake, CTest and CDash, with the simple targets
>> Nightly, Continuous and Experimental: it works very well.
>> > Now I would like to divide my project
On Fri, Aug 24, 2012 at 9:34 AM, Leif Walsh wrote:
> They are generated from facts I detect about the os
>
>
Ah ok. Better then. :-)
You could do the same thing in a ctest script. A lot of the projects we
work on at Kitware share a "common" script for the project that is included
by all the
They are generated from facts I detect about the os
Sent from my iPhone
On Aug 24, 2012, at 9:24, David Cole wrote:
>
>
> On Fri, Aug 24, 2012 at 9:07 AM, Leif Walsh wrote:
> I set the build name and site in my CMakeLists.txt before calling
> include(CTest) and it works.
>
>
> But then yo
On Fri, Aug 24, 2012 at 9:07 AM, Leif Walsh wrote:
> I set the build name and site in my CMakeLists.txt before calling
> include(CTest) and it works.
>
>
But then you can only submit dashboards from one site with that CMakeLists
file...? Anybody else submitting a dashboard for your project will p
I set the build name and site in my CMakeLists.txt before calling
include(CTest) and it works.
Sent from my iPhone
On Aug 24, 2012, at 9:01, Michele Dolfi wrote:
> Hi all,
>
> I started using CMake, CTest and CDash, with the simple targets Nightly,
> Continuous and Experimental: it works ve
Hi all,
I started using CMake, CTest and CDash, with the simple targets Nightly,
Continuous and Experimental: it works very well.
Now I would like to divide my project in subproject, so that a failure in
compiling one small test is not affecting the full dashboard report. I read
that ctest driver
2012/8/24 hce :
> Hi,
>
> i use install(FILE ..) to install a configuration file config.txt by both
> RPM packages A.rpm and B.rpm, due to the name and version in config.txt, the
> config.txt is not exactly the same in A.rpm and B.rpm. Now I've got an file
> conflict error when A.rpm was installed,
Hi,
i use install(FILE ..) to install a configuration file config.txt by both
RPM packages A.rpm and B.rpm, due to the name and version in config.txt, the
config.txt is not exactly the same in A.rpm and B.rpm. Now I've got an file
conflict error when A.rpm was installed, B.rpm failed the installat
2012/8/24 Jason T. Slack-Moehrle :
> Hello
>
> OS X 10.8, CMAKE 2.8.9.
>
> In CMAKE 2.8.9 it seems that CMAKE_FILES_DIRECTORY
>
> SET( PROJECT_BINARY_DIR "." )
> SET( CMAKE_FILES_DIRECTORY ${PROJECT_BINARY_DIR}/output/CMakeFiles )
> SET( EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}/bin )
>
> I don
24 matches
Mail list logo
