[cmake-developers] [ANNOUNCE] CMake 3.9.1 available for download

2017-08-10 Thread Robert Maynard
We are pleased to announce that CMake 3.9.1 is now available for download.

Please use the latest release from our download page:
  https://cmake.org/download/

* The "find_" command "PACKAGE_ROOT" search path group added by
  CMake 3.9.0 has been removed for the 3.9 series due to regressions
  caused by new use of "_ROOT" variables.  The behavior
  may be re-introduced in the future in a more-compatible way.

Thanks for your support!

-
Changes in 3.9.1 since 3.9.0:

Björn Esser (2):
  Utilities/Sphinx: Restore compatibility with Sphinx pre-1.2
  Help: Silence warning about document not included in toctree

Brad King (8):
  UseSWIG: Fix when Java is enabled as a language
  VS: Fix VCTargetsPath detection
  Android: Fix support for CMAKE_SYSROOT without CMAKE_SYSROOT_COMPILE
  expat: Update script to get Expat 2.2.3
  expat: Update CMake build for 2.2.3
  Tests: Simplify RunCMake.find_package PackageRoot case regexes
  find_*: Disable the PACKAGE_ROOT search path group for CMake 3.9
  CMake 3.9.1

Chuck Atkins (3):
  find_package: Add missing PACKAGE_ROOT_PATH search path implementation.
  find_package: Fix PACKAGE_ROOT test to check find_pacakge(CONFIG) mode.
  find_package: Split PACKAGE_ROOT tests to work with smaller regex

Craig Scott (1):
  FindJava: Allow early access version trailing string to be mixed case

Cristian Adam (1):
  FindBoost: pop policy stack before returning

Expat Upstream (1):
  expat 2017-08-02 (97c6bd01)

Laurent Rineau (1):
  server: Fix crash on missing cache entries

Rechi Rechi (1):
  FindJava: fix hint for windows jre 1.6

Ruslan Baratov (1):
  Help: Fix module and function names in CMP0069 examples

Sebastian Holtermann (1):
  Autogen: Always create AUTOMOC/AUTOUIC include directory
-- 

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 to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] iOS: direction to official support and questions

2017-08-10 Thread Brad King
On 08/08/2017 08:08 AM, Raffi Enficiaud wrote:
> I have looked a bit to the Android toolchains, and I have to say I found 
> those quite complicated as a first reading :)

This note may help:

 https://gitlab.kitware.com/cmake/cmake/issues/16708#note_300971

I don't think iOS will need all the toolchain and stl selection logic.

Ideally CMake would gain iOS platform modules such that one could
set CMAKE_SYSTEM_NAME to `iOS`.

> set(CMAKE_FIND_ROOT_PATH
>  ${CMAKE_IOS_DEVELOPER_ROOT}
>  ${CMAKE_IOS_SDK_ROOT}
>  ${CMAKE_PREFIX_PATH}
>  /path/to/boost_1_64_0_build/install
>  CACHE string  "iOS find search path root")
> ```
> 
> where this path is hard coded, and points to the fat static libraries 
> prefix path of boost. If I remove this path, FindBoost does not find the 
> boost libraries anymore (of course I am passing BOOST_ROOT). In 
> addition, I have this:
> 
> set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY)
> set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
> set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

These last three lines tell the find commands to only look at
paths re-rooted under CMAKE_FIND_ROOT_PATH and CMAKE_SYSROOT.
If boost is not under one of those then it won't be found.

> set(CMAKE_MACOSX_BUNDLE YES)

Is it possible to build any binary of any form on iOS without this?
If not then the iOS platform modules should set something to tell
the generators that this should always be enabled.

> set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGNING_REQUIRED "NO")

Similarly for this, but perhaps only during `try_compile`.

I'm not familiar enough with iOS development to answer the rest of
your questions.

-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 to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers