On 27/12/2016 14:34, Gregor Jasny via cmake-developers wrote:
Hello,
On 27/12/2016 13:20, Roger Leigh wrote:
I opened the following merge request to add support for the
newly-released Boost 1.63:
https://gitlab.kitware.com/cmake/cmake/merge_requests/361
I wonder what's the reason for stating explicitly all the released
versions? It they are necessary at all, couldn't they be added in
speculative batches of 10 or so?
It would certainly be possible to add additional versions ahead
of time. What would be more difficult are the component dependencies,
which are needed for the imported targets.
That said, the dependency introspection script can compute these on the
fly, at the expense of taking several minutes to grind through all the
sources and headers. We could potentially fall back to computing them
if the embedded dependency information is missing, though it does make
assumptions about the autolink macros in the headers--if they ever
changed then it would need updating.
Fundamentally, the current approach is an overly complicated hack to
work around the fact that Boost has never exported this information in a
form consumable by any build system, leading to projects hardcoding all
this information (or doing it in a single place as here).
Regards,
Roger
--
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
