ANGIF is a C library to generate GIF format output. It can generate animated GIFs or true-color (24-bit) GIFs (using both at the same time, however, does not display properly on common browsers). ANGIF is completely LZW-free. There is no code implementing the patented LZW algorithm. That also means there is no compression and the files will actually be larger than a raw file with the same image by about 13% to 16% more. Command line level test programs are included. This is a quick rough-cut beta version with documentation only in the source code (the source code actually is commented).
AVLMAP is a key:data pair data mapping (associative array) library for C programming based on AVL balanced binary trees. Added features include ordered data retrieval forward or reverse, support for optional duplicate keys (e.g. an extra linked list not needed), and the ability to find the nearest member if an exact match isn't available. Both key and data types may be selected from a choice of C data types including string and array variations. One mapping always has one key type, but data types may be mixed within a mapping.
rmd160 should be considered obsolete and inactive. OpenSSL includes most of the functionality. rmd160 is a library with an easier to use programmer calling interface than the algorithm's reference version. Features include multiple digesting instances, arbitrary data length appending, and different forms of checksum conversion. The calling program will not have to be concerned with machine byte order or arranging data into 16 word groups. Documentation is in HTML which is included, and is also viewable online (see the homepage).
BICK builds a bootable Linux ISO image from a file tree that represents the run time file tree loaded into tmpfs with options to leave /opt and /usr mounted on the CDROM to save space. For systems with enough RAM, up to as much file data as will fit on the CDROM can be loaded; initial ramdisk is not used for the runtime files.
LIBH is a general purpose C library consisting of a collection of several different sections of handy and helpful functions and macros for a variety of purposes. Sections include bit manipulation, string manipulation, I/O enhancement, date/time tools, list handling, tree handling, debug tools, a daemon tool, and CGI/HTML code.
Re: Binaries & Why Makefiles in Python are bad...
Without compiling, how can you combine patches that add features coming from a couple of different authors?
Sometimes a local autoconf really is needed
Sometimes a local autoconf really is needed. One example of that is when merging in a patch from a different author to add a new feature. Such patches can't just include a new configure script, since that would conflict with another patch from another author. What you have to do is apply all the patches, which may even change configure.in, and if they do so, you have to re-run autoconf yourself. The problem here is you have a very narrow window of version compatibility that might be made even worse depending on the patches actually used. Given a number of different autoconf versions around, this isn't trivial. I've also found that when upgrading autoconf to accomodate one package, it broke yet another package. It just isn't as portable as we have been led to believe.