On Mon, 15 Oct 2018 at 20:00, James E. King III via Boost
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.
I've done similar for GIL: https://github.com/boostorg/gil/pull/147
It would be nice to have this as a standard Boost.Build rule that one could easily add to test Jamfiles.
Yes, it would be nice to have a rule that takes list of header files, and calculates targets one per header. I stole the target name calculation idea from Log or Test https://github.com/boostorg/log/blob/develop/test/Jamfile.v2 https://github.com/boostorg/test/blob/develop/test/Jamfile.v2 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net