On Mon, 26 Sep 2011 13:43:41 +0100
Caolán McNamara <caolanm@redhat.com> wrote:
I suppose we'd always be stuck with on incremental builds with e.g.
header removals where the header remains in the solver, and/or a .so
to .a changes, where the .so remain behind.
Well, those cases might be solvable actually: gbuild could tell you
which targets in solver it knows about -- whatever more there is is old
garbage. So yeah, it should be possible to make an "delete everything
unknown to the build system" target (called "for incremental builds. But
that would kill your temporary logfiles, testfiles etc. in
$WORKDIR/$OUTDIR too. And as long as gbuild is not alone in owning
those dirs (as the old buildsystem is still around) this would require
whitelisting the old buildsystem stuff -- so it not worth it (yet).
Best,
Bjoern
--
https://launchpad.net/~bjoern-michaelsen
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.