Re: Major upgrades to SWIG/Python bindings in r15848

David James <james82@gmail.com> writes:

> On 8/20/05, Philip Martin <philip@codematters.co.uk> wrote:
>> 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

I run this in the source directory.

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

Given that I run gen-make.py, with a particular version of swig, in
the source directory it's not clear how I can have multiple build
directories using different versions of swig. I don't do that sort of
thing very often, in fact I rarely build the bindings at all, but I
have done it in the past when experimenting with new versions of swig.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org