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

2019-10-02 Thread Robert Maynard via cmake-developers
We are pleased to announce that CMake 3.15.4 is now available for download.

This release fixes a regression in EXCLUDE_FROM_ALL.

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

Thanks for your support!

-
Changes in 3.15.4 since 3.15.3:

Brad King (10):
  VS: Tell VS 16.4 not to verify SYMBOLIC custom command outputs
  Tests: Teach RunCMake to support a custom working directory
  Tests: Revise RunCMake.add_subdirectory ExcludeFromAll to avoid globbing
  Tests: Clarify target names in RunCMake.add_subdirectory ExcludeFromAll
  Makefiles: Revert "Make build root targets ... recursive"
  Restore "all" target in subdirectories marked EXCLUDE_FROM_ALL
  Help: Add release note for EXCLUDE_FROM_ALL fix in 3.14.7
  Help: Add release note for EXCLUDE_FROM_ALL fix in 3.15.4
  Help: Mention 3.14.7 EXCLUDE_FROM_ALL fix in 3.15.4 release note
  CMake 3.15.4

LE GARREC Vincent (1):
  Help: Document VS 2019 toolset in MSVC_TOOLSET_VERSION
-- 

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:
https://cmake.org/mailman/listinfo/cmake-developers


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

2019-10-02 Thread Robert Maynard via cmake-developers
We are pleased to announce that CMake 3.14.7 is now available for download.

This release fixes a regression in EXCLUDE_FROM_ALL.

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

Thanks for your support!

-
Changes in 3.14.7 since 3.14.6:

Brad King (6):
  Tests: Teach RunCMake to support a custom working directory
  Tests: Revise RunCMake.add_subdirectory ExcludeFromAll to avoid globbing
  Tests: Clarify target names in RunCMake.add_subdirectory ExcludeFromAll
  Restore "all" target in subdirectories marked EXCLUDE_FROM_ALL
  Help: Add release note for EXCLUDE_FROM_ALL fix in 3.14.7
  CMake 3.14.7
-- 

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:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] Revitalize --find-package mode?

2019-10-02 Thread Brad King via cmake-developers
On 10/2/19 9:24 AM, Nagy-Egri Máté Ferenc via cmake-developers wrote:
> to obtain dependency information is no longer maintained in CMake,
> or at least discouraged for new projects.

For reference, the `cmake --find-package` mode documentation you
mentioned is here:

* 
https://cmake.org/cmake/help/v3.15/manual/cmake.1.html#run-the-find-package-tool
  "This mode is not well-supported due to some technical limitations.
   It is kept for compatibility but should not be used in new projects."

There is an issue collecting some of the problems with it:

* https://gitlab.kitware.com/cmake/cmake/issues/14676

There is another issue discussing a possible alternative:

* https://gitlab.kitware.com/cmake/cmake/issues/17236

A key difference between the two approaches is that the latter actually
enables languages and inspects the toolchain to support things like
COMPILE_FEATURES and such.  However, the way all that information is
encoded in the imported targets created by `install(EXPORT)` is meant
to be consumed and transformed by CMake's generators.  It may not be
easy to extract it for external use.

I've just posted some additional links in the latter issue above:

* https://gitlab.kitware.com/cmake/cmake/issues/17236#note_634094

-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:
https://cmake.org/mailman/listinfo/cmake-developers


[cmake-developers] Revitalize --find-package mode?

2019-10-02 Thread Nagy-Egri Máté Ferenc via cmake-developers
Hi!

I’m currently struggling with trying to build GNOME projects using meson, but 
depending on CMake-built libraries, either in the wild or inside a package 
manager. I have managed to uncover that the way Meson is trying to invoke CMake

https://github.com/microsoft/vcpkg/issues/6683#issuecomment-533034646

to obtain dependency information is no longer maintained in CMake, or at least 
discouraged for new projects. My queries on the Meson forums did not resonate 
well (in fact they didn’t resonate at all):

https://groups.google.com/forum/#!topic/mesonbuild/OEB0UIlLl0A

Are there any opinions in how to make ends meet? I’m trying to build GIMP on 
Ubuntu LTS releases, which often have outdated packages that cannot be used to 
build GNOME master branches as well as build them natively on Windows using 
Vcpkg ports. The current method Meson tries to use CMake is totally 
Vcpkg-unfriendly. As far as I saw --find-package mode and toolchain failes are 
not friends, even configuring a one-line main.cpp fails due to basic variables 
not being set in --find-package mode.

What specific routes do you see viable?

Best regards,
Máté
-- 

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:
https://cmake.org/mailman/listinfo/cmake-developers