On 12/15/05, Greg Hudson <email@example.com> wrote:
> On Thu, 2005-12-15 at 23:57 +0000, Philip Martin wrote:
> > Finally spotted this. One disadvantage of the new system is that
> > multiple parallel builds are no longer independent. Previously it was
> > possible to have two or more build dirs, maybe with different
> > configurations, and each would be independent. With the new system
> > it's no longer possible to configure the builds to use different
> > versions of swig, and running 'make clean' in one dir could break the
> > build in another if the generated files disappear during the build.
> > Now I don't do things like that very often, so it's not a big problem,
> > but I have done both of them in the past.
Phillip, have you tried configuring your source dir in release mode?
If you run ./autogen.sh --release in your source directory, then all
of your parallel builds should be completely independent.
> I don't think "make clean" should be deleting files generated in the
> source tree. That would mean a tarball build would break after a "make
> clean" for users who don't have the tools used to create those files.
> "make distclean" shouldn't remove them either, for that matter, since
> they're part of the distributed files. I guess that's what "make
> extraclean" is for.
When we're in release mode, the generated SWIG files will only be
destroyed when you "make extraclean".
On the other hand, if you're starting from checked out sources, the
generated SWIG files will be built at runtime, so it makes sense to
destroy them when you type "make clean".
> Regardless, two parallel builds in separate directories won't be
> independent if you start from the checked-out sources. But they will be
> if you start from the distributed tarball sources; that's good enough
> for me.
If you configure your source directory in release mode, your multiple
parallel builds should be completely independent. That's good enough
for me, too.
David James -- http://www.cs.toronto.edu/~james
Received on Fri Dec 16 01:53:21 2005