[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: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-12-16 17:35:28 CET

John Lenz <lenz@cs.wisc.edu> writes:

> Using this patch, you SHOULD be able to download 1.3.24, extract it in the
> subversion directory, and rename SWIG-1.3.24 to SWIG.

I prefer to use an installed SWIG, I assume that will still be

> A few problems...
> 1) It doesn't seem to want to check the version correctly.

That sounds like a potential show-stopper, what goes wrong?

> 2) SWIG=$srcdir/SWIG/preinst-swig is turning into ./SWIG/preinst-swig,
> when in fact it needs to be $(top_srcdir)/SWIG/preinst-swig inside the
> makefile.
> 3) The makefile must recurse into the SWIG directory and run make.
> I was thinking of exporting a line like
> @enable_swig_build@$(SWIG):
> @enable_swig_build@ cd SWIG && make
> With @enable_swig_build@ being replaced by "#" or ""

I'm using an installed SWIG so I guess I don't care.

> + # We want the version as an integer so we can test against
> + # which version we're using. SWIG doesn't provide this
> + # to us so we have to come up with it on our own.
> + # The major is passed straight through,
> + # the minor is zero padded to two places,
> + # and the patch level is zero padded to three places.
> + # e.g. 1.3.21 becomes 103021
> + SWIG_BUILD_VERSION="sed -e 's/[[^0-9\.]].*$//' \
> + -e 's/\.\([[0-9]]\)$/.0\1/' \
> + -e 's/\.\([[0-9]][[0-9]]\)$/.0\1/' \
> + -e 's/\.\([[0-9]]\)\./0\1/; s/\.//g;'"

I realise this is derived from previous code, but given SWIG's past
performance on API/ABI compatibility it may be simpler just to match a
list of known working versions, at present that just "1.3.24".

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 16 17:36:53 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.