15 Oct
2018
15 Oct
'18
7:10 a.m.
Why do you think a potential Boost.CMake proposal cannot offer an equivalent of check-target-builds that internally uses the checks based on Boost.Config or Boost.Predef?
I do not think what you propose. I am just pointing out that this feature, used extensively from config and/or predef for a number of Boost libraries, needs to have an equally easy CMake equivalent so that converting the library's build or test jamfile to CMake is fairly trivial.
Sorry, but WHY exactly do you need to have the checks from Boost.Config/Predef in CMake? Do they exist in B2? In which form? Isn't Boost.Config/Predef a set of headers defining macros for consumption in source code?