kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/p5-ExtUtils-LibBuilder/Makefile

22 lines
642 B
Makefile
Raw Normal View History

Comment out dependencies of the style {perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS since pkgsrc enforces the newest perl version anyway, so they should always pick perl, but sometimes (pkg_add) don't due to the design of the {,} syntax. No effective change for the above reason. Ok joerg
2015-07-12 20:56:06 +02:00
# $NetBSD: Makefile,v 1.8 2015/07/12 18:56:12 wiz Exp $
Initial import p5-ExtUtils-LibBuilder 0.04 Some Perl modules need to ship C libraries together with their Perl code. Although there are mechanisms to compile and link (or glue) C code in your Perl programs, there isn't a clear method to compile standard, self-contained C libraries. This module main goal is to help in that task.
2012-03-11 09:18:59 +01:00
Update to 0.06: 0.06 Sun Aug 31 21:02:44 WEST 2014 - Fixed metadata for metacpan (thanks to Gabor Szabo). 0.05 Sun Aug 31 13:44:44 WEST 2014 - Added metadata for metacpan.
2014-09-07 00:42:34 +02:00
DISTNAME= ExtUtils-LibBuilder-0.06
Initial import p5-ExtUtils-LibBuilder 0.04 Some Perl modules need to ship C libraries together with their Perl code. Although there are mechanisms to compile and link (or glue) C code in your Perl programs, there isn't a clear method to compile standard, self-contained C libraries. This module main goal is to help in that task.
2012-03-11 09:18:59 +01:00
PKGNAME= p5-${DISTNAME}
Recursive PKGREVISION bump for all packages mentioning 'perl', having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
2015-06-12 12:48:20 +02:00
PKGREVISION= 1
Initial import p5-ExtUtils-LibBuilder 0.04 Some Perl modules need to ship C libraries together with their Perl code. Although there are mechanisms to compile and link (or glue) C code in your Perl programs, there isn't a clear method to compile standard, self-contained C libraries. This module main goal is to help in that task.
2012-03-11 09:18:59 +01:00
CATEGORIES= devel perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=ExtUtils/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://search.cpan.org/dist/ExtUtils-LibBuilder/
COMMENT= Perl5 module for building C libraries
LICENSE= ${PERL5_LICENSE}
Comment out dependencies of the style {perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS since pkgsrc enforces the newest perl version anyway, so they should always pick perl, but sometimes (pkg_add) don't due to the design of the {,} syntax. No effective change for the above reason. Ok joerg
2015-07-12 20:56:06 +02:00
#BUILD_DEPENDS+= {perl>=5.14.1,p5-ExtUtils-CBuilder>=0.23}:../../devel/p5-ExtUtils-CBuilder
Initial import p5-ExtUtils-LibBuilder 0.04 Some Perl modules need to ship C libraries together with their Perl code. Although there are mechanisms to compile and link (or glue) C code in your Perl programs, there isn't a clear method to compile standard, self-contained C libraries. This module main goal is to help in that task.
2012-03-11 09:18:59 +01:00
USE_LANGUAGES= c
PERL5_PACKLIST= auto/ExtUtils/LibBuilder/.packlist
PERL5_MODULE_TYPE= Module::Build
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink