On 8/20/05, Philip Martin <philip@codematters.co.uk> wrote:
> Running gen-make.py creates a load of generated files. Is there some
> reason these aren't created by a make? Since they get created by
> gen-make.py rather than make they exist in the source directory rather
> than the build directory and they show up in 'svn status', that's bad.
It would be better if we generated the files using "make", and stored
them in the build dir. I am working on this feature. (This feature
will only apply to non-release builds, because SWIG files are
generated during the source tarball release process now)
> Taking a guess, is that's because I now need to pass the swig location
> to gen-make.py rather than to configure?
Yes. If SWIG is not in your path, then you have two choices:
1. Add the directory for the swig binary to your path (so autogen.sh
can find it)
2. Specify the path directly using the following command:
python gen-make.py --with-swig=/usr/local/swig-1.3.24
In order to make the build process easier, we should also allow users
to specify their SWIG path in "configure" using the --with-swig
option. I am working on this feature. (This feature will only apply to
non-release builds, because SWIG files are generated during the source
tarball release process now)
> That seems like a step
> backwards, I can no longer have multiple build directories using
> different swig configurations.
You can still do this (see above).
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 20 21:09:12 2005