Free build it fast software for linux

Buildog was inspired by my need to track the steps involved in software builds. Particularly the software packages in the Linux From Scratch book.

It is not a package manager in the traditional sense, it will not track dependences. It tries to stay out of your way as much as possible.

If you grow weary of RPM spec files, or this months "package manager" (there are about a dozen or so of them out there, with new distributions adding their own every month) Buildog may be for you.

What it will do for you is log the information required to build it, files it created, URLs it needs (it will fetch them for you too if you want, with support for mirrors and caching) a log of the build stages, notes and descriptions, its home page, and any other information you may wish to add.

Its pretty simple to use, if youve ever installed packages from source, youll get the hang if it quickly.

Installation

Quite a bit of work has gone into making this install nicely. Perl programs are kind of notorious for being difficult to install.

It uses the autoconf to guess your location of perl, supports the usual --prefix --bindir --sysconfdir and --localstatedir options. Type make install to install it, (a plain make shows what will be installed where).

hbuild53 (hastek build for FreeBSD 5.3 onward) is a script package to help build FreeBSD base systems. It makes sense if you have multiple systems to build.

hbuild53 will work on FreeBSD 4.x - however the base kernel configuration file will not - as of 5.2.1 the base kernel configuration file is too different.

hbuild53 provides automation for some of the things you might typically do after a base FreeBSD installation. This is relatively simple stuff but has saved me time when building/rebuilding/upgrading multiple systems.

This idea will probably make sense to those who build multiple machines, and will not make sense if you work with one or two systems only..

This package is intended to help start a server build (not to be installed over existing systems, though it probably wont hurt anything to do so), assuming you will be building
other applications later as you build your final platform.

This package is specific to FreeBSD 5.3-RELEASE onward. It will upgrade your ports tree, install ports, create some customizations, and provide some sysadmin packages, such as log archivers, a chrooted BIND builder, a heirarchichal unix platform backup system, shows how to set up serial console, a new kernel, and ipf for packet filtering.

Each hbuild subdirectory has bits you might be able to adapt into your own system administration.

You will need a reasonably fast internet connection for the ports. Why install ports rather than packages? You dont have to, but I always thought its better to build the software on the particular system, although it takes longer.

Build Order Anlyzer for the Axis & Allies RTS is a tool for analyzing builds in the Axis & Allies RTS game. Many sites go to great lengths to explain Build Orders, but the Build Order Analyzer is the first tool to actually allow players the ability to define a Build Order and then compare it to other Build Orders over time.

Key Facts to know about the Build Order Analyzer:

Only tool of its kind
Can support multiple types of RTS based games (not just Axis & Allies RTS!)
Built on Java technology & open source software

The Build Order Anlyzer 2.0 for Axis & Allies RTS is a tool for analyzing builds in the Axis & Allies RTS game. Wikipedia has a great defnition for a Build Order. To summarize, a Build Order in an RTS game defines the order in which a player builds their buildings, units, and upgrades. Understanding the timing and affect of various build trees is critical in making the appropriate tactical decisions during the game.

The BOA allows a player to build and analyze multiple Build Orders without playing a game. Lose to a player due to their build? Then plug it into the BOA and figure out a build to counter it! Gamers no longer have to play game, after game, after game to figure out a decent counter to another players Build Order, they can use the BOA to figure it out. The BOA can literally save serious gamers hundreds of hours of game play!

Exact Build project is a sane GNU Auto replacement. For portable build systems nowadays normally GNU autoconf and the associated companiens such as automake and libtool. However albeit portable they are rather crufty to use. The various macro expansion and generation steps extremely blow up the initial definitions and make execution slow and debugging a nightmare.

Even with the enourmous code bloat, it does not have a wide feature set and neither allows to maximize the gain of parallel builds nor other state-of-the-art compiler features. Manual tinkering is needed in such cases.

Mostly due the code bloat but also to obtain features such as mximal parallel build and object output seperated cleanly from the source, we create our own set of Makefiles for the non-recursive build system and shell scripts for configuration, if required by the software module (some straight forware code does come without a configure script at all).

auto-build is a Perl module that can run automated, unattended software build processes.

SYNOPSIS

# auto-build [OPTION]...
Run build using latest code currently in source control
# auto-build --config /etc/auto-build.d/auto-build.conf
Run build using code committed prior to 12:30 on Dec 12th 2004
# auto-build --timestamp 12:30:00 Dec 12th 2004
--config /etc/auto-build.d/auto-build.conf

SUMMARY

auto-build is the command used to execute the Test-AutoBuild software build automation framework. It is intended to execute a single iteration of the build engine and then quit with its exit status providing an indication of the build success / fail status (see the EXIT STATUS section later in this manual page). To perform a continous automated build this command would be launched on a frequent basis from cron. Locking will ensure that two instances do not execute concurrently, so it can safely be triggered every 5 minutes.

OPTIONS

The following command line options are valid:

--config=FILE

Specify an alternative path to the configuration file for the build process. If ommitted, will default to looking for the file $HOME/auto-build.conf. The configuration data is loaded by the Config::Record module, so refer to that modules manual page for details of permitted syntax. The file will also be pre-processed by the Template module allowing dynamic generation of complex configuration files

--log4perl=FILE

Specify an alternative file containing configuration settings for the Log::Log4perl logging system. If ommitted, log4perl settings will be loaded from the master autobuild configuration file.

--timestamp=DATE

Specify the timestamp to use when checking code out of the source control repositories. For repository modules supporting timestamps it is guarenteed that the code checked out will be the latest version not newer than this timestamp. If ommitted, the timestamp will default to the current timestamp. The argument can be either an plain integer specifying number of seconds since the epoch, or any of the text representations handled by the Date::Manip module

today
1st thursday in June 1992
05/10/93
12:30 Dec 12th 1880
8:00pm december tenth

--verbose

Increase the verbosity of warning messages and errors. This will ensure that if the builder unexpectedly crashes, a complete stack trace will be dumped along will full arguments.It will also cause the post-processed configuration file to be dumped.

--help

Display a summary of the command line help options

Turnracer is an free TBS racer game for GNU/Linux and other UNIX look-alikes. The rules of Turnracer arent easy.
Turnracer is written in C, and Gtk2 based. There is not yet an AI in the game, but it is planed for one of the next releases.
Installation:
1. Make sure you have install tar an gz or bz2 (gz if you have downloaded the gz package, else the bz2)
2. Type tar -xzf THE/PATH/TO/THE/TURNRACER/PACKAGE.tar.gz(in a terminal emulator), change the z to j for bz2.
3. Go to the directory where you have unpacked turnracer(cd THE/PATH)
4. Type ./configure
5. Type make
6. Type make install (as superuser)
Enhancements:
- A level editor is included.

L4ip is a daemon that extends IPFilters simple round-robin L4 load balancing with health checks. It takes care of monitoring and dynamically adding and removing ipnat rules in the kernel.
L4ip fully supports UDP, TCP, and system()-style executions for health checks, including send/expect scripts, SSL connections, and much more.
Main features:
- Define as many clusters, with as many members as you need.
- Automatically adds and removes "ipnat" rules as needed.
- Flexible health check support, tcp-open, tcp-close, udp-open, udp-close, system.
- Simple scripting available for health checks in send/expect syntax with fnmatch pattern comparison
- Binary protocol supported in url-encoding style syntax (eg %0D)
- system() like execution of external commands available. (spawn your own health-check testers)
- Reload and restart leaving last-known-state available for less service impact.
- SSL supported for TCP testers.
- Optional IPF rules to sense RST return-packets for faster failure detection.
Enhancements:
- Solaris SMF example files were added along with a "proxy" command for protocols that need it, such as FTP and IPSec.