On Fri, Jul 21, 2017 at 7:25 AM, Roger Leigh via Boost
Could I also point to this block in https://gitlab.kitware.com/cmake/cmake/blob/master/Modules/FindBoost.cmake#L... ... *We* pay the cost of this significant defect in the Boost project in the form of a high maintenance burden and breakage with every new Boost release.
I'm new but I am in agreement that whatever is needed to make this work should be part of Boost not CMake, since Boost has the expertise to produce accurate information. Placing the burden on CMake is clearly not scalable. I propose that the Steering Committee take a break from causing unnecessary drama and instead focus on this one particular use-case. I realize it is not the "Full Monte" but its something (10 year old ticket anyone?) and I think would heal the recently caused divisions. Thanks