Hi,
There are some places in cmake code which are commented as being for
backward compatibility, but which seem to be covered by no policy, and some
of which have a TODO item for addressing that.
diff --git a/Source/QtDialog/QCMake.cxx b/Source/QtDialog/QCMake.cxx
index 0fe5f8c..31eb79d
On 02/10/2014 03:41 AM, Stephen Kelly wrote:
diff --git a/Source/cmAddCustomCommandCommand.cxx
b/Source/cmAddCustomCommandCommand.cxx
index 5634849..e967e3c 100644
--- a/Source/cmAddCustomCommandCommand.cxx
+++ b/Source/cmAddCustomCommandCommand.cxx
@@ -164,6 +164,7 @@ bool
On 02/07/2014 05:19 PM, Steve Wilson wrote:
On Feb 7, 2014, at 3:01 PM, Brad King wrote:
-DCMAKE_BUILD_TYPE=\${CTEST_CONFIGURATION_TYPE}
I have tried adding that to my test call (--build-options) but it doesn't
seem to make any difference.
Oops, I picked the wrong line for an example. We
On 02/09/2014 06:06 AM, Stephen Kelly wrote:
+ Why is PLATFORM_ID in the generators section?
It is a behavior implemented by the generators and it is a new
feature. I wasn't sure where else to put it. However, see below.
Other genex related
+ changes include
+ * Nullary $CONFIG
+
On 2014-02-08 06:10, Stephen Kelly wrote:
3) Assuming you still have no local changes,
git reset --hard origin/LinkOptionsCommand
Worth adding: If you *do* have local changes, you can (before running
the above) set them aside with git stash and (after running the above)
restore them with
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14747
==
Reported By:Daniel Levin
Assigned To:
Someone just posted this comment to one of my blogs:
(http://www.kitware.com/blog/home/post/434)
I don’t know if CMake or Ninja (or LLVM’s build rules) are at fault
here, but when I build Clang and LLVM under CMake and Ninja, parallelism
often drops to zero when a static library is being
LinkedIn
I'd like to include you in my network to share updates and stay in touch.
- Jayesh
Jayesh PATEL
Technical Lead at Grit Innovation
Australia
Confirm that you know Jayesh PATEL:
Hello,
Is there a way to get the effective include directories and compile
definitions for a target, including those specified at the directory level
and any INTERFACE_INCLUDE_DIRECTORIES and INTERFACE_COMPILE_DEFINITION on
targets that are required via target_link_libraries?
Iterating
Lars Christensen wrote:
Hello,
Is there a way to get the effective include directories and compile
definitions for a target, including those specified at the directory level
and any INTERFACE_INCLUDE_DIRECTORIES and INTERFACE_COMPILE_DEFINITION on
targets that are required via
Should I file this as a bug in the issue tracker then?
Sure. Especially if you have an easy way to reproduce. (Either
reference an external, publicly available project we can just build
and get it to happen, or attach a CMakeLists that demonstrates the
issue if possible.)
That way, we can
I understand the cross-compile process reasonably well. I also have a
fairly good feel for ExternalProject_Add, What I'm trying to do is combine
these ideas but, I am confused about one general issue.
While I am cross-compiling the Linux kernel, I discover that the kernel
requires zlib. So, I
Hello,
I don't know if I overlook something or the framework/CFBundle support on Mac
OS is rarely.
Most of the things I have already implemented as post-build commands but are
there also CMake ways of doing such things?
.) Adding resources to CFBundles? (Resources for frameworks are
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 ccde695ba8a16cea8554a0a41e41efc6181013e0 (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 0d2b20bc56bda9ef979b057c137c24aa75381915 (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 ed0a42d431923605306e5beb1514fc11cf048fb4 (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 e180c1def031ae22c4843c308d6d3710ebcb18e2 (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 f67ab2a920cfce8db31ce214a198670cab31470a (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 3c23873e04c03a9ac877a9a67325b26907e28309 (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 6e149e1591249d4666b4f7eefd58f414c4b5d973 (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 d7133c0288e82627569071c84dfaa94516deb9eb (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 cdcf23bde25e4f9f1cdb88604a38045262c41a8b (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 c9a489aec6b64ab6bbb7836611b8047db2301cc8 (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 c00d84cdf34808f66d83e78fac5b741d980d8796 (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 d51dc24e2b18e5d0ba61eccd55e34fb729d765fa (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 27d3974c66f42f1f37fb60d0e07cd9dd2ee912cf (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 7b38931a08c9f1ae8615256f3bdb3d95f3427591 (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 89d49eccc57b0e99924d7abe4a9e768d2ed4e0d4 (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 53f97f2e0739abfd3e6f9377b6d510859322 (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 8be986b6210241610c8ae8e89f7ef8793226b0ef (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 d6c69792dd0f86f99162f7c2085a5d34c7fddb0d (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 e90fc2d1560d101b710749ecfbfb21bb73b35a19 (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 b687e9c08c9125295645713b9201dab8f917f658 (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 164249af5aa9d2eb97b3b1d728e648a84d91ad54 (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 5d05124cb7222819f82eef33b14390444923e962 (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 25035cbc788c8eee7b867c79e8cb17faab0e3c1d (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 f4e0fc2f866747af636e6c0eb43c717773275dd6 (commit)
via
37 matches
Mail list logo
