On 05/22/2018 10:06 PM, Paul Fultz II wrote: > Or pkg-config could be extended to fix the issues.
The `.pc` file format is too flat to lend itself well to representing all the information we need. A goal of `.cps` files is to teach pkg-config to parse them and respond to its standard queries with the same output format as now. > In the Boost Cmake Modules, we support generating both pkg-config and > cmake config files automatically from the cmake targets: That's fantastic but until there is no such thing as a Boost installation that doesn't support both tools the problems will persist. They mangle their library names in such a way that it's impossible to use boost without a build system that memorizes dozens of mangling conventions that vary with the version of boost, version of the compiler, architecture, etc. -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
