[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SWIG Again

From: John Lenz <lenz_at_cs.wisc.edu>
Date: 2004-12-20 00:26:57 CET

On 12/19/04 17:02:19, Philip Martin wrote:
> John Lenz <lenz@cs.wisc.edu> writes:
> > In any case, it now supports two types of building
> > 1) SWIG is installed somewhere in the path, or --with-swig is passed
> I configured using --with-swig=/usr/local/swig-1.3.24
> When I run make I get
> $ make
> if test "0" -eq "1"; then cd SWIG && make; fi
> but nothing gets built.

The problem is that swig-build-preinst actually becomes the default rule,
so you need to move it below all: something like the following patch.

Note as well that using --with-swig just means that you are passing a
string to an already built SWIG. That is, configure searches for an
installed SWIG in PATH, but if for some reason it is not installed in path,
you can pass --with-swig to tell it where (say you installed it in /opt or
something). This option is from before, and has no impact on the new way
to build SWIG.

The only way (I currently have) subversion building swig as part of its own
build process is if a SWIG directory is located in the top level subversion
source. I can change this, but it would be to add another argument like --
with-swig-source or something.

--- subversion/Makefile.in~newpatch
+++ subversion/Makefile.in
@@ -128,9 +128,6 @@

- if test "@SWIG_BUILD_PREINST@" -eq "1"; then cd SWIG && make; fi
 JAVAHL_INCLUDES= @JNI_INCLUDES@ -I$(abs_builddir)/subversion/bindings/

@@ -262,6 +259,10 @@
 extraclean: external-extraclean local-extraclean
 install: external-install local-install revision-install

+ if test "@SWIG_BUILD_PREINST@" -eq "1"; then cd SWIG && make; fi

 local-all: @BUILD_RULES@

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 20 00:29:42 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.