On 2012-10-19 13:39-0400 Bill Hoffman wrote:
On 10/19/2012 1:24 PM, Alan W. Irwin wrote:
So far this morning there have been no takers, but I hope that changes
since I am really stumped by CMake _intermittently_ not issuing the
correct link command for libraries with no consistent pattern I
Stephen Kelly steveire@... writes:
Brad King wrote:
The only option I see that might work is to extend the undefined behavior
documentation of the LOCATION* properties to cover use of generator
expressions with link libraries, and then try to refactor/copy the code
out of cmTarget to
On 10/22/2012 3:34 AM, Alan W. Irwin wrote:
The diff between them shows a lot of noise
Can you send the CMakeFiles/* files? I suspect that it is detecting
the compiler or platform different somehow. Also, send the
CMakeCache.txt from both builds. You can send it directly to me to
avoid
On 10/22/2012 01:24 PM, Stephen Kelly wrote:
That's in the use-generator-target-2 branch in my clone.
git://gitorious.org/~steveire/cmake/steveires-cmake.git
I'll rebase and submit the contents of it in several parallel branches when
2.8.11 opens. I'll also fix the style issues in the
Brad King wrote:
On 10/22/2012 01:24 PM, Stephen Kelly wrote:
That's in the use-generator-target-2 branch in my clone.
git://gitorious.org/~steveire/cmake/steveires-cmake.git
I'll rebase and submit the contents of it in several parallel branches
when 2.8.11 opens. I'll also fix the style
It isn't as bad as I might have made it sound. e.g.:
add_executable(mytest test.cpp)
set_target_properties(mytest PROPERTIES RUNTIME_OUTPUT_DIRECTORY
${CMAKE_BINARY_DIR})
add_test(mytest ${CMAKE_BINARY_DIR}/mytest)
On unix (I'm not sure about all but at least on gnu linux) CMake
Hi Andreas,
thanks for your tip. Unfortunately, 'make -k install' doesn't help, as the
entire install step is a single command (cmake -P ...), so once this fails,
there is no other command make could continue with. Is there no way to do
this natively in cmake?
I could (in theory) add OPTIONAL to
I am sorry I missed your response. Here are the details:
1. I have a shell / batch script which does two things:
a. cd build_dir cmake $SRC_PATH
b. make # On Unix
On Windows, for step b., we run
devenv proj.sln /Build Release|x86 /out logfile_path
Here is the top level
On Mon, Oct 22, 2012 at 4:06 PM, Arindam Mukherjee
arindam.muker...@gmail.com wrote:
I am sorry I missed your response. Here are the details:
1. I have a shell / batch script which does two things:
a. cd build_dir cmake $SRC_PATH
b. make # On Unix
On Windows, for step b., we
Eric
Do you happen to know what docs you were looking at? It may be worth a little
bit to post that to this mailing list so that hopefully the person that wrote
those docs could be so kind as to update them with the correct syntax.
I can't find the ones I was looking at before. But hopefully
On Mon, Oct 22, 2012 at 6:38 AM, Arindam Mukherjee
arindam.muker...@gmail.com wrote:
On Mon, Oct 22, 2012 at 4:06 PM, Arindam Mukherjee
arindam.muker...@gmail.com wrote:
I am sorry I missed your response. Here are the details:
1. I have a shell / batch script which does two things:
a. cd
Hi Nils,
It isn't as bad as I might have made it sound. e.g.:
add_executable(mytest test.cpp)
set_target_properties(mytest PROPERTIES RUNTIME_OUTPUT_DIRECTORY
${CMAKE_BINARY_DIR})
add_test(mytest ${CMAKE_BINARY_DIR}/mytest)
Yes. Everything works OK now. My question was more of a theoretical
Hello,
The target property INCLUDE_DIRECTORIES overwrites the
include_directories command values.
A better way would have been that the values of the include_directories
command would appended to the values of the target property
INCLUDE_DIRECTORIES.
I think that would make more sense.
On 10/21/2012 10:20 PM, Ian Monroe wrote:
So I had code like:
include(ExternalProject)
ExternalProject_Add(
mockcpp
DOWNLOAD_COMMAND hg clonessh://h...@bitbucket.org/godsme/mockcpp
CMAKE_ARGS -DCMAKE_INSTALL_PREFIX=${MOCKCPP_PREFIX}
UPDATE_COMMAND hg pull
)
If you want to APPEND, then use set_property with APPEND.
http://cmake.org/cmake/help/v2.8.9/cmake.html#command:set_property
HTH,
David
On Mon, Oct 22, 2012 at 9:05 AM, Micha Renner micha.ren...@t-online.de wrote:
Hello,
The target property INCLUDE_DIRECTORIES overwrites the
On Mon, Oct 22, 2012 at 3:22 AM, Petr Kmoch petr.km...@gmail.com wrote:
Hi Andreas,
thanks for your tip. Unfortunately, 'make -k install' doesn't help, as the
entire install step is a single command (cmake -P ...), so once this fails,
there is no other command make could continue with. Is
Just following up after a little while...
On Sat, 8 Sep 2012 10:48:11 -0400, David Cole said:
Does this happen regardless of which Xcode you select, or only with
the -DP4 one?
Happens with any of them.
Does this still happen for you if you use CMake from the 'next' branch?
Seems fixed in
On Mon, Oct 22, 2012 at 11:26 AM, Sean McBride s...@rogue-research.com wrote:
Just following up after a little while...
On Sat, 8 Sep 2012 10:48:11 -0400, David Cole said:
Does this happen regardless of which Xcode you select, or only with
the -DP4 one?
Happens with any of them.
Does this
Hello:
I am using cmake for three months now.
but was trouble in a situation 。for details bellow: (in Windows,using Microsoft
Visual Studio 2008)
ADD_LIBRARY(test SHARED ${LIBTEST_SRC} ${LIBHELLO_SRC})
#ADD_LIBRARY(test STATIC ${LIBTEST_SRC} ${LIBHELLO_SRC})
#add executable
Hi,
On Mon, Oct 22, 2012 at 5:35 PM, 张峰 fangler2...@126.com wrote:
1.if i put TARGET_LINK_LIBRARIES(fan test) before ADD_EXECUTABLE
command,this does not work ,why??
Because until yout call add_executable(), the target name doesn't exist.
You have to use the target name as first parameter
Hello everyone,
My c++ project contains a Library folder, an Applications folder and a
Demos folder like this:
Project/
|- Library/
|- include/
|- src/
|- Applications/
|- appliA/
Hello:
I am using cmake for three months now.
but was trouble in a situation 。for details bellow: (in Windows)
ADD_LIBRARY(test SHARED ${LIBTEST_SRC} ${LIBHELLO_SRC})
#ADD_LIBRARY(test STATIC ${LIBTEST_SRC} ${LIBHELLO_SRC})
#add executable
AUX_SOURCE_DIRECTORY(. FAN_SRC)
Hello,
First off, you cannot call both add_executable and add_library in the same
CMakeLists file. Here is what I can say about your other questions:
1. All commands that require a target have to come after you have created
the target via add_executable or add_library. This is simply
On Mon, Oct 22, 2012 at 6:07 AM, Bill Hoffman bill.hoff...@kitware.com wrote:
On 10/21/2012 10:20 PM, Ian Monroe wrote:
So I had code like:
include(ExternalProject)
ExternalProject_Add(
mockcpp
DOWNLOAD_COMMAND hg clonessh://h...@bitbucket.org/godsme/mockcpp
CMAKE_ARGS
At CMake/Testing With CTest Wiki page
(http://www.cmake.org/Wiki/CMake_Testing_With_CTest), it is mentioned
that:
CTest has several additional features that include:
...
Customization of the testing by providing:
...
Ability to run commands before and after tests are run
I need to do
On 10/22/2012 12:34 PM, Ian Monroe wrote:
So what was the target use-case for ExternalProject? From the name it
sounds like it was meant exactly for making your non-external project
(aka your project) be able to pull in dependencies from external
projects.
The target use case was to create a
Hi,
On Mon, Oct 22, 2012 at 6:04 PM, Eric Clark ecl...@ara.com wrote:
First off, you cannot call both add_executable and add_library in the same
CMakeLists file.
I think there's something missing here, but its perfectly possible to
have one or more library and executable targets specified in
Eric Clark wrote:
Hello,
First off, you cannot call both add_executable and add_library in the same
CMakeLists file. Here is what I can say about your other questions:
Of course you can.
1. All commands that require a target have to come after you have
created the target via
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Rolf Eike Beer
Sent: Monday, October 22, 2012 12:11 PM
To: cmake@cmake.org
Subject: Re: [CMake] cmake trouble
Eric Clark wrote:
Hello,
First off, you cannot call both
Andreas,
I just replied to a message from another gentleman on here and I may be way off
base. But, I tried to do this once and it did not work. The only way that I
could get it to work was to add another project() call between the two... I
could have had some other issues because it has been
-Original Message-
From: Andreas Pakulat [mailto:ap...@gmx.de]
Sent: Monday, October 22, 2012 12:17 PM
To: Eric Clark
Cc: 张峰; cmake@cmake.org
Subject: Re: [CMake] cmake trouble
Hi,
On Mon, Oct 22, 2012 at 6:04 PM, Eric Clark ecl...@ara.com wrote:
First off, you cannot call
Eric Clark wrote:
From: Andreas Pakulat [mailto:ap...@gmx.de]
On Mon, Oct 22, 2012 at 6:04 PM, Eric Clark ecl...@ara.com wrote:
First off, you cannot call both add_executable and add_library in the
same CMakeLists file.
I think there's something missing here, but its perfectly
Eric Clark wrote:
Eric Clark wrote:
Hello,
First off, you cannot call both add_executable and add_library in the
same CMakeLists file. Here is what I can say about your other questions:
Of course you can.
Yes, but only if you call project() twice, correct?
No, even if you
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Rolf Eike Beer
Sent: Monday, October 22, 2012 12:48 PM
To: cmake@cmake.org
Subject: Re: [CMake] cmake trouble
Eric Clark wrote:
From: Andreas Pakulat [mailto:ap...@gmx.de] On Mon, Oct
Eric Clark wrote:
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Rolf Eike Beer
Sent: Monday, October 22, 2012 12:48 PM
To: cmake@cmake.org
Subject: Re: [CMake] cmake trouble
Eric Clark wrote:
From: Andreas Pakulat
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Rolf Eike Beer
Sent: Monday, October 22, 2012 12:51 PM
To: cmake@cmake.org
Subject: Re: [CMake] cmake trouble
Eric Clark wrote:
-Original Message-
From:
On 2012-10-22 17:55- Eric Clark wrote:
Awesome! Thank you for the answers and the quick reply! I have only
been using CMake for a little over a year and again I am sorry for
posting an incorrect answer. I always thought that I had to have one
project() call for each add_executable and/or
2012/10/22 Romain LEGUAY romain.leg...@gmail.com:
Hello everyone,
My c++ project contains a Library folder, an Applications folder and a Demos
folder like this:
Project/
|- Library/
|- include/
|- src/
|- Applications/
I've hit a snag on an HPPA machine using the HP compiler aCC. This host
is HPUX 11.11 on 9000/800. I don't know enough about C++ to make heads
or tails of the error message below and searches turn up nothing useful.
thanks,
Amul
-
CMake 2.8.9,
Alan,
Thank you for such a detailed response. I am pretty new to this mailing list
and have only responded to a few questions on here, but I have really thought
the responsiveness on here is the best of any of the message boards that I
belong to and I really appreciate it, so I like to give
On 2012-10-22 20:25- Eric Clark wrote:
I would love your opinion on what I have done here. Since this being
developed for developers, it is always nice to get the developer's
(our end-user's) perspective. Do you think I am missing the purpose of
the project() command all together?
I am
)
+set(CMake_VERSION_TWEAK 20121022)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
hooks/post-receive
--
CMake
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 4aaeb805fa8261a9edfbe12f3de562e918a35d8c (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 88d77e7f29a71f9c583419f184508c5fff822960 (commit)
via
44 matches
Mail list logo
