Hi all,
I've been working on a generic cmake stub that allows libraries to be
built with multiple configuration options a.k.a. multilib support in the
style of GCC, on behalf of my employer. This feature allows a user to
build multiple versions of the same library from the same source base
Am 23.04.2014 09:33, schrieb Faraz Shahbazker:
Hi all,
I've been working on a generic cmake stub that allows libraries to be
built with multiple configuration options a.k.a. multilib support in
the style of GCC, on behalf of my employer. This feature allows a user
to build multiple versions of
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14894
==
Reported By:Peter Kuemmel
Assigned To:
On 2013-10-19 20:16+0200 Alexander Neundorf wrote:
On Thursday 17 October 2013, Stephen Kelly wrote:
Brad King wrote:
On 10/17/2013 04:58 PM, Alexander Neundorf wrote:
Yes, that was the idea, but I can't rely anymore on a Foo_LIBRARIES
variable (or a slight variation) being set after a
On 2014-04-18 09:07, Brad King wrote:
On 04/18/2014 08:58 AM, Rolf Eike Beer wrote:
To forbid whitespace and control characters in variable names can IMHO only be
good.
Some people use arbitrary variable names as a way to do key/value tables.
In such cases it is intentional to use arbitrary
I'm getting tons of CMP0043 warnings on my existing project.
I have cmake_policy(VERSION 2.6) set in my project. Why am I being
pestered by warnings? Shouldn't I get a policy value appropriate for 2.6
(so CMP0043 should be set to OLD)?
CMake Warning (dev) in src/CMakeLists.txt:
Policy CMP0043
On 04/23/2014 12:57 PM, James Bigler wrote:
I'm getting tons of CMP0043 warnings on my existing project.
I have cmake_policy(VERSION 2.6) set in my project.
Why am I being pestered by warnings? Shouldn't I get a policy
value appropriate for 2.6 (so CMP0043 should be set to OLD)?
Setting
On 4/23/2014 12:22 PM, Alan W. Irwin wrote:
However, if you discover the problem is a general one for
--find-package and Qt5, then it appears that Qt5 might be a good
illustrative example to use for your renewed effort at developing a
reliable --find-package capability.
I recently ran into a
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14895
==
Reported By:Eric Malafeew
Assigned To:
On 2014-04-23 13:21-0400 Bill Hoffman wrote:
On 4/23/2014 12:22 PM, Alan W. Irwin wrote:
However, if you discover the problem is a general one for
--find-package and Qt5, then it appears that Qt5 might be a good
illustrative example to use for your renewed effort at developing a
reliable
On Wednesday, April 23, 2014 09:22:09 Alan W. Irwin wrote:
On 2013-10-19 20:16+0200 Alexander Neundorf wrote:
On Thursday 17 October 2013, Stephen Kelly wrote:
Brad King wrote:
On 10/17/2013 04:58 PM, Alexander Neundorf wrote:
Yes, that was the idea, but I can't rely anymore on a
On Wednesday, April 23, 2014 13:21:39 Alan W. Irwin wrote:
On 2014-04-23 13:21-0400 Bill Hoffman wrote:
On 4/23/2014 12:22 PM, Alan W. Irwin wrote:
However, if you discover the problem is a general one for
--find-package and Qt5, then it appears that Qt5 might be a good
illustrative
On 2014-04-23 16:21, Alan W. Irwin wrote:
[...] I keep making a plea for a proper fix to bug 9220 because
propagating compiler information (held potentially in a large number
of different environment variables and CMake variables for many
different computer languages) from the principal CMake
On 2014-04-23 17:19-0400 Matthew Woehlke wrote:
On 2014-04-23 16:21, Alan W. Irwin wrote:
[...] I keep making a plea for a proper fix to bug 9220 because
propagating compiler information (held potentially in a large number
of different environment variables and CMake variables for many
Hi Steve:
PLplot not only CMake exports its libraries but also provides library
information in pkg-config form for our users that prefer that form.
Therefore, for this component of our install I need to collect
explicit compile and link flags for Qt5, and it appears to me the best
way to do that
P.S. The results I posted were for cmake-2.8.12.2.
Alan
__
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state
The way I’m doing this now is the following:
a) I edit the CMakeList.txt file(s) and follow
the procedure to create an Xcode IDE project.
This project contains a bunch of targets
including ALL_BUILD, RUN_TESTS, and
Experimental - among others
You should not have to
Alan W. Irwin wrote:
Hi Steve:
PLplot not only CMake exports its libraries but also provides library
information in pkg-config form for our users that prefer that form.
Therefore, for this component of our install I need to collect
explicit compile and link flags for Qt5, and it appears to
I am using
set_property(TARGET mytarget APPEND PROPERTY LINK_FLAGS ...)
multiple times to add various link flags.
But when I inspect the actual link command, I see all my flags separated by
semi-colons and no spaces between them, which is not what I want.
Is this correct behavior for cmake?
On Wednesday, April 23, 2014 06:25:24 PM Nils Gladitz wrote:
On 23.04.2014 18:16, Clinton Stimpson wrote:
I am using
set_property(TARGET mytarget APPEND PROPERTY LINK_FLAGS ...)
multiple times to add various link flags.
But when I inspect the actual link command, I see all my flags
On 23.04.2014 18:16, Clinton Stimpson wrote:
I am using
set_property(TARGET mytarget APPEND PROPERTY LINK_FLAGS ...)
multiple times to add various link flags.
But when I inspect the actual link command, I see all my flags separated by
semi-colons and no spaces between them, which is not what I
On 2014-04-16 06:03, Rolf Eike Beer wrote:
Am 16.04.2014 11:39, schrieb Johannes Zarl:
Instead of ``${var} STREQUAL VALUE'', write:
IF ( var MATCHES ^VALUE$ )
NO, please don't! I try hard to kill all those as it requires
compiling a regular expression for a simple string match. Just
On 2014-04-23 14:30+0200 Stephen Kelly wrote:
Alan W. Irwin wrote:
Hi Steve:
PLplot not only CMake exports its libraries but also provides library
information in pkg-config form for our users that prefer that form.
Therefore, for this component of our install I need to collect
explicit
Running CMake 3.0-rc3 and the docs for target_include_directories say the
paths may be absolute or relative. Indeed the following works as desired:
target_include_directories( MyTarget PRIVATE some/dir )
The docs also mention that generator expressions can be used. However the
following
I'm using cmake version 2.8.12.1 and have just encountered an issue with my
cmake setup where I was using the [Project name]_SOURCE_DIR variable in an
include_directories command and it was being ignored. In my top level
CMakeLists.txt I had:
project(blah)
add_subdirectory(foo)
If I want to create an OSX bundle, but I want the main executable to be a
configured wrapper script written in bash, what is the best way to go about
doing that? It seems that the
Also, how do I get the wrapper script to correctly call the compiled
executable so that the app bundle is
I have CMAKE_OSX_SYSROOT defined as something:
set(CMAKE_OSX_SYSROOT
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk
CACHE LIST OSX sysroot SDK directory FORCE)
Then later I do a find_library command and it finds a library framework in
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 ab3cf9d3f175c83caaa7802635d58efe275899d8 (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 35641d6cec09d7fbc37b07fe3ff43f8740eceb84 (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 e58f7118430e0acc2aae640c10207662e9fbdf26 (commit)
via
20140423)
+set(CMake_VERSION_PATCH 20140424)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
31 matches
Mail list logo
