Onsdag 12 oktober 2011 skrev Campbell Barton:
> On Tue, Oct 11, 2011 at 10:50 PM, Yngve Inntjore Levinsen
> wrote:
> > Fredag 07 oktober 2011 skrev Yngve Inntjore Levinsen:
> >> Dear all,
> >>
> >> I have some configuration scripts in python that needs to be run for my
> >> project, so I use the F
Dear CMake Developers,
Can I know which style is more closed to CMake style?
a) CMakeLists.txt and PlatformXXX.cmake for optional platform specific source
lists in same folder.
b) CMakeLists.txt and CMakeListsXXX.cmake in same folder.
Because there are many platform specific files in my project,
On Tue, Oct 11, 2011 at 10:50 PM, Yngve Inntjore Levinsen
wrote:
> Fredag 07 oktober 2011 skrev Yngve Inntjore Levinsen:
>> Dear all,
>>
>> I have some configuration scripts in python that needs to be run for my
>> project, so I use the FindPythonInterp package. This has nicely found the
>> versio
Yes, that did help. Works perfectly without the $ character.
--
Glenn
On 11 October 2011 19:55, Michael Wild wrote:
> On 10/11/2011 06:02 PM, Glenn Coombs wrote:
> > Hi,
> >
> > I've just had a CMakeLists.txt fail to work as expected because somebody
> > was testing to see whether an environme
On Monday 10 October 2011, Robert Dailey wrote:
> I'm using set_source_files_properties() to add COMPILE_DEFINITIONS to a
> single source file. Are these definitions appended to those added via
> target-specific defines, or do they completely replace the existing ones? I
> need them to append, whic
On 10/11/2011 06:02 PM, Glenn Coombs wrote:
> Hi,
>
> I've just had a CMakeLists.txt fail to work as expected because somebody
> was testing to see whether an environment variable was set with the
> syntax: if (DEFINED $ENV{VAR}). This short example shows the problem:
>
> cmake_minimum_required(
As an extreme example, consider using boost's header-only libraries.
If I point external project at a boost tarball, every time I rebuild
(or make clean; make), CMake will re-extract the tarball, which is
quite slow for a tarball with so many files.
Why does CMake re-extract tarballs at all? When
Thanks, that was it.. doh!!!
From: Clinton Stimpson
To: cmake@cmake.org
Sent: Tuesday, October 11, 2011 10:50 AM
Subject: Re: [CMake] Problem with QT3 not generating .cpp files using Cmake
Not sure if this is the whole reason, but it looks like you are missing
Doh :-) Thanks for pointing out what should perhaps have been obvious in
retrospect. Cache variables are one of the more confusing areas of cmake.
--
Glenn
On 10 October 2011 22:38, Bill Hoffman wrote:
> On 10/10/2011 3:52 PM, Robert Dailey wrote:
>
>> Yes, this works perfectly.
>>
>> It's a
I recommend using CTest to drive the tests. You can write a CTest
script that (essentially) only does ctest_test() and ctest_submit().
Then you don't have to worry about tracking the CTest XML format.
If you don't want to do that, you'll need to simulate CTest's start
and test XML and upload it to
Have you tried using ctest -VV or ctest --debug to find out what's really
going on?
tyler
On Mon, Oct 3, 2011 at 4:36 PM, Mike Owens wrote:
> **
> ctest_update(SOURCE "${CTEST_SOURCE_DIRECTORY}" RETURN_VALUE update_result)
> is producing this error.
>
> *Update command failed: "/opt/bin/svn" "
Hi,
I've just had a CMakeLists.txt fail to work as expected because somebody was
testing to see whether an environment variable was set with the syntax: if
(DEFINED $ENV{VAR}). This short example shows the problem:
cmake_minimum_required(VERSION 2.8)
project(foo)
message("HOME: $ENV{HOME}")
if
Not sure if this is the whole reason, but it looks like you are missing the
${SAMPLE_FORMS_CPP} in add_executable().
Clint
On Tuesday, October 11, 2011 09:46:40 am Darrell Langford wrote:
> Okay, the problem I am having is as follows. I am converting a C++ QT3
> program over from using qmake to
Okay, the problem I am having is as follows. I am converting a C++ QT3 program
over from using qmake to cmake and have hit a snag.
The following is my basic layout for the cmakelists.txt file, what happens is,
when the UIC command gets called from the QT_WRAP_UI it doesn't generate out
.cpp fi
This option is valid only for PackageMaker generator. I was not careful
enough when looking at the doc :-[
sorry
Eric
pellegrini a écrit :
Hi all,
I would like to package my application using CPACK/NSIS generator.
Using the following line:
set(CPACK_RESOURCE_FILE_WELCOME
${CMAKE_CURRENT_
Hi!
I am interested in using the CDash (e.g. my.cdash.org) infrastructure for
running tests of a python package. The build steps may not make sense,
especially as the project does not use CMake. However, I have found
instructions online on how to generate the XML expected by CDash, and figured
Hi all,
I would like to package my application using CPACK/NSIS generator.
Using the following line:
set(CPACK_RESOURCE_FILE_WELCOME ${CMAKE_CURRENT_SOURCE_DIR}/README.txt)
has no effect. Indeed, my installer still show at start up the default
wellcome message.
Looking on the web, I found
Fredag 07 oktober 2011 skrev Yngve Inntjore Levinsen:
> Dear all,
>
> I have some configuration scripts in python that needs to be run for my
> project, so I use the FindPythonInterp package. This has nicely found the
> version 2.7 on my system so far, but now it suddenly finds /usr/bin/python
Dear experts,
within our cmake project there are needs to change compilation flags of some
individual files, especially we want sometimes to decrease optimization level.
For that there is a command "set_source_file_properties", but among PROPERTIES,
http://grip.espace-win.net/doc/apps/cmake/cma
19 matches
Mail list logo
