Re: svn commit: rev 4821 - trunk

On Mon, Feb 10, 2003 at 01:25:34PM -0800, Daniel Rall wrote:
> Philip Martin <philip@codematters.co.uk> writes:
>...
> > Deleting from SWIG_SRC_DIR doesn't look right. Why do the Java
> > bindings build there? Why don't they build in SWIG_BUILD_DIR?
>
> That's where they've always built to, but not for any particular
> reason. Is this more along the lines of how it should be (untested)?:
>...
> swig-java-ext-clean:
> - rm -rf $(SWIG_SRC_DIR)/java/build/
> - rm -rf $(SWIG_SRC_DIR)/java/org/
> + rm -rf $(SWIG_BUILD_DIR)/java/build/
> + rm -rf $(SWIG_BUILD_DIR)/java/org/

Conceptually, yes.

However, please delete the swig-java-ext(-clean) targets. You should be able
to build and install the Java stuff using the (install-)swig-java targets.

[ in additional to (install-)swig-java-lib for libsvn_swig_java ]

The Python stuff still has the -ext stuff which works with the distutils,
but it is going away once I get the time to finish the swig-py rules.
(specifically, copying over and compiling the .py files)

To get (install-)swig-java to work, you'll need to fix the
COMPILE_JAVA_WRAPPER and LINK_JAVA_WRAPPER symbols in Makefile.in.

The 'swig-clean' target should go away, in favor of integrating directly
with the normal clean rules (some gen-make work).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org