|
Boost : |
Subject: Re: [boost] Boost header isolation testing
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2018-10-15 20:18:26
On Mon, 15 Oct 2018 at 21:43, Roger Leigh via Boost
<boost_at_[hidden]> wrote:
> On 15/10/18 20:11, Mateusz Loskot via Boost wrote:
> > On Mon, 15 Oct 2018 at 20:00, James E. King III via Boost <boost_at_[hidden]> 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.
> >
> > 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.
>
> Note for the CMake side this is pretty simple to automate here.
Thanks, but Boost.Build does the job for GIL very well,
and in simple manner as well.
Best regards,
-- Mateusz Loskot, http://mateusz.loskot.net p.s. Let's leave CMake discussions for CMake threads, please
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk