b52d064544
Each template now needs to use $distfiles that accepts the full URL to download the distfile and old $extract_sufx is now merged on it, but this must be separated by the '@' character. Example: distfiles="http://www.foo.org/blah-6.2@.tar.gz http://www.foo.org/blob-1.0@.tar.bz2" If distfiles contains multiple files defined, $wrksrc is now mandatory. --HG-- extra : convert_revision : 1c3fa35f148af8323ce3cbcf5732104960de6bc4
34 lines
1.6 KiB
Cheetah
34 lines
1.6 KiB
Cheetah
# Template build file for 'libIDL'.
|
|
pkgname=libIDL
|
|
version=0.8.11
|
|
distfiles="
|
|
http://ftp.gnome.org/pub/gnome/sources/libIDL/0.8/$pkgname-$version@.tar.bz2"
|
|
build_style=gnu_configure
|
|
configure_env="HAVE_YACC=yes"
|
|
pkgconfig_override="libIDL-2.0.pc"
|
|
short_desc="CORBA Interface Definition Language parser"
|
|
maintainer="Juan RP <xtraeme@gmail.com>"
|
|
checksum=1ffe518c0b63996fb01013d0a5af7b043156ab6a
|
|
long_desc="
|
|
libIDL is a library licensed under the GNU LGPL for creating trees of
|
|
CORBA Interface Definition Language (IDL) files, which is a
|
|
specification for defining portable interfaces. libIDL was initially
|
|
written for ORBit (the ORB from the GNOME project, and the primary
|
|
means of libIDL distribution). However, the functionality was
|
|
designed to be as reusable and portable as possible.
|
|
|
|
It is written in C, and the aim is to retain the ability to compile it
|
|
on a system with a standard C compiler. Preprocessed parser files are
|
|
included so you are not forced to rebuild the parser, however an
|
|
effort is made to keep the parser and lexer compatible with standard
|
|
Unix yacc. Currently, flex is required to generate the lexical
|
|
scanner.
|
|
|
|
With libIDL, you can parse an IDL file which will be automatically run
|
|
through the C preprocessor (on systems with one available), and have
|
|
detailed error and warning messages displayed. On a compilation
|
|
without errors, the tree is returned to the custom application.
|
|
libIDL performs compilation phases from lexical analysis to nearly
|
|
full semantic analysis with some optimizations, and will attempt to
|
|
generate meaningful errors and warnings for invalid or deprecated IDL."
|