2009-11-17 03:38:03 +01:00
|
|
|
# Template file for 'libffi'
|
|
|
|
|
pkgname=libffi
|
|
|
|
|
version=3.0.8
|
2010-04-22 11:58:17 +02:00
|
|
|
revision=1
|
2009-11-17 03:38:03 +01:00
|
|
|
distfiles="ftp://sourceware.org/pub/$pkgname/$pkgname-$version.tar.gz"
|
|
|
|
|
build_style=gnu_configure
|
|
|
|
|
short_desc="Library supporting Foreign Function Interfaces"
|
|
|
|
|
maintainer="Juan RP <xtraeme@gmail.com>"
|
|
|
|
|
checksum=2c7c5b88a68fb362262889ba25ef25dc27864b7bbf03547a8a36b8d567569406
|
|
|
|
|
long_desc="
|
|
|
|
|
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."
|
|
|
|
|
|
2009-11-22 08:31:44 +01:00
|
|
|
subpackages="$pkgname-devel"
|
2009-11-17 03:38:03 +01:00
|
|
|
Add_dependency full glibc
|
|
|
|
|
Add_dependency build texinfo
|
