On 11 June 2015 at 15:22, Johannes Zarl-Zierl johannes.zarl-zi...@jku.at
wrote:
Hi,
I tried several times now to find documentation about how to define
and use target names which seem to have namespaces, like Qt ones.
For example: add_executable( MyProject::some_target ... )
AFAIK
I am proud to announce the second CMake 3.3 release candidate.
Sources and binaries are available at:
http://www.cmake.org/download/
Documentation is available at:
http://www.cmake.org/cmake/help/v3.3
Release notes appear below and are also published at
Hi,
I tried several times now to find documentation about how to define
and use target names which seem to have namespaces, like Qt ones.
For example: add_executable( MyProject::some_target ... )
AFAIK target namespaces are intended for imported targets, not regular
targets:
A NAMESPACE
Hi,
What is the official recommended way to make your project depend on
other libraries using cmake?
Let's say my project wants to depend on a library PKG1 (here PKG1 can
be MPFR, MPC, PTHREAD, GMP, BZIP2, you name it). Let's say the library
is installed in $PKG1/include, $PKG1/lib,
In this example, how do I get
make foo.cc
to work?
0 Thu 16:56:19 yost DaveBook ~/p/c++/cmake/custom-command-target
369 Z% bundle CMakeLists.txt genFoo
#!/usr/bin/env unbundle
# See http://yost.com/computers/bundle/
CMakeLists.txt
cmake_minimum_required(VERSION 3.3.0)
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15610
==
Reported By:trsystran
Assigned To:
Brad King wrote:
We designed
policies to give projects smooth transitions from old to new behavior.
If we suddenly make an error occur in code that currently works
warning-free it will give policies and CMake a bad name.
Ok.
Actually I re-discovered this today in KDE4
I am proud to announce the second CMake 3.3 release candidate.
Sources and binaries are available at:
http://www.cmake.org/download/
Documentation is available at:
http://www.cmake.org/cmake/help/v3.3
Release notes appear below and are also published at
On 06/11/2015 04:18 AM, Petr Kmoch wrote:
Would it be possible to update the Fixed in version field in Mantis?
Thanks. Done.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services
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 annotated tag, v3.3.0-rc2 has been created
at 6cd135ec945ac78f8320becb8c21bd6a745c8f36 (tag)
tagging
On 06/10/2015 05:41 PM, Stephen Kelly wrote:
The presence of the warning from step (1) will mean projects should have
long ported away from encountering the error.
I think the same is true of the existing design of policies. The WARN
behavior of = CMP0011 for the last six years is enough
On 06/10/2015 01:43 PM, Robert Goulet wrote:
Ok I think I got something nicely integrated now.
Thanks. Here are some comments:
+ std::string GetDestination(const char* config=nullptr) const;
Please avoid C++11 constructs.
+std::string cmInstallGenerator::GetDestination(const char* config)
On 06/10/2015 03:52 PM, Domen Vrankar wrote:
I've read it in Mastering CMake and had to search for it today... On
page 42 it says that by default if cmake_minimu_required is missing it
sets policy version of 2.4.
That's because version 2.6 was the first to introduce policies so
using 2.4
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 172a21790ba117af6a03e35c69213a89a5cb86f3 (commit)
via
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15608
==
Reported By:Hendrik Sattler
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15609
==
Reported By:Hendrik Sattler
Assigned To:
20150611)
+set(CMake_VERSION_PATCH 20150612)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
Hi all,
we've been hit by #14894 (http://public.kitware.com/Bug/view.php?id=14894)
in our project when using CMake 3.0.2. According to Mantis, it's fixed in
3.0, but neither tag v3.0.0 nor v3.0.2 seem to contain the fix. v3.1.0 does
contain it. Would it be possible to update the Fixed in version
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 3a10e1458d48b95dd4a064e74e15d3dc7f08c311 (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 7c404c8261b4d7d2d6c41fcf2aa5c992366997b7 (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 31ce82d46d4150d0726929c8e37546bf84ead673 (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 805f726cc05104a5a7234f0307cec9e9cee098db (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 d5690088683baee7e62716f6c7e89640bb77b4aa (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 71d52459900e2be0c78091cb2df6506b22c2c211 (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 41ec14b9b24271d79bd14e806995233d4d7ac687 (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 a51db76d50082dfceb071cc14f8138400544d19f (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 b142dcad64a324b652929f426e2ac59a32dde0c8 (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 532974435f9b723aa6f8f52ffc0cfed46c91d421 (commit)
via
28 matches
Mail list logo
