Hi everybody,
I'm a big cmake fan, I use to generate kdevelop projects and makefile.
Now that my application as achieved an acceptable completion level, I
think about deployment.
So, I started using CPack from within CMake (2.6) (via my CMakeLists.txt
file). But I can't manage to build an rpm
2009/5/5 Florent Lagaye florent.lag...@inrialpes.fr:
Hi everybody,
I'm a big cmake fan, I use to generate kdevelop projects and makefile.
Now that my application as achieved an acceptable completion level, I
think about deployment.
So, I started using CPack from within CMake (2.6) (via my
Once more: I have 3 projects.
projectA depends on projectB
projectB depends on SOMEAPP_INCLUDES and SOMEAPP_LIBRARIES
projectC does not depend on anything
I have FindSomeApp script that sets SOMEAPP_FOUND
1. I want to be able to complete cmake configuration, and build projectC, even
if
Thanks for the answer. There was really an INCLUDE(CPack) command don't
know why it didn't get shiped with the mail. I was really using
UseRPMTools, I changed that.
Here's my new CMakeLists.txt:
cmake_minimum_required(VERSION 2.6)
PROJECT( viewer4d )
SET( VERSION 1.0.0 )
SET(
I have checked cmGlobalGenerator.cxx and its CheckLocalGenerators
function. This seems to the right place to perform all checks.
I think I could make a global variable CMAKE_ALLOW_PARTIAL_PROJECT_TREE, which
I could check in this function. If a target has a failed dependency,
then I should
On 05.05.09 14:29:03, eblo...@free.fr wrote:
Hi,
I have a question about CMake and dependency management when an executable is
built, and linked with static libraries which are built within the same
project.
I use a top CMakeLists.txt which looks like:
PROJECT (proj)
SET
On Tue, May 05, 2009 at 10:38:23AM -0400, John Drescher wrote:
On Tue, May 5, 2009 at 10:09 AM, David Larsson laseral...@gmail.com wrote:
I've noticed that the INSTALL project generated in visual studio projects
when using install commands in CMakeLists.txt is disabled by default in
the
On Tue, May 05, 2009 at 03:05:31PM +0200, Andreas Pakulat wrote:
On 05.05.09 14:29:03, eblo...@free.fr wrote:
I use a top CMakeLists.txt which looks like:
PROJECT (proj)
SET (subprojects mylib myapp)
FOREACH (prj ${subprojects})
ADD_SUBDIRECTORY (${prj} ${prj})
ENDFOREACH
Hi all,
here is what I'm trying to do:
I have a CMake build tree with several projects and targets with some
depending on others (impressive eh? ;)). Furthermore I have a library
that I need to build outside of CMake and therefor I just added it
using
add_library(xxx SHARED IMPORTED)
(But
ping?
Hi,
this code:
list(APPEND list A B C D)
message(List: ${list})
foreach(arg ${list})
message(List elem: ${arg})
endforeach()
has the following result:
List: A;B;;C;D
List elem: A
List elem: B
List elem: C
List elem: D
The
On 05.05.09 09:21:14, Tyler Roscoe wrote:
On Tue, May 05, 2009 at 06:11:05PM +0200, Andreas Pakulat wrote:
On 05.05.09 08:28:12, Tyler Roscoe wrote:
On Tue, May 05, 2009 at 03:05:31PM +0200, Andreas Pakulat wrote:
On 05.05.09 14:29:03, eblo...@free.fr wrote:
I use a top
I saw this too.
IMHO, it's a bug. If it's a feature, I don't see the point.
I ended defining all my imported targets in the top directory, to be
able to use them wherever I need them.
Alexandre
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
The only solution I see is to use LIST(GET...
But you'll need to get LIST length somehow...
Denis
--- On Tue, 5/5/09, alexandre.feb...@thomsonreuters.com
alexandre.feb...@thomsonreuters.com wrote:
From: alexandre.feb...@thomsonreuters.com
alexandre.feb...@thomsonreuters.com
Subject: Re:
Denis Scherbakov wrote:
The only solution I see is to use LIST(GET...
But you'll need to get LIST length somehow...
This is related to this policy:
http://www.cmake.org/cmake/help/cmake2.6docs.html#policy:CMP0007
-Bill
___
Powered by www.kitware.com
Doing in-source builds is generally considered a bad idea.
Instead do
something like:
ADD_SUBDIRECTORY (${prj} ${prj}/build)
Huh? That snippet above has absolutely nothing to do with in-
source vs.
out-of-source builds. He simply accumulates all his subprojects in a
variable instead of
Ideally you wouldn't use linker flags, but just use the target you've
created via add_library. But I guess that doesn't work with the
start-group
stuff. So...
Yeah, at least I've been unable to find a better way to use --start-
group / --end-group
There is no explicit dependencies between
On 05.05.09 21:51:16, Emmanuel Blot wrote:
Doing in-source builds is generally considered a bad idea.
Instead do
something like:
ADD_SUBDIRECTORY (${prj} ${prj}/build)
Huh? That snippet above has absolutely nothing to do with in-
source vs.
out-of-source builds. He simply
But then the second parameter is completely superflous, it just adds
noise and confusion. If you use just add_directory(foo) cmake will
automatically use builddir/foo as builddir for foo.
I don't remember when I've added it, but I *had* to add it at some
point: CMake was not working as
Hello,
with cmake 2.6.4 I run into a problem with our build system (OpenSG,
opensg.vrsource.org). It has to build a bunch of (shared) libraries from
a fairly deeply neested source tree with dependencies between some of
the libs, plus tests programs, unittests and documentation.
It
On 05.05.09 22:06:01, Emmanuel Blot wrote:
But then the second parameter is completely superflous, it just adds
noise and confusion. If you use just add_directory(foo) cmake will
automatically use builddir/foo as builddir for foo.
I don't remember when I've added it, but I *had* to add it at
Carsten Neumann wrote:
It does so by performing multiple passes over the source tree
[snip]
This all works fine with cmake 2.6.x (x 4), but the latest version
complains in the OSGSETUP pass on the first call to ADD_SUBDIRECTORY in
that pass (see attachment for more details):
[snip]
Is this
21 matches
Mail list logo
