From: williamkempf_at_[hidden]
Date: 2001-06-06 09:18:21
--- 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
things,
> > he's not likely to run "jam clean" on them any way.
> >
> > Or maybe there should be another target... realclean?
>
> The only tough part is that once created, the user can stick new
files into
> these directories. Should they be deleted as well? Should the
directories be
> removed only if empty?
> Anyway, interesting questions for the person who wants to make
clean really
> spotless...
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".
> > > > Though not as important, it would be nice if
> > > > they were cleaned up, making it easier to create distribution
> > > > archives of the source.
>
> 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.
Bill Kempf