On Thu, 07 Jun 2012 20:58:43 +0200 Mel Flynn <rfl...@acsalaska.net> mentioned:
> > Given issues described with swig 1.x earlier on this list, you may want > to investigate if swig 1.x should be removed/patched/whatever before > this sweep. Swig 1.x actually works fine with ruby 1.9, I'm using it quite regularly. SWIG just generate the C source, it does not provide you with include path. It is a responsibility of the application to find out what the correct path are. You can look at my m4 macro as an example of how to do it properly: https://github.com/stass/autoconf-macros/blob/master/ax_ruby_ext.m4 -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
