You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Eric Gillespie <ep...@pretzelnet.org> on 2005/11/23 02:10:40 UTC
swig: srcdir vs. blddir (was Re: 1.3.0-rc3 tarballs up for testing/signing)
Max Bowsher <ma...@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
Re: swig: srcdir vs. blddir
Posted by David James <ja...@cs.toronto.edu>.
On 11/23/05, Julian Foad <ju...@btopenworld.com> wrote:
> David James wrote:
> >
> > [[[
> > Always generate SWIG/C files in the source directory.
>
> In the log message, can you try to include a few words to indicate why the
> change is being made, so that somebody who might contest it later on can judge
> whether it was done for a good reason and/or is still appropriate at that
> future time. If it can't be summarised well in a sentence or two, include a
> link to the email thread or issue. This applies to any commit the reason for
> which is not totally self-evident. Thanks.
Good idea! I've added a summary to my log message, and also a link to
the thread. Here's my new log message:
[[[
Always generate SWIG/C files and SWIG headers in the source directory.
(Now that the SWIG generated files are bundled in source tarballs, it makes
sense to treat them as "source directory" files. This change greatly
simplifies our SWIG build system, because we don't have to worry about
copying generated SWIG files from the source directory to the build directory
any more.)
* Makefile.in
(SWIG_PL_SRC_DIR): Add variable.
(EXTRACLEAN_SWIG_HEADERS, EXTRACLEAN_SWIG_PL, EXTRACLEAN_SWIG_PY,
EXTRACLEAN_SWIG_RB): Clean SWIG files from the source directory.
(copy-swig-py): Copy Python files directly from the source directory to
the libsvn directory.
* build/generator/gen_base.py
(TargetSWIG.add_dependencies): Read and write generated SWIG/C files in
the source directory.
* build/generator/gen_make.py
(write): Generate SWIG headers and SWIG/C files in source directory. Don't
copy SWIG/C files from the source directory to the build directory.
Suggested by: epg
Thread: http://svn.haxx.se/dev/archive-2005-11/1207.shtml
]]]
I've committed this patch with several improvements in r17497.
Hope this helps!
David
--
David James -- http://www.cs.toronto.edu/~james
Re: swig: srcdir vs. blddir
Posted by Julian Foad <ju...@btopenworld.com>.
David James wrote:
>
> [[[
> Always generate SWIG/C files in the source directory.
In the log message, can you try to include a few words to indicate why the
change is being made, so that somebody who might contest it later on can judge
whether it was done for a good reason and/or is still appropriate at that
future time. If it can't be summarised well in a sentence or two, include a
link to the email thread or issue. This applies to any commit the reason for
which is not totally self-evident. Thanks.
> * build/generator/gen_make.py
> (write): Generate SWIG/C files in source directory. Don't copy SWIG/C
> files from the source directory to the build directory.
[...]
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir (was Re: 1.3.0-rc3 tarballs up for testing/signing)
Posted by Eric Gillespie <ep...@pretzelnet.org>.
David James <ja...@cs.toronto.edu> writes:
> I couldn't wait, so I attached a patch which demonstrates your idea.
> Let me know if you have any suggestions or feedback.
I haven't actually tested it, but this looks good.
> We still have some logic in Makefile.in for copying Python files from
> the source directory to the build directory under the copy-swig-py. I
> haven't removed this code yet, but it might be a good idea for us to
> do so
Yeah.
--
Eric Gillespie <*> epg@pretzelnet.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir (was Re: 1.3.0-rc3 tarballs up for testing/signing)
Posted by David James <ja...@cs.toronto.edu>.
On 11/22/05, Eric Gillespie <ep...@pretzelnet.org> wrote:
> Max Bowsher <ma...@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.
>
> [snip convincing argument for generating SWIG code in the src dir]
Great idea, Eric! I'm convinced. It's not only better to generate our
SWIG code in the source directory, but also much easier.
I couldn't wait, so I attached a patch which demonstrates your idea.
Let me know if you have any suggestions or feedback.
We still have some logic in Makefile.in for copying Python files from
the source directory to the build directory under the copy-swig-py. I
haven't removed this code yet, but it might be a good idea for us to
do so, as soon as we update our install and test suite targets to use
the Python files from the source directory.
[[[
Always generate SWIG/C files in the source directory.
* build/generator/gen_make.py
(write): Generate SWIG/C files in source directory. Don't copy SWIG/C
files from the source directory to the build directory.
* build/generator/gen_base.py
(TargetSWIG.add_dependencies): Read generate SWIG/C dependencies from
the source directory.
Suggested by: epg
]]]
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
Re: swig: srcdir vs. blddir
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-12-16 20:40+0000, Philip Martin wrote:
> > Please see: http://svn.haxx.se/dev/archive-2005-11/1324.shtml
>
> So it fails shortly after r17497 "Always generate SWIG/C files and
> SWIG headers in the source directory", are you using a VPATH build?
>
Yes, the test system is using vpath setup.
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir
Posted by Philip Martin <ph...@codematters.co.uk>.
Jani Averbach <ja...@jaa.iki.fi> writes:
> On 2005-12-16 19:57+0000, Philip Martin wrote:
>
>> Even more annoying is that the perl bindings don't build at all. I've
>> build the perl bindings in the past, so this is a recent breakage.
>
> Last time when swig-pl has worked on my test machine is:
>
> Date: Wed, 23 Nov 2005 05:46:39 -0700
> Subject: swig-pl trunk r17488: PASS (x86_64-unknown-linux-gnushared)
>
> Please see: http://svn.haxx.se/dev/archive-2005-11/1324.shtml
So it fails shortly after r17497 "Always generate SWIG/C files and
SWIG headers in the source directory", are you using a VPATH build?
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir
Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-12-16 19:57+0000, Philip Martin wrote:
> Even more annoying is that the perl bindings don't build at all. I've
> build the perl bindings in the past, so this is a recent breakage.
Last time when swig-pl has worked on my test machine is:
Date: Wed, 23 Nov 2005 05:46:39 -0700
Subject: swig-pl trunk r17488: PASS (x86_64-unknown-linux-gnushared)
Please see: http://svn.haxx.se/dev/archive-2005-11/1324.shtml
> rm -f blib/arch/auto/SVN/_Core/_Core.so
> LD_RUN_PATH="/home/pm/sw/subversion/obj/subversion/libsvn_client/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_delta/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_fs/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_ra/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_repos/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_wc/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_diff/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_subr/.libs:/home/pm/sw/subversion/obj/subversion/bindings/swig/perl/libsvn_swig_perl/.libs" cc -shared -L/usr/local/lib core.o -o blib/arch/auto/SVN/_Core/_Core.so -L/home/pm/sw/subversion/obj/subversion/bindings/swig/perl/libsvn_swig_perl/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_client/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_delta/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_fs/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_repos/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_wc/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_diff/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_subr/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra_local/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra_svn/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra_dav/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_fs_base/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_fs_fs/.libs -lsvn_client-1 -lsvn_delta-1 -lsvn_fs-1 -lsvn_ra-1 -lsvn_repos-1 -lsvn_wc-1 -lsvn_diff-1 -lsvn_subr-1 -lsvn_swig_perl-1
> cc: core.o: No such file or directory
The problem is same.
BR, Jani
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir
Posted by Philip Martin <ph...@codematters.co.uk>.
Philip Martin <ph...@codematters.co.uk> writes:
> A more annoying problem is that the 'make -j4 swig-py' parallel build
> is broken, it sometimes fails with
>
> /usr/local/swig-1.3.24/bin/swig -I/home/pm/sw/subversion/obj/../svn/subversion/include -I/home/pm/sw/subversion/obj/../svn/subversion/bindings/swig -I/home/pm/sw/subversion/obj/../svn/subversion/bindings/swig/include -I/home/pm/sw/subversion/obj/../svn/subversion/bindings/swig/proxy -I/home/pm/sw/subversion/obj/subversion/bindings/swig/proxy -I/usr/local/apache2/include -I/usr/local/apache2/include -python -classic -w451 -w305 -o ../svn/subversion/bindings/swig/python/svn_client.c ../svn/subversion/bindings/swig/svn_client.i
> Traceback (most recent call last):
> File "build/generator/swig/external_runtime.py", line 107, in ?
> gen.write()
> File "build/generator/swig/external_runtime.py", line 99, in write
> self.write_long_long_fix()
> File "build/generator/swig/external_runtime.py", line 82, in write_long_long_fix
> self.checkout("python","python.swg")
> File "/home/pm/sw/subversion/svn/build/generator/swig/__init__.py", line 56, in checkout
> shutil.copy("%s/%s/%s" % (self.swig_libdir, dir, file), out)
> File "/usr/lib/python2.3/shutil.py", line 73, in copy
> copymode(src, dst)
> File "/usr/lib/python2.3/shutil.py", line 52, in copymode
> os.chmod(dst, mode)
> OSError: [Errno 2] No such file or directory: 'subversion/bindings/swig/proxy/python.swg'
Even more annoying is that the perl bindings don't build at all. I've
build the perl bindings in the past, so this is a recent breakage.
'make swig-pl' creates the generated C files in the source dir, but no
attempt is made to compile them, and then a link command fails because
the object is not found:
Writing Makefile.wc for SVN::_Wc
cd /home/pm/sw/subversion/obj/subversion/bindings/swig/perl/native; make
make[1]: Entering directory `/home/pm/sw/subversion/obj/subversion/bindings/swig/perl/native'
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Core.pm blib/lib/SVN/Core.pm
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Repos.pm blib/lib/SVN/Repos.pm
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Base.pm blib/lib/SVN/Base.pm
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Client.pm blib/lib/SVN/Client.pm
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Fs.pm blib/lib/SVN/Fs.pm
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Ra.pm blib/lib/SVN/Ra.pm
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Wc.pm blib/lib/SVN/Wc.pm
cp ../../../../../../svn/subversion/bindings/swig/perl/native/Delta.pm blib/lib/SVN/Delta.pm
Running Mkbootstrap for SVN::_Core ()
chmod 644 _Core.bs
rm -f blib/arch/auto/SVN/_Core/_Core.so
LD_RUN_PATH="/home/pm/sw/subversion/obj/subversion/libsvn_client/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_delta/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_fs/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_ra/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_repos/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_wc/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_diff/.libs:/home/pm/sw/subversion/obj/subversion/libsvn_subr/.libs:/home/pm/sw/subversion/obj/subversion/bindings/swig/perl/libsvn_swig_perl/.libs" cc -shared -L/usr/local/lib core.o -o blib/arch/auto/SVN/_Core/_Core.so -L/home/pm/sw/subversion/obj/subversion/bindings/swig/perl/libsvn_swig_perl/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_client/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_delta/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_fs/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_repos/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_wc/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_diff/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_subr/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra_local/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra_svn/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_ra_dav/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_fs_base/.libs -L/home/pm/sw/subversion/obj/subversion/libsvn_fs_fs/.libs -lsvn_client-1 -lsvn_delta-1 -lsvn_fs-1 -lsvn_ra-1 -lsvn_repos-1 -lsvn_wc-1 -lsvn_diff-1 -lsvn_subr-1 -lsvn_swig_perl-1
cc: core.o: No such file or directory
make[1]: *** [blib/arch/auto/SVN/_Core/_Core.so] Error 1
make[1]: Leaving directory `/home/pm/sw/subversion/obj/subversion/bindings/swig/perl/native'
make: *** [swig-pl] Error 2
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir
Posted by Philip Martin <ph...@codematters.co.uk>.
Greg Hudson <gh...@MIT.EDU> writes:
> 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.
My build from a working copy deletes generated files. Looking at the
Makefile it appears to depend on RELEASE_MODE, I'm not sure what sets
that.
> "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.
>
> 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.
I don't build the bindings very often so I'm not really bothered--but
the old system was better :)
A more annoying problem is that the 'make -j4 swig-py' parallel build
is broken, it sometimes fails with
/usr/local/swig-1.3.24/bin/swig -I/home/pm/sw/subversion/obj/../svn/subversion/include -I/home/pm/sw/subversion/obj/../svn/subversion/bindings/swig -I/home/pm/sw/subversion/obj/../svn/subversion/bindings/swig/include -I/home/pm/sw/subversion/obj/../svn/subversion/bindings/swig/proxy -I/home/pm/sw/subversion/obj/subversion/bindings/swig/proxy -I/usr/local/apache2/include -I/usr/local/apache2/include -python -classic -w451 -w305 -o ../svn/subversion/bindings/swig/python/svn_client.c ../svn/subversion/bindings/swig/svn_client.i
Traceback (most recent call last):
File "build/generator/swig/external_runtime.py", line 107, in ?
gen.write()
File "build/generator/swig/external_runtime.py", line 99, in write
self.write_long_long_fix()
File "build/generator/swig/external_runtime.py", line 82, in write_long_long_fix
self.checkout("python","python.swg")
File "/home/pm/sw/subversion/svn/build/generator/swig/__init__.py", line 56, in checkout
shutil.copy("%s/%s/%s" % (self.swig_libdir, dir, file), out)
File "/usr/lib/python2.3/shutil.py", line 73, in copy
copymode(src, dst)
File "/usr/lib/python2.3/shutil.py", line 52, in copymode
os.chmod(dst, mode)
OSError: [Errno 2] No such file or directory: 'subversion/bindings/swig/proxy/python.swg'
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir
Posted by Philip Martin <ph...@codematters.co.uk>.
David James <ja...@gmail.com> writes:
> If you run ./autogen.sh --release in your source directory, then all
> of your parallel builds should be completely independent.
The only time I used parallel directories to build the bindings was
when I was testing one of the swig transitions--I configured the
builds to use different versions of swig. That doesn't work so well
now, even in release mode, since I only have one set of swig generated
files. I don't do that much testing of the bindings, and since it's
got harder I'll do even less, but so as long as the new system means
that others do *more* testing it's a net win!
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir
Posted by David James <ja...@gmail.com>.
On 12/15/05, Greg Hudson <gh...@mit.edu> 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.
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
Re: swig: srcdir vs. blddir
Posted by Greg Hudson <gh...@MIT.EDU>.
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.
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.
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: swig: srcdir vs. blddir
Posted by Philip Martin <ph...@codematters.co.uk>.
Eric Gillespie <ep...@pretzelnet.org> writes:
> Max Bowsher <ma...@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