AMDG On 10/15/2018 12:00 PM, James E. King III via Boost wrote:
In the winapi project there's a neat little Jamfile rule that will ensure each public header will compile properly (i.e. it is not missing any #include statements). I pulled this into uuid when I started maintaining it, and I find myself pulling it into another repository. It would be nice to have this as a standard Boost.Build rule that one could easily add to test Jamfiles. Is there anything like this that exists right now in Boost.Build?
Making a generalized version of this is a bit tricky as there are a lot of things that can vary and I'm not really sure how to parameterize it in a sane way. The most annoying part of the code is calculating the name of the target, and unfortunately, this is also the part that is most likely to need customization. In Christ, Steven Watanabe