Re: Major upgrades to SWIG/Python bindings in r15848

David James <james82@gmail.com> writes:

> I've committed some major upgrades to SWIG/Python bindings in r15848
> (Merged from the python-bindings-improvements branch).
>
> As gstein says, "It works on my machine" ;) Let me know if you run
> into any issues.

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.

I configure using --with-swig=/usr/local/swig-1.3.24 and it worked in
the past, but it no longer works:

configure: Configuring python swig binding
checking for Python includes... -I/usr/include/python2.3
checking for compiling Python extensions... gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC
checking for linking Python extensions... gcc -pthread -shared
checking for linking Python libraries...
checking for apr_int64_t Python/C API format string... L

$ make swig-py
python -c "raise 'Cannot find SWIG 1.3.24 or better. Please install SWIG, add it to your PATH,\nand rerun ./autogen.sh'"
Traceback (most recent call last):
  File "<string>", line 1, in ?
Cannot find SWIG 1.3.24 or better. Please install SWIG, add it to your PATH,
and rerun ./autogen.sh
make: *** [wrong-swig] Error 1

Taking a guess, is that's because I now need to pass the swig location
to gen-make.py rather than to configure? That seems like a step
backwards, I can no longer have multiple build directories using
different swig configurations.

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