With the current port, it looks for the ruby binary name, which doesn't
exist by default. This specifically provides the ruby18 binary name
(since it doesn't look like swig 1.3.36 fully supports ruby 1.9). No
difference in swig -ruby output compared to the current port when using
the example code at http://www.swig.org/tutorial.html
Looking for OKs.
Thanks,
Jeremy
Index: Makefile
===================================================================
RCS file: /cvs/ports/devel/swig/Makefile,v
retrieving revision 1.52
diff -u -p -r1.52 Makefile
--- Makefile 9 Jun 2011 07:34:33 -0000 1.52
+++ Makefile 2 Sep 2012 21:19:34 -0000
@@ -6,7 +6,7 @@ SUBST_VARS= VERSION
VERSION= 1.3.36
DISTNAME= swig-${VERSION}
-REVISION= 5
+REVISION= 6
CATEGORIES= devel
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=swig/}
@@ -32,6 +32,7 @@ CONFIGURE_ARGS+= --with-tclincl=${MODTCL
--with-tcllib=${MODTCL_LIBDIR} \
--with-guilelib=${LOCALBASE}/lib \
--with-python=${MODPY_BIN} \
+ --with-ruby=${RUBY} \
--without-php4 \
--without-ocaml
MODGNU_CONFIG_GUESS_DIRS=${WRKSRC}/Tools/config
