Hi everyone,
The Makefile generation code in cmGlobalXCodeGenerator.cxx
(cmGlobalXCodeGenerator::CreateCustomRulesMakefile) does not add a
.SUFFIXES: call, resulting in make having implicit rules in place.
The fix should be trivial, simply adding
makefileStream .SUFFIXES: \n; after the first
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11682
==
Reported By:Maddes
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=11683
==
Reported By:Markus Elfring
Assigned To:
On 01/11/2011 04:18 PM, Alexander Neundorf wrote:
Well, there was the following commit in KDE for two module FindKExiv2.cmake
and FindKipi.cmake
For both modules it adds a variable UPPERCASED_NAME_LOCAL_DIR, which can be
set if the using project doesn't use an externally installed
Thanks for the suggestion.
I just committed this change and pushed it to 'next':
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=66d9cd83519962f320d4b6edefeb15ae250107ae
Cheers,
David
On Tue, Jan 11, 2011 at 4:58 AM, Johan Björk p...@spotify.com wrote:
Hi everyone,
The Makefile
On Tue, Jan 11, 2011 at 11:55 PM, Brad King brad.k...@kitware.com wrote:
Typically we use code of this form:
if(FOO_USE_SYSTEM_BAR)
find_package(BAR)
else()
add_subdirectory(bar)
set(BAR_INCLUDE_DIRS ${CMAKE_CURRENT_SOURCE_DIR}/bar/include)
set(BAR_LIBRARY_DIRS ...)
#
On 01/11/2011 06:13 PM, Pau Garcia i Quiles wrote:
What about something like this?
if( FOO_USE_LOCAL_BAR)
set( CMAKE_PREFIX_PATH ${PROJECT_SOURCE_DIR}/3rdparty )
endif(FOO_USE_LOCAL_BAR)
find_package(BAR)
It searches the local directory first, then goes for system. Looks easier to
On Wed, Jan 12, 2011 at 12:18 AM, Brad King brad.k...@kitware.com wrote:
On 01/11/2011 06:13 PM, Pau Garcia i Quiles wrote:
What about something like this?
if( FOO_USE_LOCAL_BAR)
set( CMAKE_PREFIX_PATH ${PROJECT_SOURCE_DIR}/3rdparty )
endif(FOO_USE_LOCAL_BAR)
find_package(BAR)
It
2011/1/11 Tobias Ellinghaus h...@gmx.de:
Am Montag, 10. Januar 2011 schrub Eric Noulard:
which would at least allow to copy the files into
CMAKE_CURRENT_SOURCE_DIR.
You may generate those file (with configure_file) inside your source tree
and the generated file will be packaged by
2011/1/11 Michael Hertling mhertl...@online.de:
On 01/11/2011 12:55 AM, Tobias Ellinghaus wrote:
Because some information (like latest git commit as version string) is no
longer available when using a source package. Of course I can put the
generated files into the source tree, but that's
On Mon, Jan 10, 2011 at 6:55 PM, Emmanuel Blot eblot...@gmail.com wrote:
On Mon, Jan 10, 2011 at 5:56 PM, marco atzeri marco.atz...@gmail.com wrote:
I don't understand why you find and empty definition
Well, it seems that CYGWIN is not defined:
MESSAGE (STATUS CYGWIN: ${CYGWIN})
MESSAGE
On 01/10/2011 06:24 PM, Andrea Galeazzi wrote:
I've got a main project which relies on several sub-library projects, so
the main CMakeLists.txt
add_subdirectory(W:/Omega/Kernel
${CMAKE_CURRENT_BINARY_DIR}/myLib1)
...
and then I also specify the directory where all libraries have
Manu,
please maintain the discussion on the mailing list as these is a general issue
Sure, sorry (actually I replied to your PM, I have not seen it did not
contain a cc: to the ML)
if you are cross compiling, the target is not cygwin, so CYGWIN is not
defined.
Ok, understood.
However on
Hello,
On Tue, 11 Jan 2011 01:42:47 +0100
Michael Hertling mhertl...@online.de wrote:
Since CMake prefers to specify libraries by path instead of using
-l/-L or the like, there's usually no need for the LINK_DIRECTORIES()
command, IMO.
Sorry to jump into the discussion, but I'm having a
On 11.01.11 10:27:02, Thomas Petazzoni wrote:
Hello,
On Tue, 11 Jan 2011 01:42:47 +0100
Michael Hertling mhertl...@online.de wrote:
Since CMake prefers to specify libraries by path instead of using
-l/-L or the like, there's usually no need for the LINK_DIRECTORIES()
command, IMO.
Hi all,
I was wondering how I can check whether I can successfully compile and
link an executable, without actually running it. CheckCXXSourceCompiles
checks whether I can compile the code, however linking could still fail.
CheckCXXSourceRuns OTOH also tries to run the executable, which causes
Zitat von Thomas Petazzoni thomas.petazz...@free-electrons.com:
On Tue, 11 Jan 2011 01:42:47 +0100
Michael Hertling mhertl...@online.de wrote:
Since CMake prefers to specify libraries by path instead of using
-l/-L or the like, there's usually no need for the LINK_DIRECTORIES()
command, IMO.
Thanks, Fraser. Of course...
If you need to escape a backslash such that the regular expression itself
contains a backslash at a certain point, then you need to double it up. For
example to match the backslash character itself, you need to use [\\], but
to encode other escape chars directly that
Doesn't CheckCXXSourceCompiles link?
I think there's no way to avoid the link in a try_compile...
On Tue, Jan 11, 2011 at 5:49 AM, Marcel Loose lo...@astron.nl wrote:
Hi all,
I was wondering how I can check whether I can successfully compile and
link an executable, without actually running
Hi!
I'd like to use cmake on our project (Synfig - http://synfig.org)
Currently it uses autotools and pkconfig to prepare the code to the build and
install processes. It is a C++/gtkmm application. Currently it builds fine on
linux, builds with lots of hacking on windows under cgwin and nobody
On 12/15/2010 11:10 AM, Mario Rodríguez wrote:
Intel Fortran Composer 12.0 32b
Not currently supported:
http://www.cmake.org/Bug/view.php?id=11517
Sorry,
-Brad
Dear all,
I have the same problem as described before: I use Visual Studio 2010 and
also Intel Fortran compiler 12. This gives
At Tue, 11 Jan 2011 12:40:03 + (GMT),
Carlos Lopez Gonzalez wrote:
Hi!
I'd like to use cmake on our project (Synfig - http://synfig.org)
Currently it uses autotools and pkconfig to prepare the code to the build and
install processes. It is a C++/gtkmm application. Currently it builds
Hi,
probably it could sound a weird question: has anyone ever try to
generate a VS2010 solution with a different toolchain like gcc? In your
opinion is it a possible goal to achieve or the differences between MSVC
and GCC are so big that it's actual impossible?
Cheers
Andreas Schneider ha scritto:
Hello CMake,
my name is Andreas Schneider and I'm working for Red Hat. At the end of last
year I've worked on Dogtag PKI [1]. The Dogtag Certificate System [2] is an
enterprise-class open source Certificate Authority.
The project is written in serveral
Do you get different results if you use CMake from git 'master' or 'next' ??
(Or CMake 2.8.2...?)
In 2.8.3, there was a change introduced that caused problems in *some*
projects. I suspect your project is one of them.
This commit:
On 01/11/2011 09:48 AM, Eric Noulard wrote:
2011/1/11 Michael Hertling mhertl...@online.de:
On 01/11/2011 12:55 AM, Tobias Ellinghaus wrote:
Because some information (like latest git commit as version string) is no
longer available when using a source package. Of course I can put the
Thanks for the explanation David it really helps to narrow down what might be
going on. Couple of comments. Starting fresh this morning everything seems to
be working correctly after simply deleting the build folder and starting over.
So maybe I had a stale cmake variable floating around.
Hi David,
I guess you're right. Further playing with CheckCXXSourceCompiles and
investigating the generated CMakeLists.txt file led me to the conclusion
that the link step is indeed also performed. I was led astray by the
name of the command and my notion that it wraps TRY_COMPILE. Also my
2011/1/11 Michael Hertling mhertl...@online.de:
On 01/11/2011 09:48 AM, Eric Noulard wrote:
[...]
The fact is CPack doesn't know much about source package and
in fact it package source using the CPACK_INSTALLED_DIRECTORIES directory
list.
(look at the generated CPackSourceConfig.cmake)
I
On Tue, Jan 11, 2011 at 10:31 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
Thanks for the explanation David it really helps to narrow down what might
be going on. Couple of comments. Starting fresh this morning everything
seems to be working correctly after simply deleting the build
Yes... this confused me when I first encountered it as well.
TRY_COMPILE is misnamed in CMake.
In functionality, it's actually a TRY_LINK operation.
On Tue, Jan 11, 2011 at 10:59 AM, Marcel Loose lo...@astron.nl wrote:
Hi David,
I guess you're right. Further playing with
On Tuesday 11 January 2011 16:01:14 Andrea Galeazzi wrote:
Hi Andreas,
Hi Andrea,
I'm a dyed-in-the-wool Java developer (and also Fedora user) so it makes
me very happy to know that someone are working to integrate Java in
CMake. My question is: shouldn't Ant be enough? Or better, Could
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
|- CMakeLists.txt
/my/project/path/B - include
This is wonderful and I am making progress but I have a few more questions.
Assume I am using CMake 2.8.3 (as it will become the requirement).
For external Dylibs and frameworks that my project depends on will the new way
that bundle utilities work still copy the frameworks (like Qt
On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
This is wonderful and I am making progress but I have a few more questions.
Assume I am using CMake 2.8.3 (as it will become the requirement).
For external Dylibs and frameworks that my project depends on
Thanks for the help, David and and Fraser! I have it working.
On Tue, Jan 11, 2011 at 4:33 AM, David Cole david.c...@kitware.com wrote:
Thanks, Fraser. Of course...
If you need to escape a backslash such that the regular expression itself
contains a backslash at a certain point, then you need
Hi,
with the new external project support in CMake it is very easy to build
complex projects in one run, but it is still complicated to resolve the
different library paths on windows. There is a bug in the Cmake
bugtracker describing the problem very well, and as somebody pointed out
it also
Am Dienstag, 11. Januar 2011 schrub Eric Noulard:
[many great ideas how to solve my issue]
Thank you very much folks. I guess I will find something with the pointers you
gave me. :-)
Current source packaging is more or less a hack.
Useful hack, but a hack.
Better than nothing I guess.
Hello,
My experience with CMake programming is evolving. I try to update some scripts
which were published with the feature request Add simple CMake build files.
https://sourceforge.net/apps/trac/cppcheck/ticket/1092#comment:5
A concern that I try to tackle as a next step for this software
On Tue, Jan 11, 2011 at 6:22 PM, David Cole david.c...@kitware.com wrote:
On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
This is wonderful and I am making progress but I have a few more
questions. Assume I am using CMake 2.8.3 (as it will become the
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 functionality, it's actually a TRY_LINK operation.
Update the doc?
Eike
signature.asc
Description: This is a digitally signed
On Tuesday 11 January 2011 16:01:14 Andrea Galeazzi wrote:
Hi Andreas,
Hi Andrea,
I'm a dyed-in-the-wool Java developer (and also Fedora user) so it makes
me very happy to know that someone are working to integrate Java in
CMake. My question is: shouldn't Ant be enough? Or better,
2011/1/11 Andreas Schneider a...@redhat.com:
On Tuesday 11 January 2011 16:01:14 Andrea Galeazzi wrote:
Hi Andreas,
Hi Andrea,
I'm a dyed-in-the-wool Java developer (and also Fedora user) so it makes
me very happy to know that someone are working to integrate Java in
CMake. My question is:
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 8c041faf14490aa4e8838032085940dd15d642c5 (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 7ebfa8218b58d0b835fa23a6e40afe8043a17d7e (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 3272d2d96fc047cbee7610ec8747f21f57752c1e (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 b524f864ca4928b266a3d5504cb5e62f9ca6038a (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 b8e5d7b49c4c00c80f861456c185daba987284c3 (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 333e707d9578f7a98e118c74a8bb513c7babb8ed (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 18180cdb50fd254b70cb757fef4cfbb394ceaaab (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 984ca06a8ef41ef8b16e820db687be44f4c19ec5 (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 c73babf5d2f8bb93bef9adc947a59cc4b8189853 (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 f04bbdf1d4a8b1b1d5f4a2ceae2870af5c6d417e (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 4ab987b7ccc62abab700cb02b75460cf2a6f7862 (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 d4ed72e3bb4d3ca85750c21eae21a0273207e0dc (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 764015c2840b1059093e8af86dcbf96e048d2dfa (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 9a81f0dd0cd45715456b4d298403833b22832cf0 (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 7decc70eead665f75872dcf0b95a088d3b307879 (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 50e9e7d34505a53ca73f64a28f6a476e570ca481 (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 46ed6c65a8b4a8c56cd66fca7bbaec49d1587010 (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 68a411cbe48d1a7fed01f53ba017fafcc7159cc5 (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 9cafd412c619364ba36ddd9f34f0b40aa211 (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 c768b354f38df55c9ea8fe2f2176208a8ff4594f (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 ffa69d506a27cda31a6eb64006939e9771159cf1 (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 3baf7846b502434a2b78fed58c93108368cc1a09 (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 e3ef6bb0b81d83753f2fda65f4272fb653cfd3c0 (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 90e9b65f10f7e96284d2c75907326faef64c669a (commit)
from
67 matches
Mail list logo
