cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
abb1d83425
openbsd-ports/devel/ruby-rubyinline/Makefile

33 lines
723 B
Makefile
Raw Normal View History

normalize pkgpath
2011-09-16 05:24:48 -04:00
# $OpenBSD: Makefile,v 1.11 2011/09/16 09:24:58 espie Exp $
Initial import of ruby-rubyinline-3.6.7. Ruby Inline is an analog to Perl's Inline::C. Out of the box, it allows you to embed C/++ external module code in your ruby script directly. By writing simple builder classes, you can teach how to cope with new languages (fortran, perl, whatever). The code is compiled and run on the fly when needed. Using the package_inline tool Inline allows you to package up your inlined object code for distribution to systems without a compiler.
2008-04-19 14:34:08 -04:00
COMMENT= embed C/++ external module code in your Ruby script
Update to ruby-rubyinline-3.8.3.
2009-08-20 18:38:48 -04:00
DISTNAME= RubyInline-3.8.3
REVISION bumps for most ruby ports after the ruby.port.mk update. PKG_ARCH = * removed from many ports as it is added automatically for pure ruby gem ports. Switch ports that previously used GEM_SKIPDEPENDS to adding dependencies or modifying the underlying gem metadata with patches. OK landry@
2010-11-08 18:28:53 -05:00
PKGNAME= ${DISTNAME:L}
normalize pkgpath
2011-09-16 05:24:48 -04:00
REVISION= 4
Initial import of ruby-rubyinline-3.6.7. Ruby Inline is an analog to Perl's Inline::C. Out of the box, it allows you to embed C/++ external module code in your ruby script directly. By writing simple builder classes, you can teach how to cope with new languages (fortran, perl, whatever). The code is compiled and run on the fly when needed. Using the package_inline tool Inline allows you to package up your inlined object code for distribution to systems without a compiler.
2008-04-19 14:34:08 -04:00
CATEGORIES= devel
HOMEPAGE= http://www.zenspider.com/ZSS/Products/RubyInline/
# MIT
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MODULES= lang/ruby
CONFIGURE_STYLE= ruby gem
Update to 3.8.1. Okay bernd@.
2008-10-30 10:00:07 -04:00
BUILD_DEPENDS= ${RUN_DEPENDS}
REVISION bump all ruby ports due to a change in the pkgspec. Previously, we were using ruby->=1.8,<=1.9, instead of ruby->=1.8,<1.9. While this wouldn't cause an issue, since our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9, it's still wrong and should be fixed. This also fixes the following minor issues: Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS. Currently we don't have a ruby port that uses FLAVORs that would differ from MODRUBY_FLAVOR, but it's possible we will in the future. Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in REGRESS_DEPENDS. This probably is not strictly necessary, but BUILD_PKGPATH is used in more cases, so it is good for consistency. Switch to new style *_DEPENDS, with the version specification at the end. The remaining cases where this is not done is because a specific version is used. Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if the old version is installed when you run a regress test, it will install the new version first. Some conversion of spaces to tabs for consistency. OK landry@
2010-11-24 16:35:13 -05:00
RUN_DEPENDS= devel/ruby-zentest,${MODRUBY_FLAVOR} \
devel/ruby-hoe,${MODRUBY_FLAVOR}
Initial import of ruby-rubyinline-3.6.7. Ruby Inline is an analog to Perl's Inline::C. Out of the box, it allows you to embed C/++ external module code in your ruby script directly. By writing simple builder classes, you can teach how to cope with new languages (fortran, perl, whatever). The code is compiled and run on the fly when needed. Using the package_inline tool Inline allows you to package up your inlined object code for distribution to systems without a compiler.
2008-04-19 14:34:08 -04:00
REVISION bump all ruby ports due to a change in the pkgspec. Previously, we were using ruby->=1.8,<=1.9, instead of ruby->=1.8,<1.9. While this wouldn't cause an issue, since our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9, it's still wrong and should be fixed. This also fixes the following minor issues: Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS. Currently we don't have a ruby port that uses FLAVORs that would differ from MODRUBY_FLAVOR, but it's possible we will in the future. Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in REGRESS_DEPENDS. This probably is not strictly necessary, but BUILD_PKGPATH is used in more cases, so it is good for consistency. Switch to new style *_DEPENDS, with the version specification at the end. The remaining cases where this is not done is because a specific version is used. Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if the old version is installed when you run a regress test, it will install the new version first. Some conversion of spaces to tabs for consistency. OK landry@
2010-11-24 16:35:13 -05:00
REGRESS_DEPENDS= ${FULLPKGNAME}:${BUILD_PKGPATH} \
REVISION bumps for most ruby ports after the ruby.port.mk update. PKG_ARCH = * removed from many ports as it is added automatically for pure ruby gem ports. Switch ports that previously used GEM_SKIPDEPENDS to adding dependencies or modifying the underlying gem metadata with patches. OK landry@
2010-11-08 18:28:53 -05:00
${MODRUBY_RAKE_DEPENDS}
Initial import of ruby-rubyinline-3.6.7. Ruby Inline is an analog to Perl's Inline::C. Out of the box, it allows you to embed C/++ external module code in your ruby script directly. By writing simple builder classes, you can teach how to cope with new languages (fortran, perl, whatever). The code is compiled and run on the fly when needed. Using the package_inline tool Inline allows you to package up your inlined object code for distribution to systems without a compiler.
2008-04-19 14:34:08 -04:00
do-regress:
Update to 3.8.1. Okay bernd@.
2008-10-30 10:00:07 -04:00
@cd ${WRKBUILD} && ${RUBY} -Ilib/ ./test/test_inline.rb
Initial import of ruby-rubyinline-3.6.7. Ruby Inline is an analog to Perl's Inline::C. Out of the box, it allows you to embed C/++ external module code in your ruby script directly. By writing simple builder classes, you can teach how to cope with new languages (fortran, perl, whatever). The code is compiled and run on the fly when needed. Using the package_inline tool Inline allows you to package up your inlined object code for distribution to systems without a compiler.
2008-04-19 14:34:08 -04:00
.include <bsd.port.mk>
Reference in New Issue Copy Permalink