[cmake-developers] [ANNOUNCE] CMake 3.10.0-rc1 is now ready for testing

2017-10-05 Thread Robert Maynard
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

Re: [cmake-developers] CMake 3.10 feature freeze on 2017-10-02

2017-10-05 Thread Brad King
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

Re: [cmake-developers] Extending XCode scheme generation support

2017-10-05 Thread Steven Velez
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

Re: [cmake-developers] CMP0071

2017-10-05 Thread Sebastian Holtermann
> 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

Re: [cmake-developers] CMP0071

2017-10-05 Thread Sebastian Holtermann
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