VERSION_MINOR 10)
-set(CMake_VERSION_PATCH 20171005)
+set(CMake_VERSION_PATCH 20171006)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
I am proud to announce the first CMake 3.10 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.10
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.10/release/3.10.html
Some of the more
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.10.0-rc1 has been created
at 4dc9ffb065de7aa4838991aaa46dfa3581c36044 (tag)
tagging
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, release has been updated
via ecaddda2fea374089d867ad17b8b4700b189f397 (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 8e3b207ebb2243de44c910861c42e4dec4beaf60 (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 4a4d62430be91f13588e62d71932d2f6332fcf2e (commit)
via
On 10/02/2017 11:48 AM, Brad King wrote:
> I'll announce when post-3.10 development is open.
I've branched 'release' for 3.10. The repository is now open for
post-3.10 development. Please rebase open merge requests on 'master'
before staging or merging.
> Meanwhile the following types of
/CMakeVersion.cmake
@@ -1,5 +1,5 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 10)
-set(CMake_VERSION_PATCH 0)
-set(CMake_VERSION_RC 1)
+set(CMake_VERSION_PATCH 20171005)
+#set(CMake_VERSION_RC 1)
https://cmake.org/g
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 a91eb5e41f486628910f189bf40403568af013c7 (commit)
via
Thanks for the followup Gregor.
One thing that concerns me about the property-centric approach is that
I can't think of a way to use properties for generating a custom
scheme that builds the ALL_BUILD target. I would assume this would
run into the same issues and limitations that I have seen in
You are over thinking it. As someone else stated, check if the build directory
and the source directory are the same and if they are you FATAL_ERROR with a
message. Otherwise you can put a single CMakeLists.txt file in the top level to
kick things off.
Plus, I think it is starting to become
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 4ffa4ddd8078918583fc03302fa3c3db2c1ca733 (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 dbb16722ee0669b52ef15b4ee35c7ca623e400c9 (commit)
via
> I find myself setting SKIP_AUTOUIC on *.h and *.cpp files to silence
> CMP0071 warnings.
It's an unfortunate situation.
In many cases (qt < 5.10) it might work to just let AUTOUIC probe
the (moc/uic/rcc) GENERATED files as well by setting
`cmake_policy(SET CMP0071 NEW)`
--
Powered by
On Mittwoch, 4. Oktober 2017 20:01:50 CEST clin...@elemtech.com wrote:
> - On Sep 26, 2017, at 9:07 AM, Sebastian Holtermann sebl...@xwmw.org
wrote:
> >> I updated and I'm getting this:
> >>
> >> CMake Warning (dev) in claro/navigation5/CMakeLists.txt:
> >> Policy CMP0071 is not set: Let
15 matches
Mail list logo
