swig: srcdir vs. blddir (was Re: 1.3.0-rc3 tarballs up for testing/signing)

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 :).

--
Eric Gillespie <*> epg@pretzelnet.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 23 03:11:26 2005