Build Gear is a lightweight build tool for building embedded firmware. Its primary focus is to make it easy to create and maintain fully-customized embedded firmware. This is reflected in a straightforward commandline interface and support for easy-to-understand build files. The secondary focus is build performance and build integrity. Build Gear is easy to use and well-suited for rapid prototyping and product development of GNU/Linux firmware to be deployed in small-to-medium-sized embedded systems.
RPSL (Rapid Prototyping Shared Library) is a set of bash scripts and utility files that coordinate the GNU autotools and pkg-config for C/C++ build automation. The scripts and procedures define a system for building and linking that supports an individual or small group. A single command (rpslSyncBuild) scans for source, writes a Makefile.am and Configure.ac, and produces a conventional autotools tree ready for the usual "configure, make, make install" build steps.
Cinabox (Continuous Integration in a Box) automates the setup of a Continuous Integration (CI) system by doing The Simplest Thing That Could Possibly Work. It consists of two simple scripts to set up a cruisecontrolrb CI server from scratch on an Ubuntu 8.04 system: one script to bootstrap Ruby, and another script to set up CI.
cygbuild is a porting tool for making Cygwin net releases. It helps Cygwin source and binary package maintainers to configure, build, strip, produce diffs, and generate Cygwin specific files. To put it simply, it converts any freely available program or package into a complete Cygwin net release distribution.
depfinder finds the dependencies of Slackware packages. The dependency list can be output to stdout, to a .dep text file without version information, or to a slack-required file with version information. depfinder is very fast; its speed is mainly due to the C++ code that is used in depfinder to find in which package each individual library is included. It also has support for running multiple jobs, which makes it a lot faster when used with multiple CPUs/cores. depfinder supports detecting dependencies of binary files compiled with languages such as C or C++ and it can also detect Python dependencies.
The Mknew Project is an investigation of how to build simple Unix shell scripts to manage common development and administrative tasks. The emphasis is on using languages and tools that already exist and are in common use. A related emphasis is on exploring the functional programming nature of the bash shell. This is accomplished by using the bash function capability, and using the bash "$(" ")"syntax to delay function execution in bash scripts. This allows building scripts that have a LISP-like function syntax that permits shell scripts to be written as a series of function calls with minimal syntax. The goal is to provide a way to specify make procedures of heterogeneous components in a bash script. These can include diverse source code languages, documentation text, test procedures, and data. In addition to the mknew function library (mklib), these "make" procedures rely only on capabilities provided by the bash shell, and common Unix command line utilities.
no-pkg-config is a bash script which implements the functionality of the standard pkg-config utility. It is intended for users of minimal systems who want to use pkg-config but do not want to install all the dependencies of the standard implementation. Most of the important features of the original implementation are supported. The commandline syntax and .pc file format are the same as the original. To use it, just place the script somewhere in your PATH and give it execute permissions.
pkgmake automates some steps when making software releases. It creates a copy of the development tree, optionally cleans it up a bit (i.e. removes CVS/* and .svn/*), tars it, places the tarball in the SOURCES/ directory, creates the corresponding .spec file from a provided template (and the data specified in the configuration/on the command line), and runs rpmbuild and/or debbuild as well as spec2arch. As a result, you will have packages for Debian and RPM based distributions as well as the PKGBUILD file for ArchLinux. Using relman as the recommended frontend to pkgmake, new software releases are as easy as calling relman with two parameters: the project name plus the release version - and all packages are made and distributed.