Hi,
when using out-of-source builds and the Eclipse CDT project generator, a
linked resource is created in the Eclipse project file, which points to
CMAKE_SOURCE_DIR, so the user can browse the source directory.
Now, when CMAKE_BINARY_DIR is a subdirectory of CMAKE_SOURCE_DIR (e.g.
On Sunday 23 October 2011, Alexander Neundorf wrote:
Hi,
I just used ProcessorCount.cmake the first time.
I noticed a small issue:
AFAIK module file names in cmake use CamelCase, while the macros/functions
use underscores: SomeCoolStuff.cmake - some_cool_stuff()
ProcessorCount.cmake
On Tuesday 01 November 2011, Eric Noulard wrote:
2011/11/1 Alexander Neundorf neund...@kde.org:
...
and I'd be very happy if this could be solved.
Me too.
I'll dig a little bit on the Eclipse side again, but generating 2
files in the source does not look like a big deal.
The thing is that
2011/11/1 Alexander Neundorf neund...@kde.org:
On Tuesday 01 November 2011, Eric Noulard wrote:
2011/11/1 Alexander Neundorf neund...@kde.org:
...
and I'd be very happy if this could be solved.
Me too.
I'll dig a little bit on the Eclipse side again, but generating 2
files in the source
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12549
==
Reported By:void.pointer
Assigned To:
On Tue, Nov 1, 2011 at 5:58 AM, Alexander Neundorf neund...@kde.org wrote:
Hi,
when using out-of-source builds and the Eclipse CDT project generator, a
linked resource is created in the Eclipse project file, which points to
CMAKE_SOURCE_DIR, so the user can browse the source directory.
Now,
On Friday, October 28, 2011 07:58:25 Clinton Stimpson wrote:
On Friday, October 28, 2011 06:21:23 am Stephen Kelly wrote:
On Friday, October 28, 2011 13:56:20 Thiago Macieira wrote:
On Friday, 28 de October de 2011 13:13:20 Stephen Kelly wrote:
* If you want to be easily found for others
On Tue, Nov 1, 2011 at 6:11 AM, Alexander Neundorf neund...@kde.org wrote:
On Sunday 23 October 2011, Alexander Neundorf wrote:
Hi,
I just used ProcessorCount.cmake the first time.
I noticed a small issue:
AFAIK module file names in cmake use CamelCase, while the macros/functions
use
On Friday, October 28, 2011 13:13:20 Stephen Kelly wrote:
== Summary ==
I'm considering adding some cmake files to Qt, which would be installed by
Qt, and which would make it easier for CMake based projects to depend on
Qt.
I'm CC'ing the cmake developers too see what they think of the
On 10/31/2011 5:20 PM, Alexander Neundorf wrote:
Not sure what the other cmake developers would think about supporting an
additional file format for the Config.cmake files, e.g. xml or json, so they
could be easily used and generated also by other tools. I.e. not only by/for
cmake, but basically
On Tuesday 01 November 2011, Brad King wrote:
On 10/31/2011 5:20 PM, Alexander Neundorf wrote:
Not sure what the other cmake developers would think about supporting an
additional file format for the Config.cmake files, e.g. xml or json, so
they could be easily used and generated also by
On 11/1/2011 1:20 PM, Alexander Neundorf wrote:
Would you prefer XML, JSON or something else ?
I have no preference. If the format is simple enough to parse in CMake code
then it can't be too hard to parse with a C++ implementation later ;)
However, note that you're trying to set a precedent
These two patches address some issues I found:
-ExternalProject_Add(... DEPENDS something) does not work if that something is
not itself created by ExternalProject_Add(). Fixed and testcase added.
-The testcases for ExternalProject fail to detect on my German system my
Subversion version. We
On Tuesday 01 November 2011, Brad King wrote:
On 11/1/2011 1:20 PM, Alexander Neundorf wrote:
Would you prefer XML, JSON or something else ?
I have no preference. If the format is simple enough to parse in CMake
code then it can't be too hard to parse with a C++ implementation later ;)
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=12550
==
Reported By:Aaron Simmons
Assigned To:
Hello! Can you help me, please?
I'm generating VS 2010 solution/projects and finally when I open main
solution file I can SEE only ALL_BUILD project.
All builds fine, all projects exists. But I can't see them and work with
sources from them directly. What's wrong?
--
Powered by www.kitware.com
2011/11/1 Anton Sibilev anton.sibi...@gmail.com:
Hello! Can you help me, please?
I'm generating VS 2010 solution/projects and finally when I open main
solution file I can SEE only ALL_BUILD project.
All builds fine, all projects exists. But I can't see them and work with
sources from them
2.8.6. Just a minute later found that problem was in incorrect FOLDER
property... Sorry!
2011/11/1 Eric Noulard eric.noul...@gmail.com
2011/11/1 Anton Sibilev anton.sibi...@gmail.com:
Hello! Can you help me, please?
I'm generating VS 2010 solution/projects and finally when I open main
Hi,
I'm new to this list and just recently started to use CMake and CPack.
So far I'm very pleased but there's one thing that I think could use
some improvement;
As far as I van see (from Wiki) the RPM generating backend of CPack uses
CPACK_PACKAGE_DESCRIPTION_FILE if
2011/11/1 Alexander Neundorf neund...@kde.org:
Hi,
when using out-of-source builds and the Eclipse CDT project generator, a
linked resource is created in the Eclipse project file, which points to
CMAKE_SOURCE_DIR, so the user can browse the source directory.
Now, when CMAKE_BINARY_DIR is a
2011/11/1 Erik Hofman e...@ehofman.com:
Hi,
I'm new to this list and just recently started to use CMake and CPack.
So far I'm very pleased but there's one thing that I think could use
some improvement;
As far as I van see (from Wiki) the RPM generating backend of CPack use
You can get up
2011/11/1 Alexander Neundorf neund...@kde.org:
On Tuesday 01 November 2011, Eric Noulard wrote:
[...]
So before making the build dir as a source subdir case FATAL, are you sure
we really don't want to authorize the generatiion of .project
.cproject in the source dir
in this very particular
On Mon, Oct 31, 2011 at 11:59 PM, Steven Velez sbv1...@gmail.com wrote:
Hi Robert,
I reviewed the patch, and I am not sure vsAuxPath should be a
requirement. As I stated earlier, we've gotten the binding to work
acceptably without it and I assume others have as well. Further, some
users
I realize this is a feature but since I've provided the patch files that
implement this (attached to the bug below) I was hoping you wouldn't mind.
It's a small feature addition for source control bindings. Read more here:
http://public.kitware.com/Bug/view.php?id=12549
-
Robert Dailey
On Mon, 31 Oct 2011 17:27:38 -0700, Jerry said:
The OS X .dmg installer, cmake-2.8.6-Darwin64-universal.dmg, at http://
www.cmake.org/cmake/resources/software.html, failed to install symlinks
in /usr/bin as promised. I received six messages, I think from the Cmake
app, of this nature:
Failed
On 10/28/2011 06:20 PM, Jose wrote:
I give up. [...]
Never say die. ;)
[...] I solved the problem with the solution Michael gave me. Actually
this linking flag : -Bstatic
was the causant of the troubles.
Out of curiosity: We've seen the failing link line; how does the
successful one look
For some reason the built in variable like MSVC_VERSION and MSVC do not
have any value unless the project() command is called first. Can someone
explain why?
-
Robert Dailey
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Tuesday 01 November 2011, Robert Dailey wrote:
For some reason the built in variable like MSVC_VERSION and MSVC do not
have any value unless the project() command is called first. Can someone
explain why?
Without checking...
IIRC, the project() call enables by default the C and the CXX
On Tue, Nov 1, 2011 at 11:22 AM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Tuesday 01 November 2011, Robert Dailey wrote:
For some reason the built in variable like MSVC_VERSION and MSVC do not
have any value unless the project() command is called first. Can someone
explain why?
Just to be clear, I am not advocating having to deal with the perforce
SCC integration dialog for every project in the solution. In our set
up, we need to deal with it once for the solution... without having
access to AuxPath. However, I do imagine, that it probably has
something to do with
I'm trying to use CPACK to generate a binary installer, I can get a source
installer to sort of work, but I don't need the source at all. We do out of
source builds, but I have CMAKE place my libs and bins back into the source
tree under a parent/project/lib and parent/project/bin directory
I don't see a way to join or normalize paths in CMake. For example, there
is a base path that the user can specify in a cache variable, like so:
BASE_PATH = T:/stuff/
Later in my CMake script, I join a subpath to it like so:
${BASE_PATH}/morestuff
The problem is, this becomes:
On Tuesday 01 November 2011, Robert Dailey wrote:
I don't see a way to join or normalize paths in CMake. For example, there
is a base path that the user can specify in a cache variable, like so:
BASE_PATH = T:/stuff/
Later in my CMake script, I join a subpath to it like so:
There is a one-time operation I need CMake to perform the very first time a
user generates. This operation involves copying several files from a remote
server (third party libraries) and placing them in the binary dir.
Right now I'm attempting to do this via a cache variable:
set( COPY_DONE
INSTALL rule DESTINATION arguments are intended to be non-full path
directory names, that get placed underneath CMAKE_INSTALL_PREFIX.
When CPack runs, it tries to build the install target after setting a
value into CMAKE_INSTALL_PREFIX.
Since your install rules ignore this, by giving full path
2011/11/1 David Cole david.c...@kitware.com:
INSTALL rule DESTINATION arguments are intended to be non-full path
directory names, that get placed underneath CMAKE_INSTALL_PREFIX.
When CPack runs, it tries to build the install target after setting a
value into CMAKE_INSTALL_PREFIX.
Since
When generating for Visual Studio, is there a way to make projects in debug
configuration have a different set of include directories from the release
configuration?
-
Robert Dailey
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
Not yet
On Tue, Nov 1, 2011 at 4:30 PM, Robert Dailey rcdai...@gmail.com wrote:
When generating for Visual Studio, is there a way to make projects in debug
configuration have a different set of include directories from the release
configuration?
-
Robert Dailey
--
Powered by
On Tue, Nov 1, 2011 at 3:32 PM, David Cole david.c...@kitware.com wrote:
Not yet
Meaning there are plans in the works to add such functionality in the near
future?
For now I guess I could actually hard code VS environment variables in my
include directory strings, such as $(Configuration).
--
On Tue, Nov 1, 2011 at 4:33 PM, Robert Dailey rcdai...@gmail.com wrote:
On Tue, Nov 1, 2011 at 3:32 PM, David Cole david.c...@kitware.com wrote:
Not yet
Meaning there are plans in the works to add such functionality in the near
future?
For now I guess I could actually hard code VS
Well if you need any help coding the feature let me know. I'm already
liking the idea of adding features I want myself into CMake :)
Thanks!
-
Robert Dailey
On Tue, Nov 1, 2011 at 3:47 PM, David Cole david.c...@kitware.com wrote:
On Tue, Nov 1, 2011 at 4:33 PM, Robert Dailey
Thanks, I didn't even think of doing it like that :)
This works great. Thanks!
-
Robert Dailey
On Tue, Nov 1, 2011 at 3:46 PM, Fraser Hutchison
fraser.hutchi...@googlemail.com wrote:
Hi Robert,
I think you need something like:
if( NOT COPY_DONE )
... do work
On Nov 1, 2011, at 6:56 AM, Sean McBride wrote:
On Mon, 31 Oct 2011 17:27:38 -0700, Jerry said:
The OS X .dmg installer, cmake-2.8.6-Darwin64-universal.dmg, at http://
www.cmake.org/cmake/resources/software.html, failed to install symlinks
in /usr/bin as promised. I received six messages,
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 d86be11b853ef01f6526d19f3bd24f65bec2d054 (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 6b93e43277c4ddf50a549f1d7e0e80e621315a57 (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 a476a91a749d49c8f75da0ffbc2ee1fd3f882b8c (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 a2d0d66b89a11fa9a7d280d80f5ef58b87c7dfac (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 9d87a9251eef7008731fc4182cddccf5916bf541 (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 55eda4a06013fd4d09728a5a96edcc6fc4d1f988 (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 e0d97b672875ab83e4e30ddd00746860e6e1fd87 (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 c2300e6265400089b8efb5e34e4d33e1425354ac (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 5531e5e162d448d6f63cea509c2a634b7fea0654 (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 09dfcfb6cbc15588c4cc6fcff76a9e2d1559d529 (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 55659c4ea932851c4d969b83e919c3dacec2505e (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 a39c195bc56656e86b4d647f50f987eb955d240b (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 d4621bdb308056f286a445fd01444b1cf8638119 (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 b447c1d1dbdd3b6adebae779eedf0ca4fbde329b (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 b46baba2aab2a9ef0fadfb5268a3c57f09fa5422 (commit)
via
58 matches
Mail list logo
