Free build a bear 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).

Wx::build::MakeMaker is a Perl module with ExtUtils::MakeMaker specialization for wxPerl modules.

SYNOPSIS

use Wx::build::MakeMaker;
wxWriteMakefile( NAME => My::Module, VERSION_FROM => Module.pm );

FUNCTIONS

wxWriteMakefile
wxWriteMakefile( arameter => value, ... );

This functions is meant to be used exactly as ExtUtils::MakeMaker::WriteMakefile (see). It accepts all WriteMakefiles parameters, plus:

WX_CORE_LIB
WX_CORE_LIB => xrc core base

link libraries from wxWidgets core or contrib directory. If not spedified, defaults to adv html core net base for compatibility.

WX_LIB
WX_LIB => -lxrc

Link additional libraries from wxWidgets contrib directory.

REQUIRE_WX
REQUIRE_WX => 2.003002 # wxWidgets 2.3.2

Do not build this module if wxWidgets version is lower than the version specified.

NO_WX_PLATFORMS
NO_WX_PLATFORMS => [ x11, msw ]

Do not build this module on the specified platform(s).

ON_WX_PLATFORMs
ON_WX_PLATFORMS => [ gtk ]

only build this module on the specified platform(s).

game is a simple Tetris-like game.
The objective of the game is to keep the level of colored blocks down as long as possible.
New blocks are falling down at an increasing rate, blocks can be removed by creating rows of three or more blocks of the same color. The longer the row,
the more points you get.
Usage:
The objective of the game is to keep the level of colored blocks down as long as possible. New blocks are falling down at an increasing rate, blocks can be removed by creating rows of three or more blocks of the same color. The longer the row, the more points you get.
space - Flip two neighbour blocks.
arrow keys - Move cursor
h,j,k,l - Move cursor (vi-fans)
escape - Quit game, no questions asked.
s - Starts the game. If a game is in progress, a new game
will be started instantly.
p - Pause game. To avoid cheating, the game will be hidden
during pause.
e - Generate earthquake. This can be used as a last resort in
case of panic, and will remove approximately 30 blocks from
the field. It might help you. Then again, it might not.
Can be used once per game and costs 50 points.
Installation:
Linux:
Make sure the SDL, SDL_image and SDL_mixer runtime libraries are installed
$ tar -zxvf game- -linux.tgz
$ cd game
$ ./game
Enhancements:
- Added better error handling on SDL img load failures

KJam is a build tool like make. It uses a syntax similar to Jam, with more powerful features than the original Jam.
It has built-in very fast dependency scanning, per-target viewpathing, and C-like control flow. It is optimized for multi-processor machines. It can accelerate building by launching build actions on a distributed peer to peer network of build servers.
KJam Build Tool is designed to support large projects with thousands of targets, or projects requiring building on many target architectures.
KJam is designed to be:
Unintrusive and clean KJam is small. It has negligible CPU overhead, and it doesnt create or leave behind temporary files.
Scalable KJam is able to build large projects spread across many directories in a single pass and can manage and distribute build steps to multiple processors on one or more networked machines.
Highly portable KJam currently runs only on Windows, but it is designed to be easily portable. Ports to Linux and OSX are planned.
Multiplatform Platform independent rules and platform specific actions can be defined separately from dependency rules.
Customizable Developers can enhance and extend KJam by creating user defined rules to utilize other built-in directives.
Language KJam includes flow-control statements, variables, and a few other features of general purpose languages.
Automatic Dependencies KJam computes dependencies for its targets during building. There is no need for a separate off-line make depend step.
Enhancements:
- A new "immediate" action modifier keyword was added, which causes actions to be run as soon as they are parsed, instead of during the command phase.
- Output formatting was improved.
- Several bugs were fixed.

kdesvn-build script builds KDE from its Subversion source repository. Well, that and a *LOT* more...
It builds qt-copy, automatically includes unsermake in the build, easily supports being run from cron, allows module-specific options such as configure flags, logs everything, and generally makes it as easy as possible to manage a bleeding edge KDE installation.
kdesvn-build by default will install things into a ~/kde directory, but it supports using your system KDE if you just want to install e.g. an application from Extragear.
Its incredibly featureful, although Ive tried hard to setup sane default options so that you dont have to worry about twiddling the knobs.
Main features:
- Will automatically checkout and update the KDE source code from its Subversion repository.
- Will download and use unsermake, an advanced build tool that can significantly decrease compile time, especially over distributed systems. It also supports progress estimates of compile progress.
- kdesvn-build logs everything for easy perusal later, that way you can determine why things went wrong if a build fails. kdesvn-build automatically creates symlinks for easy access to the last log (log/latest).
- color-coding of the output (which can be turned off)
- Has support for qt-copy, the KDE snapshort of Trolltechs Qt library, optionally with bugfix/optimization patches applied that havent made it into the official library.
- kdesvn-build is very customizable. You can control most options down to a module-by-module basis if you so desire, including configure-flags and your C++ flags during compilation. Instead of trying to remember what configure line you used, you can set it once and forget it.
- Extensive documentation, including a Wiki page. Feel free to let me know if you need something explained (e-mail address at bottom). Or you can join #kdesvn-build on irc.kde.org for help.
- A detailed sample configuration file is included, usually you can just copy it to ~/.kdesvn-buildrc and be done with it.
- Much more!
Enhancements:
- Some Coverity-scanner-specific code has been factored out into a plugin (in kdesdk/scripts, dont worry).
- The progress output feature works with CMake now (CMake 2.4.3 or greater)

Tete project is an ear trainer.

Tete allows you to select intervals, chords, or scales and play examples of the selected sounds in a random order.

As each is played, it is highlighted in the list. Once you think you can tell what is playing, you can test yourself.

A series of sounds will be played, again at random, and you attempt to identify what has been played.

You can control how each sound is played back by changing the MIDI instrument, the octave range allowable, the root note, and whether the sounds are played ascending or descending.

Java::Build::Tasks is a Perl module that collects common Java build tasks in one place: jar, jarsigner, etc.

SYNOPSIS

use Java::Build::Tasks;

set_logger($log_object);

copy_file(source, dest);
copy_file(list, of, sources, dest);
copy_file(-r, list, of, sources, with, flags, dest);
copy_file([ list, of, sources ], dest);
copy_file([ -r, list, of, sources, with, flags ], dest);

my $file_list = build_file_list(
BASE_DIR => where/to/start,
EXCLUDE_PATTERNS => [ qr/leave/, qr/these/, qr/out/ ],
INCLUDE_PATTERNS => [ qr/.*include/, qr/these.*/ ],
EXCLUDE_DEFAULTS => 1,
STRIP_BASE_DIR => 1,
QUOTE_DOLLARS => 1,
);

jar(
JAR_FILE => some/full/path/ending/in/a.jar,
FILE_LIST => $file_list;
MANIFEST => location/of/manifest/to/put/in/jar,
BASE_DIR => path/to/change/to/before/building/jar,
APPEND => 1,
);

signjar(
JAR_FILE => what/to/sign,
KEYSTORE => path/to/your/keystore,
ALIAS => $your_alias,
STOREPASS => $your_keystore_pass,
);

my $config_hash = read_prop_file($prop_file_name);

update_prop_file(
NAME => /optional/path/and/file.properties,
NEW_PROPS => %values_to_add_or_update,
);

filter_file(
INPUT => t/file1,
OUTPUT => t/file2,
FILTERS => [
sub { my $string = shift; $string =~ s/Happy/Joyous/g; $_;}
],
);

my $dirties = what_needs_compiling(
SOURCE_FILE_LIST => $list,
SOURCE_DIR => path/to/your/source/files,
DEST_DIR => path/to/your/compiled/files,
SOURCE_TO_COMPILIED_NAME => sub { ... },
);

my $classpath = make_jar_classpath(
DIRS => [ /path/to/some/set/of/jars,
/path/to/some/other/jars ],
INCLUDE_PATTERNS => [ qr/.jar$/, qr/.ZIP$/ ], # optional
);

purge_dirs($base_dir, qw(sub directories to remove));