kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/eet/buildlink3.mk

19 lines
489 B
Makefile
Raw Normal View History

Second try at jpeg-8 recursive PKGREVISION bump.
2010-01-18 10:58:37 +01:00
# $NetBSD: buildlink3.mk,v 1.14 2010/01/18 09:58:44 wiz Exp $
Import eet from pkgsrc-wip. Packaged by Peter Bex and modified by me. EET is a tiny library designed to write an arbitrary set of chunks of data to a file and optionally compress each chunk (very much like a zip file) and allow fast random-access reading of the file later on. It does not do zip as a zip itself has more complexity than is needed, and it was much simpler to implement this once here. EET is extremely fast, small and simple. EET files can be very small and highly compressed, making them very optimal for just sending across the Internet without having to archive, compress or decompress and install them. They allow for lightning-fast random-access reads once created, making them perfect for storing data that is written once (or rarely) and read many times, but the program does not want to have to read it all in at once. It also can encode and decode data structures in memory, as well as image data for saving to EET files or sending across the network to other machines, or just writing to arbitrary files on the system. All data is encoded in a platform independent way and can be written and read by any architecture.
2004-10-13 10:57:55 +02:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= eet
Import eet from pkgsrc-wip. Packaged by Peter Bex and modified by me. EET is a tiny library designed to write an arbitrary set of chunks of data to a file and optionally compress each chunk (very much like a zip file) and allow fast random-access reading of the file later on. It does not do zip as a zip itself has more complexity than is needed, and it was much simpler to implement this once here. EET is extremely fast, small and simple. EET files can be very small and highly compressed, making them very optimal for just sending across the Internet without having to archive, compress or decompress and install them. They allow for lightning-fast random-access reads once created, making them perfect for storing data that is written once (or rarely) and read many times, but the program does not want to have to read it all in at once. It also can encode and decode data structures in memory, as well as image data for saving to EET files or sending across the network to other machines, or just writing to arbitrary files on the system. All data is encoded in a platform independent way and can be written and read by any architecture.
2004-10-13 10:57:55 +02:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
.if !defined(EET_BUILDLINK3_MK)
EET_BUILDLINK3_MK:=
Import eet from pkgsrc-wip. Packaged by Peter Bex and modified by me. EET is a tiny library designed to write an arbitrary set of chunks of data to a file and optionally compress each chunk (very much like a zip file) and allow fast random-access reading of the file later on. It does not do zip as a zip itself has more complexity than is needed, and it was much simpler to implement this once here. EET is extremely fast, small and simple. EET files can be very small and highly compressed, making them very optimal for just sending across the Internet without having to archive, compress or decompress and install them. They allow for lightning-fast random-access reads once created, making them perfect for storing data that is written once (or rarely) and read many times, but the program does not want to have to read it all in at once. It also can encode and decode data structures in memory, as well as image data for saving to EET files or sending across the network to other machines, or just writing to arbitrary files on the system. All data is encoded in a platform independent way and can be written and read by any architecture.
2004-10-13 10:57:55 +02:00
Update to eet-1.0.1 from e17. This is the first real release and no real ChangeLog is present.
2008-06-22 03:21:31 +02:00
BUILDLINK_API_DEPENDS.eet+= eet>=1.0.1
Second try at jpeg-8 recursive PKGREVISION bump.
2010-01-18 10:58:37 +01:00
BUILDLINK_ABI_DEPENDS.eet?= eet>=1.2.3nb2
eet is not in pkgsrc-wip any more.
2004-10-13 11:03:35 +02:00
BUILDLINK_PKGSRCDIR.eet?= ../../devel/eet
Import eet from pkgsrc-wip. Packaged by Peter Bex and modified by me. EET is a tiny library designed to write an arbitrary set of chunks of data to a file and optionally compress each chunk (very much like a zip file) and allow fast random-access reading of the file later on. It does not do zip as a zip itself has more complexity than is needed, and it was much simpler to implement this once here. EET is extremely fast, small and simple. EET files can be very small and highly compressed, making them very optimal for just sending across the Internet without having to archive, compress or decompress and install them. They allow for lightning-fast random-access reads once created, making them perfect for storing data that is written once (or rarely) and read many times, but the program does not want to have to read it all in at once. It also can encode and decode data structures in memory, as well as image data for saving to EET files or sending across the network to other machines, or just writing to arbitrary files on the system. All data is encoded in a platform independent way and can be written and read by any architecture.
2004-10-13 10:57:55 +02:00
Update eet to 1.2.0. Changes: * Make use of eina. * Fix string in list and hash. * Fix array in eet_data. * Add crypto support to eet with OpenSSL. * Add GNUtls support to eet. * Make password callback work with GNUtls. * Add a function to retrieve raw signature. * Fix a corrupted pointer use in eet_cipher.c * Add some missing __UNUSED__ flags. * Fix problem reported by llvm * Add sha1 retrieval for an Eet_File. * Force fsync() after data is written to file, solve ext4 issues. * Disable fsync. Edit the code if you need it. * Make eet_data thread safe. * Fix eet pkg-config dependencies. * Fix double init of gcry. * Release eet 1.2.0
2009-06-10 08:40:11 +02:00
.include "../../devel/eina/buildlink3.mk"
Import eet from pkgsrc-wip. Packaged by Peter Bex and modified by me. EET is a tiny library designed to write an arbitrary set of chunks of data to a file and optionally compress each chunk (very much like a zip file) and allow fast random-access reading of the file later on. It does not do zip as a zip itself has more complexity than is needed, and it was much simpler to implement this once here. EET is extremely fast, small and simple. EET files can be very small and highly compressed, making them very optimal for just sending across the Internet without having to archive, compress or decompress and install them. They allow for lightning-fast random-access reads once created, making them perfect for storing data that is written once (or rarely) and read many times, but the program does not want to have to read it all in at once. It also can encode and decode data structures in memory, as well as image data for saving to EET files or sending across the network to other machines, or just writing to arbitrary files on the system. All data is encoded in a platform independent way and can be written and read by any architecture.
2004-10-13 10:57:55 +02:00
.include "../../devel/zlib/buildlink3.mk"
.include "../../graphics/jpeg/buildlink3.mk"
Expose OpenSSL so that the pkgconfig file works.
2009-09-11 23:48:01 +02:00
.include "../../security/openssl/buildlink3.mk"
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
.endif # EET_BUILDLINK3_MK
Import eet from pkgsrc-wip. Packaged by Peter Bex and modified by me. EET is a tiny library designed to write an arbitrary set of chunks of data to a file and optionally compress each chunk (very much like a zip file) and allow fast random-access reading of the file later on. It does not do zip as a zip itself has more complexity than is needed, and it was much simpler to implement this once here. EET is extremely fast, small and simple. EET files can be very small and highly compressed, making them very optimal for just sending across the Internet without having to archive, compress or decompress and install them. They allow for lightning-fast random-access reads once created, making them perfect for storing data that is written once (or rarely) and read many times, but the program does not want to have to read it all in at once. It also can encode and decode data structures in memory, as well as image data for saving to EET files or sending across the network to other machines, or just writing to arbitrary files on the system. All data is encoded in a platform independent way and can be written and read by any architecture.
2004-10-13 10:57:55 +02:00
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= -eet
Reference in a new issue Copy permalink