UIML stands for User Interface Markup Language. It is an XML-family language for user interface description. The basic idea is to build user interfaces for various platforms from one description (source). The description consists of a widget structure definition, widget properties, reaction on events, widget set description, application logic, etc. The project aim is to build a Python renderer for UIML. It supports static rendering and wxPython. See additional info on UIML at www.UIML.org
smake is a highly portable 'make' program that makes commands up to date based on rules in Makefiles and on the timestamps of the related files. It implements a complete superset of the features of the classical POSIX/Unix make program. It warns about typical misuse of dynamic macros that prevent portability of makefiles. Its automake features allow you to run scripts to automatically create rules for unknown platforms.
XML-Lit is a simple program to perform very basic literate programming with any XML-based markup language. It uses James Clark's Expat XML parser to weave (convert to a form suitable for processing) and tangle (extract the source code from) your XML documents. It has only been tested with DocBook at the moment, but there is no reason why it should not work with any arbitrary XML markup.
gstdint.h installs a header file, "gstdint.h", that will "#include" the "stdint.h" or "inttypes.h" header file of the local system - if one of these exists. Otherwise the bitsizes of basic types are detected for the local libc/compiler pair, and the C96 inttypes typedefs are generated into "gstdint.h".
CUT is a unit-testing framework for C, C++, and Objective-C. Unlike other unit testing tools, CUT doesn't strive to be an SUnit clone. It automates a lot of the drudge work often encountered when using other unit testing packages for the C family of programming languages. CUT may also be used to unit-test assembly language software in some circumstances.
prtpacker (Portable Resource Tree Packer, pronounced PIRT-Packer) is a tool for creating C or C++ source code from external program resources such as images, text, or data. These resources can be arranged in a tree structure much like a typical file system. After compiling and linking the resulting source code you can access the resource tree from within your software through a simple API. Be aware that all resources stay in memory and cannot be easily deallocated.