The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=12564
==
Reported By:Andras Lasso
Assigned To:
I'm glad to inform you that I recently wrote an article about CMake
published in the Italian computer science magazine IoProgrammo
(www.ioprogrammo.it http://www.ioprogrammo.it/) on November issue. A
next one is gonna be published on December. I seize this opportunity to
congratulate all the
Thanks, I think I must be doing something wrong elsewhere then, because I
follow the same syntax as what you wrote.
However, it is not working for me which means my error must be somewhere else.
I had thought, based on a stack overflow link, that CMAKE_STATIC_LIBRARY_PREFIX
was only for linking
On 11/08/2011 01:36 PM, Schuchard, Matthew wrote:
Thanks, I think I must be doing something wrong elsewhere then, because I
follow the same syntax as what you wrote.
However, it is not working for me which means my error must be somewhere else.
Could you provide a minimal but complete
Hi All,
I have one issue connected with generated code.
What is recommended way to proceed with generators which provides
source which is dynamic?
The setup looks like: generator has some input, and depending on this
input files are generated.
From cmake point of view I need only this list of
Hi all,
I've updated one of my dashboard machines to 10.7 and Xcode 4.2 and am having
trouble with the Xcode generator. It fails with:
-
The C compiler /usr/bin/llvm-gcc is not able to compile a simple test
program.
It fails with the following output:
Change Dir:
More info, please...
I assume you mean CMake 2.8.6 and not 2.4.6, as in the subject line... :-)
Are you setting CC and CXX before calling cmake -G Xcode ../CMake?
That's not a valid way of setting the compiler to a different compiler
with the Xcode generator.
Are you trying to build CMake or
Excellent! Will the article be available online, or do you have to get
a copy of the November issue of the magazine to read the article?
Thanks,
David C.
Kitware, Inc.
On Tue, Nov 8, 2011 at 3:54 AM, Andrea Galeazzi galea...@korg.it wrote:
I'm glad to inform you that I recently wrote an
On Tue, 8 Nov 2011 11:06:46 -0500, David Cole said:
More info, please...
I assume you mean CMake 2.8.6 and not 2.4.6, as in the subject line... :-)
Doh!
Are you setting CC and CXX before calling cmake -G Xcode ../CMake?
Yes, see:
http://www.cdash.org/CDash/viewNotes.php?buildid=1705589
Hello,
I have 2 build configurations for the same source code and I am generating
visual studio 2005 projects. So for the first configuration I need different
defines than for the second configuration. So I do like this:
mkdir build1
cd build1
cmake -DPORT=bla ../source
mkdir build2
cd build2
On 11/08/2011 03:30 PM, Łukasz Tasz wrote:
Hi All,
I have one issue connected with generated code.
What is recommended way to proceed with generators which provides
source which is dynamic?
The setup looks like: generator has some input, and depending on this
input files are generated.
I've got a question related to the way CMake handles files that are non-existant
at CMake-time, but which are listed as OUTPUTs of an add_custom_command, and are
included in a source_group. I'm using CMake 2.8.5 and the Visual Studio 2010
generator.
I have a Python script which reads a .resx file
On 11/08/2011 09:08 PM, Tom Deblauwe wrote:
Hello,
I have 2 build configurations for the same source code and I am generating
visual studio 2005 projects. So for the first configuration I need different
defines than for the second configuration. So I do like this:
mkdir build1
cd
On 11/08/2011 10:56 PM, Matthew LeRoy wrote:
I've got a question related to the way CMake handles files that are
non-existant
at CMake-time, but which are listed as OUTPUTs of an add_custom_command, and
are
included in a source_group. I'm using CMake 2.8.5 and the Visual Studio 2010
I needed this patch for an app I'm working on.
Only very lightly tested (i.e. my library loads now :-)
--- FindX11.cmake.old 2011-11-09 01:52:59.352674210 +
+++ FindX11.cmake 2011-11-09 01:56:23.047527447 +
@@ -33,6 +33,7 @@
#X11_XTest_INCLUDE_PATH,X11_XTest_LIB,
On Tue, Nov 8, 2011 at 12:08 PM, Tom Deblauwe tom.debla...@traficon.com wrote:
Hello,
I have 2 build configurations for the same source code and I am generating
visual studio 2005 projects. So for the first configuration I need different
defines than for the second configuration. So I do
I'm trying to set up component based packaging (with RPM). I have it
working, I just can't control the name.
I would like it to be something like
comp-9.9.9-01-rhel5-i686.rpm
But currently it uses $CPACK_PACKAGE_NAME instead of the component name.
--
Gantry S. York
Digitascio, Inc
--
2011/11/9 Gantry York gantry.y...@digitascio.com:
I'm trying to set up component based packaging (with RPM). I have it
working, I just can't control the name.
You currently don't have full control over the package name.
- for a non-component packaging you can chose the package
name by
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 67e3b64ab535573d27c5ae20be3afefe612654bd (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 d8d4e801acf486bd63d73c00733faeba8b2eea71 (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 6c2f30822bc4eec4bd3e47d0f06fbf9627a21d45 (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 3452dadf89db0bc6cfc6e80d2caf0b6c7891d120 (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 7ee0f580eb9714593b062f8ce6ca190ac50d6cd8 (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 e4085569a95c223ff27680d48b9019196fb25db3 (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 a985a9e0f783cf2e8c84491145a52e482ef03ae0 (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 5a3a5ba0522df360a9d855958a06dce4b01413f1 (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 a5579b76f05166815a809e66d488540e24813132 (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 6478502efcfc2e1c2e50ca2ff124a18d00e55a05 (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 437deb33563b2011f3713e51cf53671780534ef1 (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 96dd530410d13238a697d1d9df9c9b6804855f74 (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 fb48538ed184d1fd0cb0b9c748c823e56f8891f3 (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 5675ec5e493e01e10d9ad8d8b60eac62033f31c2 (commit)
from
32 matches
Mail list logo
