Free 4.0 build 80123 software for linux

VMware Server product is a robust yet easy to use software for users new to server virtualization technology.
VMware Server enables companies to partition a physical server into multiple virtual machines, and to start experiencing the benefits of virtualization.
Benefits of VMware Server
Provision a new server in minutes without investing in new hardware.
Run Windows and Linux operating systems and applications on the same physical server.
Increase the utilization of a physical server.
Move virtual machines from one physical host to another without re-configuration.
With VMware Server you can:
Streamline software development and testing by allowing developers to create multiple environments with different operating systems on the same server.
Evaluate software in ready-to-run virtual machines without installation and configuration.
Re-host legacy operating systems such as Windows NT Server 4.0 and Windows 2000 Server in a virtual machine running on new hardware and operating system.
Simplify server provisioning by building a virtual machine once and deploying it multiple times.
Leverage pre-built, ready-to-run virtual appliances that include virtual hardware, operating system and application environments. Virtual appliances for Web, email, proxy and other infratructure services are available for download from the VMTN Virtual Machine Center.
VMware Server is the first step to VMware Virtual Infrastructure
While VMware Server is a compelling product for new virtualization users, VMware Virtual Infrastructure products-ESX Server with Virtual SMP and VirtualCenter with VMotion-enable companies to implement large-scale production server consolidation, business continuity, and enterprise desktop solutions with enterprise-class performance, high availability, manageability and security. View a comparison between VMware Server and VMware Virtual Infrastructure.
Enhancements:
- This release fixes four security vulnerabilities, as reported in CVE-2007-1337, CVE-2007-1877, CVE-2007-1069, and CVE-2007-1876.
- These vulnerabilities permitted denial of service, crashes of Windows guests, or corrupted stack pointers.
- A problem with VMware Tools that caused the guest to run out of memory was fixed.
- A crash in the VIX API was resolved.
- Building of the kernel and the HGFS modules was improved.
- Several occasional crashes were fixed.

Autobuild project consists of a tool to process software build logs and generate HTML.
Autobuild is a package that processes output from building software, primarily focused on packages using Autoconf and Automake, and generates HTML summaries.
The output includes project name, version, build host types, build host name, and indication of success or failure.
The output is indexed in many ways to simplify browsing.
Enhancements:
- The tools now use cf-shell.sf.net instead of shell.sf.net.

Java::Build is a family of modules which you can use instead of Ant.

SYNOPSIS

use Java::Build::JVM; # access to the javac compiler in one jvm
use Java::Build::Tasks; # some helpful methods similar to Ant tasks

my $source_files = build_file_list(
BASE_DIR => $some_path,
INCLUDE_PATTERNS => [ qr/.java$/ ],
);
my $dirty_sources = what_needs_compiling(
SOURCE_FILE_LIST => $source_files,
);
if (@$dirty_sources) {
my $compiler = Java::Ant::JVM->getCompiler();
$compiler->destination($base_dir);
$compiler->classpath($base_dir);
$compiler->compile($dirty_sources);

my $class_files = build_file_list(
BASE_DIR => $some_path,
INCLUDE_PATTERNS => [ qr/.class$/ ],
EXCLUDE_PATTERNS => [ qr/Test/ ],
EXCLUDE_DEFAULTS => 1,
STRIP_BASE_DIR => 1,
);
jar(
JAR_FILE => $jar_file_name,
FILE_LIST => $class_files,
BASE_DIR => $some_path,
);
}

ABSTRACT

This family of modules helped me move away from Ant to a proper scripting language, namely Perl. With it you can use a single JVM for compiling your java programs. It provides many useful methods to help you build lists of files, package them with jar, etc. Currently the modules are unix centric. If you make them work elsewhere, please send in patches.

Boost.Build is a system for large project software construction, which is simple to use and powerfull. Boost.Build project is an onging project to rewrite Boost.Build, improving design and making it more extensible.
Main features:
- Simple and high level target description language. In most cases name of target and list of sources is enough.
- Variant builds. You can build with your choice of basic variants (e.g. debug, release, profile...), toolsets (e.g. gcc and msvc) and specific properties (e.g. inlining off) from a single command invocation.
- Portability. ``Feature Normalization allows to fine-tune targets independently from the toolset used, and modular toolset descriptions are employed to generate actual build instructions.
- Multi-project builds. Several projects can be combined and built together, with dependencies correctly tracked. Typically, the setting (like include paths and defines) needed to use other project will be handled automatically.
- Extensibility. New file types and tools can be easily added
Enhancements:
- Support was added for several new tools, including the Qt4 library.
- An "indirect requirement" feature was added.
- Several improvements were made in the "install" target.
- The --build-dir, --debug-building, and --clean-all command line options were added.
- Numerous bugs were fixed, and interface improvements were done.

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)

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.

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.