[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: swig: srcdir vs. blddir

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-12-16 00:57:26 CET

Eric Gillespie <epg@pretzelnet.org> writes:

> Max Bowsher <maxb1@ukf.net> writes:
>> The interesting wrinkle here is that, SWIG files which can be shipped in
>> a tarball, or generated during the build, can be in the srcdir OR the
>> blddir, not always one or the other.
> That's not very wrinkly, but actually quite common. Files that
> ship in the distfile have to work from srcdir, so why have them
> also work from blddir? Just build them into srcdir instead of
> blddir.
> Before you contest in revulsion that anything you "build" must go
> in the "build dir", realize that's not true. configure,
> documentation, headers, *.in files, and various other bits are
> shipped in srcdir, yet are "built". I think we only have
> configure falling into that category in Subversion today, but
> these swig files should be treated the same way.
> The distinction here is not "built files go in blddir", but
> "files added to an unpacked distfile go in blddir". Users are
> not expected to build configure, documentation, or swig files.
> I'll post a patch in a couple days to demonstrate, and hopefully
> no one will object to my committing it :).

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.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 16 00:58:15 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.