From: Toon Knapen (toon_at_[hidden])
Date: 2001-06-10 05:32:54
williamkempf_at_[hidden] wrote:
>
> --- In boost_at_y..., "David Abrahams" <abrahams_at_m...> wrote:
> >
> > ----- Original Message -----
> > From: <williamkempf_at_h...>
> > To: <boost_at_y...>
> > Sent: Wednesday, June 06, 2001 9:37 AM
> > Subject: [boost] Re: Boost Build System
> >
> >
> > > --- In boost_at_y..., "David Abrahams" <abrahams_at_m...> wrote:
> > > > ----- Original Message -----
> > > > From: <williamkempf_at_h...>
> > > > > In general, the directory structure created for the object
> > > > > output isn't removed.
> > > >
> > > > They are created if not already present. How do you know whether
> > > it's OK to
> > > > remove them?
> > >
> > > A command of "jam clean", to me, should assume that they should be
> > > removed whether or not they existed previously. The only purpose
> of
> > > the Clean target is to create a pristine directory/file structure
> for
> > > distribution. If an admin uses these directories for other
> In all the makefiles I've ever used the directories were removed with
> a "make clean". The admin should know to either not add files to
> these directories or to not call "jam clean".
>
> >
> > BTW, you can use -sALL_LOCATE_TARGET=path to build into some other
> directory
> > tree. That will keep your source directories clean.
>
> Still not as convenient as the "traditional" method, though.
>
Traditionally `make clean` only destroys intermediate files whereas
`make distclean` destroys all derived objects. I'll have to look into it
of course but using make it's easy to track these intermediate files and
clean them up.
toon