[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] The carnivorous config bug
From: |
Eric S. Raymond |
Subject: |
Re: [gpsd-dev] The carnivorous config bug |
Date: |
Fri, 1 Nov 2013 09:04:12 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Greg Troxel <address@hidden>:
>
> "Eric S. Raymond" <address@hidden> writes:
>
> > Hal Murray <address@hidden>:
> >> A) scons -c goes through the configuration stuff. Is there a reason for
> >> that?
> >
> > Yes, scons is designed to work in one pass rather than two and always
> > does any configure stuff up front before building targets; clean is
> > just another target. This is good for build consistency, because what
> > you need to clean may depend on configure options.
>
> So if you
>
> scons # build
> install/change your system
> scons clean
>
> then you may have leftover objects, but not any that the new config will
> use?
>
I think that's the way it;s supposed to work. scons keeps a database of
sha1 hashes and dependencies and rebuilds by content changes.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
signature.asc
Description: Digital signature