Re: Re-running library tests
Mateusz Loskot via Boost-build <[email protected]>
| Newsgroups | gmane.comp.lib.boost.build |
|---|---|
| Message-ID | <CABUeae_p257GK75KDyqNh-9DBDzVrkjNq1tnjE3vxjMOQAtSfg@mail.gmail.com> |
On 9 March 2018 at 21:34, Konstantin Litvinenko via Boost-build <[email protected]> wrote: > On 03/09/2018 09:45 PM, Steven Watanabe via Boost-build wrote: >>>> >>>> I find it easiest to touch the source or use -a (rebuild all). >>> >>> >>> Pity, I was hoping to avoid compilation/link phase. >>> >> >> Even if there were a way to do this, it would >> rebuild a main-target as a unit (including compile and >> link) > > > Create some dumb make (make rule or something like that, I don't remember) > target that never produce output and make test <dependency> on that target? Thanks for the top. From my POV, it's going to be quicker to add CMake configuration for the library I'm working on, so the build behaves as I expect, than fiddle with Boost.Build. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build