[CMake] Sucess with VS2008

I managed to run cmake with vs2008 after downloading the QT vs2008 build, so now I can get going . Many thanks to Michael Wild and Mike Jackson for the help. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitwar

Re: [CMake] Still no luck with visual studio 2008

Did you compile Qt with Visual Studio? That is what the error is saying. You are trying to configure your project using the visual studion generator against a Qt built with MinGW. You can not do this. _ Mike Jackson mike.jack

[CMake] Still no luck with visual studio 2008

Hi all, I have managed to get it as far as this error now, but no further. It does work when set to mingw however. The error message is not too helpful - does anyone have any idea how I go about getting it to work with visual studio? Is it something to do with the open source app I am trying

[CMake] Policy CMP0009 doesn't work (2.6.4)

I couldn't find any way to search the CMake bug tracker, so it's entirely possible this is already filed. I didn't see any reference to it in my mailing list archives, however. Policy CMP0009 is documented (when set to NEW) to make FILE(GLOB_RECURSE) only follow symlinks if the FOLLOW_SYMLINKS fla

Re: [CMake] COMMAND does not accept standard method of splitting stderr and stdout results

On 2010-03-17 22:57+0100 Michael Wild wrote: I just tried a few things, and it seems that you can use eval to your advantage: project(test C) add_custom_command(OUTPUT bla.stderr bla.stdout COMMAND eval "((echo 'this is stdout'; echo 'this is stderr' >&2) > bla.stdout) 2> bla.stderr" VERB

Re: [CMake] libgcc_s_dw2-1.dll not found

On 17. Mar, 2010, at 22:13 , Oli Glaser wrote: > Hi again, > > I should have said previously that I pointed cmake to the qmake.exe but then > I got another error saying > libgcc_s_dw2-1.dll not found, although it is on my computer. How do I point > cmake to this? What am I doing wrong? > I kno

Re: [CMake] COMMAND does not accept standard method of splitting stderr and stdout results

On 17. Mar, 2010, at 21:46 , Alan W. Irwin wrote: > On 2010-03-17 20:21+0100 Michael Wild wrote: > >> Thing is, cmake is neither bash nor ksh, else it would be called cash ;-) > > True, but COMMAND does execute a command on the command line, and on the > Unix side of things that must involve th

[CMake] libgcc_s_dw2-1.dll not found

Hi again, I should have said previously that I pointed cmake to the qmake.exe but then I got another error saying libgcc_s_dw2-1.dll not found, although it is on my computer. How do I point cmake to this? What am I doing wrong? I know I'm new to cmake but I can't believe it can be this hard just

Re: [CMake] CMake 2.8.1 available for download

On 2010-03-17 16:16-0400 Bill Hoffman wrote: Alan W. Irwin wrote: Hi Bill: [...] could you please make sure this regression fix is included in the next CMake release? Alan Yup, it will be in the next release. Great, and thanks to you and the rest of the development team for 2.8.1! Alan _

Re: [CMake] COMMAND does not accept standard method of splitting stderr and stdout results

On 2010-03-17 20:21+0100 Michael Wild wrote: Thing is, cmake is neither bash nor ksh, else it would be called cash ;-) True, but COMMAND does execute a command on the command line, and on the Unix side of things that must involve the shell. To confirm that, note that the Makefiles generated b

Re: [CMake] CMake 2.8.1 available for download

Alan W. Irwin wrote: Hi Bill: I just discovered you did not include the regression fixup below in cmake-2.8.1. I spent a fair amount of effort making a simple test case at your request, verifying that Brad's one-liner patch worked, etc. I assume you didn't include it due to an oversight or bec

[CMake] building plplot

Hi everyone, I am trying to build plplot with CMake. My details -Windows XP -to build plplot I installed the MinGW suite -cmake 2.8 Here's what i get: C:\plplot-5.9.5>cmake -DCMAKE_INSTALL_PREFIX=C:\plplotBUILD -- The C compiler identification is unknown -- Check for working C compiler: C:/MinGW

Re: [CMake] How to build and link Externa Project with exported target

On Wednesday 17 March 2010, Michael Wild wrote: > On 17. Mar, 2010, at 15:43 , Luigi Calori wrote: ... > > Is this ExternalProject_Add feature really used/developed? I find it > > really nice but a little scared of weather it will be really supported > > and improved. I have done some patching on

[CMake] CMake 2.8.1 available for download

Hi Bill: I just discovered you did not include the regression fixup below in cmake-2.8.1. I spent a fair amount of effort making a simple test case at your request, verifying that Brad's one-liner patch worked, etc. I assume you didn't include it due to an oversight or because the issue was dis

Re: [CMake] COMMAND does not accept standard method of splitting stderr and stdout results

On 17. Mar, 2010, at 18:42 , Alan W. Irwin wrote: > According to "Unix in a Nutshell", the bourne and korn shells use the > following method of splitting stderr and stdout into two separate > files. > > (cmd >f1) 2>f2 > > I have checked that the parentheses work for bash, although they are not

Re: [CMake] set proxy with cmake file download

Eric Noulard wrote: 2010/3/12 AKHRES Nader > I'm using windows... maybe it works on linux, I'll have a try but I would need a way to make it works on windows as well I don't know the default behavior of curl lib on Windows but the CTest source code do

[CMake] CMake 2.8.1 available for download

On behalf of myself, Ken, Brad, Dave, Alex, Zach and the rest of the CMake team, we are pleased to announce that CMake 2.8.1 is available for download at: http://www.cmake.org/cmake/resources/software.html Here are the changes for CMake 2.8.1: Changes in CMake 2.8.1 - Fix failing test on cygwin

Re: [CMake] COMMAND does not accept standard method of splitting stderr and stdout results

On 2010-03-17 13:46-0400 David Cole wrote: If you must run a script verbatim, then write a script. Then have cmake just execute the script. My use case is I plan to have about 100 custom commands in my FreeEOS test suite, and they all need their stderr split from stdout. I guess the silver li

[CMake] Problem with cmake when make is in a path with spaces.

Hello all, I have a problem on a mac os x server where I want to compile a simple code with cmake. The cmake process fails because it cannot compile a test file. The output file shows some bizarre error. Apparently it cannot find the make command. The problem lies, I think, in the fact that the ma

[CMake] ANNOUNCE - Developer Training at Kitware May 3-6

A Brief Reminder from Kitware, * Developer's Training Week will be held May 3 – 6, 2010, in Albany, NY. Early Registration closes April 1. Details -- Developer's Training Week will cover our open-source projects including VTK, ITK, ParaView and CMake. This hands-on course is appropr

Re: [CMake] COMMAND does not accept standard method of splitting stderr and stdout results

If you must run a script verbatim, then write a script. Then have cmake just execute the script. On Wed, Mar 17, 2010 at 1:42 PM, Alan W. Irwin wrote: > According to "Unix in a Nutshell", the bourne and korn shells use the > following method of splitting stderr and stdout into two separate > fi

[CMake] COMMAND does not accept standard method of splitting stderr and stdout results

According to "Unix in a Nutshell", the bourne and korn shells use the following method of splitting stderr and stdout into two separate files. (cmd >f1) 2>f2 I have checked that the parentheses work for bash, although they are not necessary. Therefore, the above seems to be a good candidate for

Re: [CMake] Include paths not being searched?

On Wed, Mar 17, 2010 at 11:36 AM, Bill Hoffman wrote: > Michael Wild wrote: > >> Yes, that would be the problem. CMake assumes that .c is a C file, not >> C++. >> >> To override this: >> >> set(SRCS src1.c src2.c src3.c) >> add_executable(super ${SRCS}) >> set_source_files_properties(${SRCS} PROPE

Re: [CMake] Include paths not being searched?

Michael Wild wrote: Yes, that would be the problem. CMake assumes that .c is a C file, not C++. To override this: set(SRCS src1.c src2.c src3.c) add_executable(super ${SRCS}) set_source_files_properties(${SRCS} PROPERTIES LANGUAGE CXX) To set this globally, you can override the CMAKE_C_SOUR

Re: [CMake] Include paths not being searched?

On 17. Mar, 2010, at 16:06 , David Doria wrote: >> Those files should not need to be on the include path since your compiler >> should know how to find them (after all, they belong to the c++ standard >> library). Do you happen to use -nostdinc or -nostdinc++ in your compile >> flags? Also, wh

Re: [CMake] Include paths not being searched?

On 03/17/2010 10:06 AM, David Doria wrote: Those files should not need to be on the include path since your compiler should know how to find them (after all, they belong to the c++ standard library). Do you happen to use -nostdinc or -nostdinc++ in your compile flags? Also, what is your c++

Re: [CMake] Include paths not being searched?

> Those files should not need to be on the include path since your compiler > should know how to find them (after all, they belong to the c++ standard > library). Do you happen to use -nostdinc or -nostdinc++ in your compile > flags? Also, what is your c++ compiler? > > If you do a verbose build

Re: [CMake] How to build and link Externa Project with exported target

On 17. Mar, 2010, at 15:43 , Luigi Calori wrote: > > [...] >> He's not downloading with CMake, he just told git that in this directory is >> a submodule. The user has then to fetch it himself with one command: >> >> http://git.wiki.kernel.org/index.php/GitSubmoduleTutorial >> > Sorry ... no

Re: [CMake] Include paths not being searched?

On 17. Mar, 2010, at 15:32 , David Doria wrote: > The reason I was looking to check the contents of INCLUDE_DIRECTORIES > was that when I build my project I am getting errors like this: > > /usr/include/fstream:40:19: error: istream: No such file or directory > > The output of this: > get_prope

Re: [CMake] static library from several subdirectories

Hi, >-Original Message- >From: Michael Wild [mailto:them...@gmail.com] >I think the problem is that the ${BIG_LIB} target does not exist when >you call ADD_DEPENDENCIES. Probably you should also collect all the >custom targets into a global property and then after the >ADD_LIBRARY(${BIG_

Re: [CMake] How to build and link Externa Project with exported target

[...] He's not downloading with CMake, he just told git that in this directory is a submodule. The user has then to fetch it himself with one command: http://git.wiki.kernel.org/index.php/GitSubmoduleTutorial Sorry ... no git expert at all my point was just to hack ExternalProject_add

Re: [CMake] INCLUDE_DIRECTORIES empty?

> The syntax is: > > INCLUDE_DIRECTORIES(../../include) > > This will append to the already existing include directories. > > Michael > Ok. And then how do I see the list of everything that has been added to INCLUDE_DIRECTORIES? Thanks, David ___ Power

[CMake] Include paths not being searched?

The reason I was looking to check the contents of INCLUDE_DIRECTORIES was that when I build my project I am getting errors like this: /usr/include/fstream:40:19: error: istream: No such file or directory The output of this: get_property(inc_dirs DIRECTORY PROPERTY INCLUDE_DIRECTORIES) message("in

Re: [CMake] INCLUDE_DIRECTORIES empty?

> As I said, it's a directory-property: > > get_property(inc_dirs DIRECTORY PROPERTY INCLUDE_DIRECTORIES) > message("inc_dirs = ${inc_dirs}") > > > Michael Gotcha. Thanks a lot! David ___ Powered by www.kitware.com Visit other Kitware open-source proje

Re: [CMake] How to build and link Externa Project with exported target

On 17. Mar, 2010, at 14:37 , Luigi Calori wrote: > Hi Michael and Nicola, > I'm in a similar situation as I' m trying to build up a cmake based > dependency builder for OpenSceneGraph based projects: > So I' m really interested in any "best practice" advice > > Michael Wild wrote: >> On 17. Mar

Re: [CMake] INCLUDE_DIRECTORIES empty?

On 17. Mar, 2010, at 14:45 , David Doria wrote: >> This is a read-only directory property: >> >> http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_dir:INCLUDE_DIRECTORIES >> >> Michael > > That's ok, all I want to do is read it. That's why I thought it would just be: > > MESSAGE("INCLU

Re: [CMake] INCLUDE_DIRECTORIES empty?

> This is a read-only directory property: > > http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_dir:INCLUDE_DIRECTORIES > > Michael That's ok, all I want to do is read it. That's why I thought it would just be: MESSAGE("INCLUDE_DIRECTORIES: ${INCLUDE_DIRECTORIES}") But I guess INCLUDE_DIR

Re: [CMake] INCLUDE_DIRECTORIES empty?

On 17. Mar, 2010, at 14:34 , David Doria wrote: >> The syntax is: >> >> INCLUDE_DIRECTORIES(../../include) >> >> This will append to the already existing include directories. >> >> Michael >> > > Ok. And then how do I see the list of everything that has been added > to INCLUDE_DIRECTORIES? >

Re: [CMake] How to build and link Externa Project with exported target

Hi Michael and Nicola, I'm in a similar situation as I' m trying to build up a cmake based dependency builder for OpenSceneGraph based projects: So I' m really interested in any "best practice" advice Michael Wild wrote: On 17. Mar, 2010, at 13:17 , Nicola Brisotto wrote: Hi! I'm building

Re: [CMake] INCLUDE_DIRECTORIES empty?

On 17. Mar, 2010, at 13:58 , David Doria wrote: > If I do something like this: > > INCLUDE_DIRECTORIES(${INCLUDE_DIRECTORIES} ../../include) > > I'd expect ../../include to be appended to the current INCLUDE_DIRECTORIES. > > So then when I do this: > MESSAGE("INCLUDE_DIRECTORIES: ${INCLUDE_DI

[CMake] INCLUDE_DIRECTORIES empty?

If I do something like this: INCLUDE_DIRECTORIES(${INCLUDE_DIRECTORIES} ../../include) I'd expect ../../include to be appended to the current INCLUDE_DIRECTORIES. So then when I do this: MESSAGE("INCLUDE_DIRECTORIES: ${INCLUDE_DIRECTORIES}") at the very least, I should see ../../include, but p

Re: [CMake] How to build and link Externa Project with exported target

On 17. Mar, 2010, at 13:17 , Nicola Brisotto wrote: > Hi! > I'm building a project that require a 3rd party library libqxmpp. Both > project uses cmake > I want to build libqxmpp with ExternalProject_add, this the code I use: > > ExternalProject_add( > libqxmpp > #no download, i'm

Re: [CMake] static library from several subdirectories

On 17. Mar, 2010, at 13:01 , Verweij, Arjen wrote: > Hi, > >> From: Michael Wild [mailto:them...@gmail.com] > >> I'd recommend to change the add_sources function to do all the >> preprocessing and then only add the products (.f, .f90, .c etc.) files >> to the list. You can do the preprocessing

[CMake] How to build and link Externa Project with exported target

Hi! I'm building a project that require a 3rd party library libqxmpp. Both project uses cmake I want to build libqxmpp with ExternalProject_add, this the code I use: ExternalProject_add( libqxmpp #no download, i'm using git submodule DOWNLOAD_COMMAND "" CMAKE_ARGS

Re: [CMake] static library from several subdirectories

Hi, >From: Michael Wild [mailto:them...@gmail.com] >I'd recommend to change the add_sources function to do all the >preprocessing and then only add the products (.f, .f90, .c etc.) files >to the list. You can do the preprocessing like this (of course, you'll >have to change things for your setup,

Re: [CMake] link issue with 2 statics lib->what's wrong in my cmake project

AKHRES Nader wrote: thank you very much Bill, it works now! Is it a big deal if I let the lib A where you advise me to remove it? Either way should work. -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.k