On 22. Jul, 2010, at 8:38 , norulez wrote:
> How can I find out which build type is used? Because if I didn't define
> CMAKE_BUILD_TYPE, this variable is uninitialized.
That depends. For single-configuration generators (i.e. Makefile based), the
user has to set CMAKE_BUILD_TYPE. If it is empty
How can I find out which build type is used? Because if I didn't define
CMAKE_BUILD_TYPE, this variable is uninitialized.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Plea
On 22. Jul, 2010, at 3:09 , Michael Hertling wrote:
> On 07/21/2010 10:26 AM, Michael Wild wrote:
>>
>> On 21. Jul, 2010, at 9:56 , Marcel Loose wrote:
>>
>>> On Tue, 2010-07-20 at 09:18 -0700, Alan W. Irwin wrote:
On 2010-07-20 17:12+0200 Michael Hertling wrote:
> On 07/20/2010
Am Thursday 22 July 2010 schrieb norulez:
> This shouldn't work, because you could build deb packages on redhat systems
> with cpack without any deb tools installed
Well, in that case you don't need to search for anything debian-like and can
always use that generator. Then you only need to check
This shouldn't work, because you could build deb packages on redhat systems
with cpack without any deb tools installed
Am 22.07.2010 um 08:02 schrieb Rolf Eike Beer :
> Am Thursday 22 July 2010 schrieb Freddie Witherden:
>
>> I wish to know how I can have CMake/CPack determine if it is possible
Am Thursday 22 July 2010 schrieb Freddie Witherden:
> I wish to know how I can have CMake/CPack determine if it is possible to
> build an RPM or DEB package on the system (so if all the required
> utilities are installed) and if so to go ahead and package them.
FIND_PROGRAM(rpmbuild) or things li
On 07/21/2010 10:46 PM, Hickel, Kelly wrote:
>
>> -Original Message-
>> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
>> Behalf Of Verweij, Arjen
>> Sent: Wednesday, July 21, 2010 3:43 PM
>> To: cmake@cmake.org
>> Subject: Re: [CMake] how to set ar/ranlib flags per targ
On 07/21/2010 10:26 AM, Michael Wild wrote:
>
> On 21. Jul, 2010, at 9:56 , Marcel Loose wrote:
>
>> On Tue, 2010-07-20 at 09:18 -0700, Alan W. Irwin wrote:
>>> On 2010-07-20 17:12+0200 Michael Hertling wrote:
>>>
On 07/20/2010 03:26 AM, Alan W. Irwin wrote:
> On 2010-07-20 00:51+0200 Mi
Hi,
I am trying to do cross-compiling with CMake for IAR compiler (ARM).
My main problem with the current CMake 2.8.2 is the complain about -c option
from IAR compiler. IAR compiler does not accept -c as input C file and the
sysntax is CC .c [options]. How can I tell CMake not to put -c when
Hi,
I use CPack in my project to build binary packages as an alternative to `make
install`. However, I am interested in getting my project to automatically
detect which packages to build.
Currently I have TGZ set and then require the user to pass the appropriate
parameter to `cmake` (such as
Due to ABI differences, over the years we have
installed libraries under subdirs named after the
compiler group (gcc, xlc, ...). For this we need
to figure out what compiler might be inside a compiler
wrapper (like CC on the cray, whatever in mpicc, etc.)
Are there general strategies or modules
Well the thread you reference asks the TS to submit a bug in Mantis. Was such a
bug ever submitted?
I did a quick check and I can't find one using several queries.
No other ideas for fixing your problem except for wrapping add_library to
include 32/64 bit argument.
Regards,
Arjen
>-Origin
Hi,
>The generators are testing and inspecting the toolchain.
>Something is not building as expected so it reports the
>problem up front rather than waiting for some subtle
>error when building the main project.
OK.
>> "NMake Makefiles JOM"
>[snip]
>> -- FIXME: altered Windows.cmake for debuggin
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
> Behalf Of Verweij, Arjen
> Sent: Wednesday, July 21, 2010 3:43 PM
> To: cmake@cmake.org
> Subject: Re: [CMake] how to set ar/ranlib flags per target
>
> Kelly,
>
> I suffer from the same problem an
Kelly,
I suffer from the same problem and solved it like this:
SET(CMAKE_C_ARCHIVE_CREATE " -X64 cr ")
SET(CMAKE_C_ARCHIVE_APPEND " -X64 r")
SET(CMAKE_C_ARCHIVE_FINISH " -X64 ")
SET(CMAKE_CXX_ARCHIVE_CREATE ${CMAKE_C_ARCHIVE_CREATE})
SET(CMAKE_CXX_ARCHIVE_APPEND ${CMAKE_C_ARCHIVE_APPEND})
S
Hello,
I'm using CMake 2.8.1, and have a problem on AIX similar to this one:
http://web.archiveorange.com/archive/v/5y7PkUbT6iizO31eshQa .
I have the additional complication of needing to build both 32 and 64
bit libraries from the same set of CMake files.
I've tried a number of things (list be
On 21. Jul, 2010, at 18:59 , Alan W. Irwin wrote:
> On 2010-07-21 08:50-0700 Alan W. Irwin wrote:
>
>> To draw this subthread to a definite conclusion, here is what works
>> for me now to get python version for either python2 or python3.
>>
>> softw...@raven> python -c \
>> 'import sys; print("
2010/7/21 Olaf van der Spek :
> On Wed, Jul 21, 2010 at 5:39 PM, Droscy wrote:
>> Hi Olaf,
>>
>> Olaf van der Spek ha scritto:
>>> Could this be changed to "xbt-tracker_0.1.1_i386.deb"?
>>>
>> I'm using the following code to obtain a correct debian-name
>
> Looks good, but this should really be pa
On 07/21/2010 10:32 AM, Verweij, Arjen wrote:
> Is it normal for generators to be this picky?
The generators are testing and inspecting the toolchain.
Something is not building as expected so it reports the
problem up front rather than waiting for some subtle
error when building the main project.
On 2010-07-21 08:50-0700 Alan W. Irwin wrote:
To draw this subthread to a definite conclusion, here is what works
for me now to get python version for either python2 or python3.
softw...@raven> python -c \
'import sys; print("%s.%s.%s" % sys.version_info[0:3])'
2.6.5
softw...@raven> python3 -c
I agree with Olaf. CMake needs better error reporting for parameter
checking on macros and functions
I ran into similar with use of:
http://www.cmake.org/Wiki/CMakeMacroParseArguments
where I elided the empty quotes "" and it was as though the macro/function
it was contained in did not exist as
On Wed, Jul 21, 2010 at 10:45 AM, Michael Xanadu
wrote:
> Hi Zack,
>
> there's no VTK_DIR row in my CMake GUI. That's my problem. ;-)
>
Do you have the advanced option selected in the cmake-gui?
John
___
Powered by www.kitware.com
Visit other Kitware
On 2010-07-19 00:47+0200 Eric Noulard wrote:
"import sys; print sys.version.split()[0]" will not work with python 3 because
print is a function:
Hi Eric:
Thanks for that reminder about using the print function for python3
and also for giving me the hint about sys.version_info to avoid
trailin
Hi Olaf,
Olaf van der Spek ha scritto:
> Could this be changed to "xbt-tracker_0.1.1_i386.deb"?
>
I'm using the following code to obtain a correct debian-name
string(TOLOWER "${CPACK_PACKAGE_NAME}" CPACK_PACKAGE_NAME_LOWERCASE)
find_program(DPKG_PROGRAM dpkg DOC "dpkg program of Debian-based s
On Wed, Jul 21, 2010 at 5:39 PM, Droscy wrote:
> Hi Olaf,
>
> Olaf van der Spek ha scritto:
>> Could this be changed to "xbt-tracker_0.1.1_i386.deb"?
>>
> I'm using the following code to obtain a correct debian-name
Looks good, but this should really be part of the generator.
Olaf
__
On Wed, Jul 21, 2010 at 5:32 PM, Hendrik Sattler
wrote:
> Zitat von Olaf van der Spek :
>
>> Hi,
>>
>> At the moment the default package file name is like
>> "xbt-tracker-0.1.1-Linux.deb".
>> Could this be changed to "xbt-tracker_0.1.1_i386.deb"?
>> Note the underscore instead of minus as field se
Zitat von Olaf van der Spek :
Hi,
At the moment the default package file name is like
"xbt-tracker-0.1.1-Linux.deb".
Could this be changed to "xbt-tracker_0.1.1_i386.deb"?
Note the underscore instead of minus as field separator and the architecture.
Last time I looked at CPack, the cpack core
I can't help either (no Windows, see?) but I have one personal request (don't
know how others here think about this): Could you please turn off HTML emails?
Because
* it hurts my eyes (as in "it's dead ugly")
* it doesn't respect my favorite font, text size, and quoting display style
* it is usu
Hi,
At the moment the default package file name is like
"xbt-tracker-0.1.1-Linux.deb".
Could this be changed to "xbt-tracker_0.1.1_i386.deb"?
Note the underscore instead of minus as field separator and the architecture.
Olaf
___
Powered by www.kitware.c
On 7/21/2010 10:41 AM, Emmanuel Christophe wrote:
Hi Dave,
Thanks for the information. I was not aware of the new ctest script
style: I got this from Luis when I set up the ITK nightly a while ago.
That's also what seems to appear on:
http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest
Do you ha
Hi Kelly,
Thanks for your reply. To circumvent these issues we've taken a fresh Windows
XP VM and installed compilers cmake UnxUtils but nothing else. No special
environment variables clouding the view either :)
Regards,
Arjen
From: Kelly Thompson [mailto:k...@lanl.gov]
Sent: woensdag 21 juli
On Wed, Jul 21, 2010 at 5:00 PM, Michael Wild wrote:
>
> On 21. Jul, 2010, at 16:53 , Olaf van der Spek wrote:
>
>> On Wed, Jul 21, 2010 at 4:24 PM, Olaf van der Spek
>> wrote:
>>> Hi,
>>>
>>> http://www.itk.org/Wiki/CMake:CPackConfiguration
>>>
CPACK_PACKAGE_NAME: Package name, defaults to
On 21. Jul, 2010, at 16:53 , Olaf van der Spek wrote:
> On Wed, Jul 21, 2010 at 4:24 PM, Olaf van der Spek
> wrote:
>> Hi,
>>
>> http://www.itk.org/Wiki/CMake:CPackConfiguration
>>
>>> CPACK_PACKAGE_NAME: Package name, defaults to the project name.
>>
>> I've got "project(xbttracker)" but it
Hi Arjen,
This may be totally the wrong direction, but we have seen similar errors
that appear to be caused by resident programs that crawl the local
filesystem. Desktop search engines (Microsoft or Google) or anti-virus
software may try to open your build files (including temporary files) for
My CreateDashboardScripts.cmake and DashboardScript.cmake.in located
in this repository might be a useful example - I also had a hard time
figuring out how to do the new-style script.
http://github.com/rpavlik/wiimote-head-tracker-gui/tree/master/cmake/
Ryan
On 7/21/2010 9:41 AM, Emmanuel Ch
On Wed, Jul 21, 2010 at 4:24 PM, Olaf van der Spek wrote:
> Hi,
>
> http://www.itk.org/Wiki/CMake:CPackConfiguration
>
>> CPACK_PACKAGE_NAME: Package name, defaults to the project name.
>
> I've got "project(xbttracker)" but it's still using Project as name.
> What am I doing wrong?
Looks like ch
Thanks Mike!
That work like a charm. I'm not sure why I overlooked that portion of the
user manual. Thanks for being patient.
-kt
> -Original Message-
> From: Michael Wild [mailto:them...@gmail.com]
> Sent: Tuesday, July 20, 2010 2:00 PM
> To: Kelly Thompson
> Cc: cmake@cmake.org
> Su
Brad,
Is this normal behaviour after all? Or at least intended?
Thanks,
Arjen
>-Original Message-
>From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
>Of Verweij, Arjen
>Sent: dinsdag 13 juli 2010 13:27
>To: cmake@cmake.org
>Subject: Re: [CMake] incremental build sl
Hi Dave,
Thanks for the information. I was not aware of the new ctest script
style: I got this from Luis when I set up the ITK nightly a while ago.
That's also what seems to appear on:
http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest
Do you have any pointer for the new-style ctest?
Thanks,
Emm
Hi,
I'm having trouble generating the Makefiles I want on Windows. I can't generate
"Unix Makefiles" because cmake fails to compile a simple program. But also
using generators that should be very much alike, "NMake Makefiles" and "NMake
Makefiles JOM", the first will finish and the second will
Hi,
http://www.itk.org/Wiki/CMake:CPackConfiguration
> CPACK_PACKAGE_NAME: Package name, defaults to the project name.
I've got "project(xbttracker)" but it's still using Project as name.
What am I doing wrong?
$ make && cpack
[100%] Built target xbt_tracker
CPack: Create package using DEB
CPac
On Wed, Jul 21, 2010 at 4:03 PM, Eric Noulard wrote:
>> project(X T)
> Which is not found :-)
Ah, didn't think project would accept a second parameter as language.
> I'm not sure what you mean by " I forgot to use quotes"
It should've been project("X T")
Olaf
_
2010/7/21 Olaf van der Spek :
> Hi,
>
> I forgot to use quotes, but cmake doesn't make that obvious.
> Shouldn't it return a better error message?
>
> $ cat CMakeLists.txt
> project(X T)
If you read the documentation from the "project" command you read:
project( [languageName1 languageName2 ... ]
On 21. Jul, 2010, at 15:48 , Olaf van der Spek wrote:
> Hi,
>
> I forgot to use quotes, but cmake doesn't make that obvious.
> Shouldn't it return a better error message?
>
> $ cat CMakeLists.txt
> project(X T)
>
> $ cmake .
> CMake Error: Error required internal CMake variable not set, cmake
I too would like the answer to this and other questions. I have been having
the same problem with CMake (among others)
How to build a project that contains multiple 3rd party sources where:
1) build of one package is dependent on the not yet installed install of a
dependency package where the in
Hi,
I forgot to use quotes, but cmake doesn't make that obvious.
Shouldn't it return a better error message?
$ cat CMakeLists.txt
project(X T)
$ cmake .
CMake Error: Error required internal CMake variable not set, cmake may
be not be built correctly.
Missing variable is:
CMAKE_T_COMPILER_ENV_VAR
I am guessing that this commit from Dec. 2009:
0b38bb4c535ae972d7f973e3e69945a6d0c14d75
to fix this bug:
http://public.kitware.com/Bug/view.php?id=2336
is related to your problem...
I would recommend updating your script to a "new-style" (since ctest 2.4 at
least) script that uses the ctest_buil
On 7/21/2010 6:23 AM, sheissj wrote:
Hello.
I want to generate a simple Makefile from cmake.
This Makefile looks like this:
all:
@echo "No build"
tags:
ctags -R *.cpp
cscope -b -q -k *.cpp
This simple Makefile do not have target to build source code. It is only
for building ct
2010/7/21 sheissj :
> Hello.
>
> I want to generate a simple Makefile from cmake.
> This Makefile looks like this:
>
> all:
> @echo "No build"
>
> tags:
> ctags -R *.cpp
> cscope -b -q -k *.cpp
>
>
> This simple Makefile do not have target to build source code. It is only for
> building
Hello.
I want to generate a simple Makefile from cmake.
This Makefile looks like this:
all:
@echo "No build"
tags:
ctags -R *.cpp
cscope -b -q -k *.cpp
This simple Makefile do not have target to build source code. It is only for
building ctags index and cscope db.
So it is not a ma
On 21. Jul, 2010, at 9:56 , Marcel Loose wrote:
> On Tue, 2010-07-20 at 09:18 -0700, Alan W. Irwin wrote:
>> On 2010-07-20 17:12+0200 Michael Hertling wrote:
>>
>>> On 07/20/2010 03:26 AM, Alan W. Irwin wrote:
On 2010-07-20 00:51+0200 Michael Hertling wrote:
> On 07/18/2010 10:14
On Tue, 2010-07-20 at 09:18 -0700, Alan W. Irwin wrote:
> On 2010-07-20 17:12+0200 Michael Hertling wrote:
>
> > On 07/20/2010 03:26 AM, Alan W. Irwin wrote:
> >> On 2010-07-20 00:51+0200 Michael Hertling wrote:
> >>
> >>> On 07/18/2010 10:14 PM, Alan W. Irwin wrote:
> (1) http://public.kitwa
On Tue, Jul 20, 2010 at 21:23, Bill Hoffman wrote:
> On 7/19/2010 11:10 PM, Emmanuel Christophe wrote:
>>
>> Hi all,
>>
>> I used to do parallel build for my nightly with ctest by putting
>> MAKECOMMAND:STRING=/usr/bin/make -i -j8
>> in my .cmake script.
>>
>
>
>
> http://www.cdash.org/CDash/build
53 matches
Mail list logo
