The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11685
==
Reported By:Evgeny Kapun
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11687
==
Reported By:laurentdk01
Assigned To:
Hi Manuel,
I think the goals of your work are important. I like the general
idea. One sure way to give such tools the same view of the code
as the compiler is to ask the build system to provide the information.
I'm a CMake developer but I also wrote gccxml. The latter is a
code analysis tool
Hi everyone,
The XCode generator does not properly add recursive dependencies, resulting
in that the project files won't be re-generated correctly.
The problem should be easily reproduced in any project that has at least one
add_subdirectory() command, just study the
Hi Brad,
On Wed, Jan 12, 2011 at 8:25 AM, Brad King brad.k...@kitware.com wrote:
Hi Manuel,
I think the goals of your work are important. I like the general
idea. One sure way to give such tools the same view of the code
as the compiler is to ask the build system to provide the
Hello,
how can I determine the path to installed target? The problem is, if I
set DESTDIR for example D:\, I the install path becomes
D:\Programme\project name, so I cannot use DESTDIR to determine
the path.
--
BG,
Alexey
___
Powered by www.kitware.com
Hello,
I would like the add the CMake approach for software generation to a project. My
project example supports also other build tools.
This has got consequences on the way how informations like version numbers are
shared between these approaches.
The CMake tutorial describes components for
I would like the add the CMake approach for software generation to a
project. My project example supports also other build tools.
This has got consequences on the way how informations like version numbers
are shared between these approaches.
The CMake tutorial describes components for the
Are you using source control?
Yes. - But there are challenges to query content management systems in a
portable way.
I use a combination of version in the main CMakeLists.txt and the svn
rev. Variables from these get into a generated project header file
that is also generated in the main
Is it possible to change the default path (project.dir) where the object
files (.o or .obj) are put?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
2011/1/12 Alexey Livshits livch...@web.de:
Hello,
how can I determine the path to installed target?
When ?
If it is inside a CMakeLists.txt i.e. at CMake time usually you can't
unless you specify absolute install path in your install rules.
The problem is, if I
set DESTDIR for example D:\, I
It is *possible*, but you would have to change the source code to CMake...
We select directories on a per-target basis to avoid name clashes between
object files named the same but from different targets.
There is no way to adjust it as a project CMakeLists writer...
intentionally. We view it as
What do you want to do?
I have some tests, which cannot be run without installation because of
dependencies. So I need to specify the install path to add_test. Is
there a better approach?
--
BG,
Alexey
___
Powered by www.kitware.com
Visit other
2011/1/12 SF Markus Elfring elfr...@users.sourceforge.net:
Hello,
I would like the add the CMake approach for software generation to a
project. My project example supports also other build tools.
This has got consequences on the way how informations like version numbers
are shared between
On 11-1-2011 at 21:51, in message
20110111213036.af4c126...@public.kitware.com, Rolf Eike Beer
e...@sf-mail.de wrote:
Am Dienstag, 11. Januar 2011, 11:20:06 schrieb David Cole:
Yes... this confused me when I first encountered it as well.
TRY_COMPILE is misnamed in CMake.
In
On 01/12/2011 01:24 PM, Alexey Livshits wrote:
What do you want to do?
I have some tests, which cannot be run without installation because of
dependencies. So I need to specify the install path to add_test. Is
there a better approach?
Yes, make the tests run without installation. To give
Yes, make the tests run without installation. To give more advice, we'd
need to know more about those dependencies. Are they other
executables? Data files? Libraries?
Well, if I could do that, I wouldn't ask ;)
I have 2 versions, which are built from the same sources. So I have to
have 2
Hi,
when I run cmake like this:
cmake -DCMAKE_TOOLCHAIN_FILE=toolchain-sdk-gcc.cmake
-DMY_TOOLCHAIN_PATH=$HOME/toolchains/sdk/ path/to/CMakeLists.txt
with toolchain-sdk-gcc.cmake:
SET(CMAKE_SYSTEM_NAME Linux)
SET(CMAKE_SYSTEM_VERSION 1)
SET(QT_QMAKE_EXECUTABLE ${MY_TOOLCHAIN_PATH}/bin/qmake)
2011/1/12 Alexey Livshits livch...@web.de:
Yes, make the tests run without installation. To give more advice, we'd
need to know more about those dependencies. Are they other
executables? Data files? Libraries?
Well, if I could do that, I wouldn't ask ;)
I have 2 versions, which are built
On 01/12/2011 01:48 PM, Alexey Livshits wrote:
Yes, make the tests run without installation. To give more advice, we'd
need to know more about those dependencies. Are they other
executables? Data files? Libraries?
Well, if I could do that, I wouldn't ask ;)
I have 2 versions, which are
If the two version are needed you may build them in a single build.
...
but may be I'm missing something about your 2 versions?
That's what I already do. The problem is, libv1 and libv2 should be
called libv.
Alternatively, may be you can decide that your needed
temporary install will always
As I mentioned above, there are targets foo1 and foo2, build from foo
sources, and the output name has to be foo. This is the conflict. The
test depends from foo1 and bar2.
If you don't explain the problem more clearly, people won't be able to
help you; particularly because I suspect that you
I use a simple text file with the build number, which is tracked under
VCS. During the build I parse it, generate my version header, increase
the number, save it to the file and check it in.
Which (CMake) commands do you use for this approach?
Regards,
Markus
On 01/12/2011 02:16 PM, Alexey Livshits wrote:
As I mentioned above, there are targets foo1 and foo2, build from foo
sources, and the output name has to be foo. This is the conflict. The
test depends from foo1 and bar2.
If you don't explain the problem more clearly, people won't be able to
Here is the code:
find_file(myproject_BUILD_NUMBER_FILE_FOUND myproject_build_number.txt
PATHS ${myproject_SOURCE_DIR})
if(${myproject_BUILD_NUMBER_FILE_FOUND} MATCHES NOTFOUND)
set(myproject_CURRENT_BUILD_NUM 1)
else()
file(READ ${myproject_SOURCE_DIR}/myproject_build_number.txt
Here is the code:
Thanks. - Very nice. :-)
Which software licence does belong to your approach?
Would anybody like to transform your example into an official CMake module?
Regards,
Markus
___
Powered by www.kitware.com
Visit other Kitware
Well, if you don't want any help fixing the real problem, then the
answer is simple: CMake can't possibly give you that information because
of DESTDIR.
Thank you.
So, go and fix your project.
I wish I could, but its not so simple. If you have an idea, just let me know.
--
BG,
Alexey
Which software licence does belong to your approach?
I don't know :)
--
BG,
Alexey
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check
On Wed, Jan 12, 2011 at 8:34 AM, Alexey Livshits livch...@web.de wrote:
Well, if you don't want any help fixing the real problem, then the
answer is simple: CMake can't possibly give you that information because
of DESTDIR.
Thank you.
So, go and fix your project.
I wish I could, but
David Cole ha scritto:
It is *possible*, but you would have to change the source
code to CMake...
We select directories on a per-target basis to avoid name
clashes between object files named the same but from different targets.
There is no way to adjust it as a project CMakeLists
On 01/12/2011 02:47 PM, David Cole wrote:
On Wed, Jan 12, 2011 at 8:34 AM, Alexey Livshits livch...@web.de wrote:
Well, if you don't want any help fixing the real problem, then the
answer is simple: CMake can't possibly give you that information because
of DESTDIR.
Thank you.
So, go and
Thing is, you can't *rely* on DESTDIR *not* being used by the user of
your project. If a user shoots himself in the foot, that's his fault,
but when designing your test architecture you IMHO shouldn't make the
use of DESTDIR impossible. I'm sure Debian/Ubuntu/the/whole/zoo would
object to
On 01/12/2011 03:03 PM, Alexey Livshits wrote:
Thing is, you can't *rely* on DESTDIR *not* being used by the user of
your project. If a user shoots himself in the foot, that's his fault,
but when designing your test architecture you IMHO shouldn't make the
use of DESTDIR impossible. I'm sure
Here is the code:
I have got another idea.
Did anybody try to use the C/C++ preprocessor (cpp and eventually including
the compiler) to output a file in a format which is suitable for processing of
this data as a project specification for CMake?
Regards,
Markus
2011/1/12 Tim St. Clair timoth...@gmail.com:
As a side issue: not all platforms which support the TGZ natively
support fakeroot.
I think ownership rights should likely be a CPACK option as a result.
True off course.
Would you be willing to file a feature request and possibly a patch proposal?
Hello,
I am new to CMake and following a few examples, I am now trying to
cross-compile a C++ program from Cygwin to Linux, and I got the following
errors:
CMake Error: Error required internal CMake variable not set, cmake may be
not be built correctly.
Missing variable is:
On 01/11/2011 05:46 PM, Marco wrote:
Dear CMake experts,
I'm facing the following problem. I have a project with many
subdirectories, all at the same hierarchical level:
/my/project/path/CMakeLists.txt
/my/project/path/A - include
|- src
|-
On 01/12/2011 04:29 PM, Enrique Izaguirre wrote:
Hello,
I am new to CMake and following a few examples, I am now trying to
cross-compile a C++ program from Cygwin to Linux, and I got the following
errors:
CMake Error: Error required internal CMake variable not set, cmake may be
not be
On Tue, Jan 11, 2011 at 11:00 PM, David Cole david.c...@kitware.com wrote:
On Tue, Jan 11, 2011 at 4:21 PM, Crni Gorac cgo...@gmail.com wrote:
[ ... ]
I hope you guys don't mind if I jump in and re-ask related question I
posted couple days ago (I'm sure Michael will soon face the same
Hi,
my project is stored in a git repo with submodules.
I'm wondering if ctest is updating also the submodules when running
ctest Nightly|Continuous etc.
or just the main repo.
I believe not, unless I have some other problems with my test script.
I could do a manual git pull git submodule init
Are you using CMake 2.8.3? If not, you should upgrade. There were some
improvements made w.r.t. ctest_update and git repos in that release. I think
the submodule update was one of them...
HTH,
David
On Wed, Jan 12, 2011 at 12:16 PM, Gerhard Gappmeier
gerhard.gappme...@ascolab.com wrote:
For better or worse (mostly better) we are now heavy users of
ExternalProject. That module works really well to pull in external
dependencies and get them built.
ExternalProject_add has a DEPENDS keyword that lets you specify
dependencies on other External Projects. But an ExternalProject isn't
On 12.01.11 11:56:53, kent williams wrote:
I'm generating a list of files with file(GLOB), but then I want to
remove some filenames from the resulting list.
So essentially I'd like a CMake function like this
function(RemoveItemsFromList ListA ListToRemove)
endfunction(RemoveItemsFromList)
On Wed, Jan 12, 2011 at 12:16 PM, Gerhard Gappmeier
gerhard.gappme...@ascolab.com wrote:
Hi,
my project is stored in a git repo with submodules.
I'm wondering if ctest is updating also the submodules when running
ctest Nightly|Continuous etc.
or just the main repo.
I believe not, unless
On 1/12/2011 12:43 PM, David Cole wrote:
Are you using CMake 2.8.3? If not, you should upgrade. There were some
improvements made w.r.t. ctest_update and git repos in that release. I
think the submodule update was one of them...
Among the improvements was the submodule update command:
On Wed, Jan 12, 2011 at 12:53 PM, kent williams
nkwmailingli...@gmail.com wrote:
For better or worse (mostly better) we are now heavy users of
ExternalProject. That module works really well to pull in external
dependencies and get them built.
ExternalProject_add has a DEPENDS keyword that
It appears there are some inconsistencies with specifying different
SOURCE/BUILD when using functions like ctest_configure, ctest_coverage, etc. I
have tried specifying different binary/source directories but it only seems
like it has been partially implemented. To verify this, I went into
Hello again:
For some reason when I try to compile a simple C++ program, it takes the
wrong compiler, even though I am setting the appropriate one in the
Toolchain file; I am working on Cygwin, and I am trying to compile for a
LInux environment using g++-linux compiler, which I tested it and works
First, use the correct spelling:
-DCMAKE_TOOLACHAIN_FILE
should be:
-DCMAKE_TOOLCHAIN_FILE
If that doesn't solve it entirely, then try using a name without the +
character in it for the PROJECT command.
If that doesn't do it, give us more details, I guess.
I'm not a cross-compiling expert, so
Am Tuesday 11 January 2011 schrub Eric Noulard:
[...]
in fact I think the real source for this is the fact the CPack lacks
the notion
of EXTRA distribution file which is available with autoconf, EXTRA_DIST
var
http://www.gnu.org/software/hello/manual/automake/Basics-of-Distribution.h
tml
While Marcus states what is likely the preferred way, I just added an
ADD_DEPENDENCIES(internal_target external_target) statement that seems to
always work?
Allen
Date: Wed, 12 Jan 2011 13:23:52 -0500
From: Marcus D. Hanwell marcus.hanw...@kitware.com
Subject: Re: [CMake] How to have a
add_dependencies does work to make sure that ExternalProject targets build
before internal targets, if you need that.
But, like Marcus said, you probably need the ExternalProject to be
configured and built before your own calls to find_package... so if you have
that chicken and egg problem, you
Ironically the reason I want to make a target depend on an external
project is that our top level project is already built as an
ExternalProject for all the reasons that have been mentioned.
I need a custom target to depend on THAT external project, just in the
sense that I want it to be built
So add_dependencies should work for you.
Let us know if it's not working like you think it should...
On Wed, Jan 12, 2011 at 3:48 PM, kent williams nkwmailingli...@gmail.comwrote:
Ironically the reason I want to make a target depend on an external
project is that our top level project is
On 1/12/2011 4:21 PM, SF Markus Elfring wrote:
I hope that the involved technical details can be better resolved in a
wider audience.
Now I would like to show a small script which demonstrates a specific
detail in the wording of an error message that I did not expect in this
way.
OK, I got past my JNI issue (must set java version number) - except now I have
a problem with the classpath for building the java files only on windows! On
linux everyone's happy. On windows, using VS2008, the classpath in the project
files have been converted from ';' to spaces?
Any ideas?
What would you like it to print?
It depends on the syntax interpretation if the passed quoted parameter will be
processed as a CMake list.
David Cole pointed it out to me that this is not the case if some data are
enclosed by quotation marks.
2011/1/12 Tobias Ellinghaus h...@gmx.de:
Am Tuesday 11 January 2011 schrub Eric Noulard:
[...]
in fact I think the real source for this is the fact the CPack lacks
the notion
of EXTRA distribution file which is available with autoconf, EXTRA_DIST
var
This currently has no support for watcom's libraries, I'm working on
adding that in the same method basically that visual studio uses for
all of its versions; this is still in progress but I'll come up with
soemhting like a patch in abit.
While doing this I found that there is a bug with VS2010
2011/1/10 Bjørn Forsman bjorn.fors...@gmail.com:
Hi all,
I just found out that CHECK_INCLUDE_FILES ignores CMAKE_FIND_ROOT_PATH. The
documentation for CHECK_INCLUDE_FILES says:
...
The following variables may be set before calling this macro to
modify the way the check is run:
I am using CMake to cross compile with an arm toolchain and getting a linker
error:
undefined reference to `__sync_fetch_and_add_4'
the toolchain has both a shared and static libgcc:
./lib/gcc/arm-linux-gnueabi/4.5.2/libgcc.a
./lib/gcc/arm-linux-gnueabi/4.5.2/libgcc_eh.a
Am Donnerstag, 13. Januar 2011, 02:10:12 schrieb Darren Hollenbeck:
I am using CMake to cross compile with an arm toolchain and getting a
linker error:
undefined reference to `__sync_fetch_and_add_4'
the toolchain has both a shared and static libgcc:
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 c2158199a4744615b199c6bed39cba77a96680c2 (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 bb9cb067bf94bbefd209a71816c2489111694e08 (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 1a7868ccd6889b5224ee87c7cb2787135a672001 (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 e292128bbdeb9e6c2ce7826343edc06afb412068 (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, master has been updated
via f5b43f59de71b9d6954532d484bf19719e5d1157 (commit)
from
67 matches
Mail list logo
