On 18/06/2017 21:24, Glen Fernandes via Boost wrote:
On Sun, Jun 18, 2017 at 4:03 PM, Edward Diener via Boost
wrote: Please give a specific example of what this XYZConfig.cmake module entails ? For a header-only library ? For a built library ? For running tests ? For creating documentation ? Along with some sort of decent explanation of what is going on in each situation.
+1. I'm interested in the [typical] Boost header-only library case: - The CMakeLists.txt for building its tests - The .cmake file for locating the library - The consumption of the library in a user's CMakeLists
I have a guess ( based on my fairly basic usage of CMake) that at least #3 there should be simple (i.e. would it involve more than adding to include_directories or target_include_directories?).
I have a patchset for Boost 1.64 in motion implementing a bare minimum viable cmake 3. No custom macros nor functions. It's out for review off list right now, but it will include an example of header only library. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/