kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/libffi/Makefile

22 lines
526 B
Makefile
Raw Normal View History

Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
# $NetBSD: Makefile,v 1.6 2006/03/04 21:29:17 jlam Exp $
Initial import of libffi-2.0beta into the NetBSD Packages Collection. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. Libffi can be used in such programs to provide a bridge from the interpreter program to compiled code. Ffi stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The libffi library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above libffi that handles type conversions for values passed between the two languages.
2003-07-18 14:39:40 +02:00
Use gcc-3.3.5 tarball. Very minor changes. Bump PKGREVISION. Adapt patch-aa to include (currently untested) powerpc support.
2005-03-07 15:54:40 +01:00
DISTNAME= gcc-3.3.5
Initial import of libffi-2.0beta into the NetBSD Packages Collection. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. Libffi can be used in such programs to provide a bridge from the interpreter program to compiled code. Ffi stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The libffi library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above libffi that handles type conversions for values passed between the two languages.
2003-07-18 14:39:40 +02:00
PKGNAME= libffi-2.0beta
Use gcc-3.3.5 tarball. Very minor changes. Bump PKGREVISION. Adapt patch-aa to include (currently untested) powerpc support.
2005-03-07 15:54:40 +01:00
PKGREVISION= 2
Initial import of libffi-2.0beta into the NetBSD Packages Collection. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. Libffi can be used in such programs to provide a bridge from the interpreter program to compiled code. Ffi stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The libffi library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above libffi that handles type conversions for values passed between the two languages.
2003-07-18 14:39:40 +02:00
CATEGORIES= devel
Use gcc-3.3.5 tarball. Very minor changes. Bump PKGREVISION. Adapt patch-aa to include (currently untested) powerpc support.
2005-03-07 15:54:40 +01:00
MASTER_SITES= ${MASTER_SITE_GNU:=gcc/gcc-3.3.5/}
Initial import of libffi-2.0beta into the NetBSD Packages Collection. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. Libffi can be used in such programs to provide a bridge from the interpreter program to compiled code. Ffi stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The libffi library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above libffi that handles type conversions for values passed between the two languages.
2003-07-18 14:39:40 +02:00
EXTRACT_SUFX= .tar.bz2
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Initial import of libffi-2.0beta into the NetBSD Packages Collection. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. Libffi can be used in such programs to provide a bridge from the interpreter program to compiled code. Ffi stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The libffi library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above libffi that handles type conversions for values passed between the two languages.
2003-07-18 14:39:40 +02:00
HOMEPAGE= http://sources.redhat.com/libffi/
COMMENT= Foreign function interface
GNU_CONFIGURE= yes
CONFIGURE_ENV+= with_target_subdir=.
Override config.guess and config.sub. Add DragonFly.
2006-01-08 21:40:02 +01:00
CONFIG_GUESS_OVERRIDE= ../config.guess
CONFIG_SUB_OVERRIDE= ../config.sub
Initial import of libffi-2.0beta into the NetBSD Packages Collection. The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run-time. Some programs may not know at the time of compilation what arguments are to be passed to a function. For instance, an interpreter may be told at run-time about the number and types of arguments used to call a given function. Libffi can be used in such programs to provide a bridge from the interpreter program to compiled code. Ffi stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The libffi library really only provides the lowest, machine dependent layer of a fully featured foreign function interface. A layer must exist above libffi that handles type conversions for values passed between the two languages.
2003-07-18 14:39:40 +02:00
WRKSRC= ${WRKDIR}/${DISTNAME}/libffi
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink