_VERSION_MINOR 7)
-set(CMake_VERSION_PATCH 20170110)
+set(CMake_VERSION_PATCH 20170111)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Hi,
We have a custom command for a third-party utility (genreflex, from the
ROOT system) which has a directive:
IMPLICIT_DEPENDS CXX ${CMAKE_CURRENT_SOURCE_DIR}/classes.h
How would I, either as an extra COMMAND or as a separate custom command,
manually invoke the configured CXX compiler
You can temporarily unset CMAKE_SIZEOF_VOID_P before calling
write_basic_package_version_file. See for instance
https://bitbucket.org/eigen/eigen/src/ff6170e75ab07d74d8f7dd21af777a94799d168d/CMakeLists.txt?at=3.3=file-view-default#CMakeLists.txt-541:545
.
On Tue, Jan 10, 2017 at 7:52 PM, Ghislain
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 55f86ceb1f2e5e925a678e9decf181141bb301dc (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 19e5a8a29816e5f9a61b53a444a127b87c55c12e (commit)
via
I would like to run a custom command on the zip file generated by
cpack. The idea is that I want to calculate its sha256 checksum.
Unfortunately it seems the zip file cannot be a target in a
CMakeLists.txt file or I'm doing something wrong.
Can someone give me a hand?
--
Gonzalo
Dear Ghis,
the easiest long-term fix would be an own glmConfig.cmake file.
The command write_basic_package_version_file uses a template with those
pointer checks. The glm-developers could simply copy the template to
their source directory, remove the unneeded lines and run the
configure_file
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 25b5e76e15b3b5fe6e0aacd5345ecd1f3d360e5b (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 b526e70725cc58b1bc51c0d5c4f3f9c00a908387 (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 f1926db39ba43c3ba8d3397425fd93de71d6bbf1 (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 202c24a3e137558723f8d781ccbdd3665daa8b2e (commit)
via
I was wondering if anyone was familiar with Chocolatey and whether there
are plans to add support for it in cmake/cpack.
For those that don't know, Chocolatey is a small Windows' utility
similar to Debian's apt-get. It allows simple management of packages
(binaries mainly).
--
Powered 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, next has been updated
via b4636f780f83e0da8431a5cfd6725878baf65aab (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 deefc1319b83543ff4ffe65feded4ddc290b6a54 (commit)
via
Dear all,
I am currently hit by an issue with the CMake detection of a header-only
library [1]. The library is built on a 64-bit machine and packaged for all
other architectures supported by Debian.
However, CMake detection fails on 32-bit platforms with the following error:
```
Any attempt to
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 0287d41c435914431fee29ce064a480c5eb59174 (commit)
via
Hello,
after hours and hours of searching and trying to get it to work I hope
someone here can help me as I'm now out of ideas. I'm trying to build an
OpenFX plugin for DaVinci Resolve (a movie color grading software,
https://www.blackmagicdesign.com/products) via CMake. Resolve is
delivered
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 44c85ae38a4401379c411a1e3fefce8aefce0eed (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 014c446aeeecb24be2a0494f1031cd992fd3d045 (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 d954016868c66aa78b66bd94c2d744b8cc42738a (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 14f8a662df08f79471f199ff40444593933e509d (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 31e1ebf7015852bae9dbc5204e37534ae29c8548 (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 63a8770f08d0bcb239ceaaa18f5a6ee99af38be2 (commit)
via
There's a couple of ways to fix this; for instance, on Windows I could
use NO_DEFAULT_PATH on the find_library call and that would resolve the
issue. The main reason why I haven't done this yet is because I think
that's a packaging bug in the Vulkan SDK side which I was going to
report there (I
That makes sense! Removing the variable from PATH does indeed fix the issue.
It is not a blocking issue for me.
I agree that this is a Vulkan packaging issue. However, since you are
looking for $ENV{VULKAN_SDK} in the find module and assuming it exists,
then it 'should' override the other path?
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 da90f247541d7a3e3cd8ae32fe74450e8ffb46b8 (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 f79c8a9fa000f7e3b4cdb984cd91a709cb42bce6 (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 3ae275f4f8a4dcf6721c0112b7d4cfcb9366a35e (commit)
via
Hi,
the problem here is that the Vulkan SDK helpfully adds
D:/VulkanSDK/1.0.37.0/Bin into PATH, while the Vulkan module dutifully
searches Bin on x64 and Bin32 on x86. However, because /Bin is in the
PATH, and because the libraries for both architectures are named the
same, it will pick up the
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 ae4b031f2bcd15bb06edb97a217d8461926cc950 (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 29234c055a20494f76f9653fa11df5bc7d901ebd (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 4b74150218a9c0ab28070d10c87f4391b724bba6 (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 9239141e954c6b9eaba53fcad46fa2de24d8ba44 (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 89a350e455008070ec9c4c6ed55e1e4fb681921b (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 2c8eb2696a8f3505d45ed5accfa94b3e5541e169 (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 c43cf158d74460440dc5a3d0aec984c754f57958 (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 ea62999f457a4263702a7f01e2c9bd8070da1e01 (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 039a7df9bada6d061f34728a0bb57fdcb9e277c1 (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 914728f8d724e834a402619d05309ad8154ba59d (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 b641f2b873d55f8ba7b99db906fe6a780a910369 (commit)
via
(Full source is available at https://github.com/rjhansen/sherpa )
I have a Qt 5.7 application which I'm trying to migrate from qmake to
cmake 3.7. So far it almost works on OS X, except when it comes to
making a proper app bundle.
The relevant contents of my CMakeLists.txt are as follows:
41 matches
Mail list logo
