Projects

GNU Libtool

GNU Libtool hides the complexity of using shared libraries behind a consistent, portable interface. GNU Libtool ships with GNU libltdl, which hides the complexity of loading dynamic runtime libraries (modules) behind a consistent, portable interface.

Buildbot

The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. ... [More] The guilty developer can be identified and harassed without human intervention. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve. [Less]

Waf

Waf is a general-purpose build system which was modelled from Scons. Though it comes last in the arena of the build systems, we believe that Waf is a vastly superior alternative to its competitors (Autotools, Scons, Cmake, Ant, etc) for building software, and especially for open-source projects: ... [More] * Waf depends on Python only which is ported on most platforms * Waf scripts are Python modules which are easier to learn and to maintain that custom languages * Waf license has very little constraints (BSD) and can be redistributed easily (all in one 100kb script) * Waf architecture is modular and can be extended easily, it relies on state-of-the-art algorithms * Waf provides many more features than its competitors * Waf provides many small projects and code snippets [Less]

testfarm

TestFarm is a client-server Python application that allows you to monitor the stability and efficiency of a development project by performing continuous builds and tests on multiple platforms. The overall idea is based on Mozilla Tinderbox, or buildbot but with a much simpler approach and sound extensibility mechanisms.

Savadur

Savadur is a simple client/server build bot. It is very flexible and fully configurable in XML.

XChat-WDK

XChat-WDK is a patchset for XChat SVN which allows for building on Windows using the Windows Driver Kit. This results in binaries usable across all versions of Windows starting from XP. In human language it means it's a free build of XChat for Windows. XChat-WDK aims to follow the changes ... [More] made to the main XChat source tree. It doesn't aim to add new features or so. Since it's just a maintenance patch, if you report a problem you should try to provide a solution as well. If you don't, it's quite unlikely it will get solved unless it gets solved in the XChat tree. [Less]

easybuild-framework

EasyBuild is a software installation framework in Python that allows you to install software in a structured and robust way.

GradleFx

Gradle plugin for building Flex projects. LATEST VERSION: 0.5

orogeny

So you've used Ant, played with JRake, thought Schmant was cool and couldn't face using make again... Why does building Java code have to be so hard? Wouldn't it be easier if you could write in Java to build it? And why can't it be simpler to debug build scripts and files? Well ... [More] , now you can. Enter orogeny! It's free, open source and has the collective wisdom of tens of man years of software development behind it. Orogeny is just a build tool. Like all the best software, it's very singularly focused. It does things one way, with the principal of least surprise. It's designed to compile java into an useful output - executable, modern jars ready to just execute and go. It doesn't care about your source control system, it doesn't force you to use dependency libraries like maven and it does make the simplest tool around. You can extend it - you write Java. You can have IntelliJ intellisense it! [Less]

grill

About GrillGrill is a generic build system designed to have the build recipes decoupled from the implementation of the build system. That way any third party is free to use alternatives to the provided implementation. Specifically Grill provides: A specification for creating build ... [More] "recipes" in XML A build system using these XML build recipes The build recipes are much similar to Ant in syntax, but void of the Java-isms. The language is completely generic and extensible. The Grill RecipesThe build recipe schema is based around a few simple ideas: Declarative syntax, nothing is infered or implied. Ie. there are no magic variables whose existence is inferred from other magic variables. What you write is what you get. Extensible Avoid "scripting" by providing useful constructs to fulfill 90% of the needs of most projects. Make the common parts easy, but don't pretend or try to make complex tasks simple Should be easy to debug Should be easy to validate for the build system It should be easy for the build system to provide concise and informal error messages Not be aimed at compiling code for any specific language The Grill ImplementationThe actual implementation of the Grill recipe builder is based around a few core concepts: Provide strict validation of the build recipes Precise and verbose error messages Do not pollute the source tree with build artifacts Nothing gets in without unit tests Relations to Other Build ToolsAutotools: While Grill was created partly because of dissatisfaction with the GNU Autotools, it is not the goal of Grill to replace them. Indeed a core functionality of Grill is to compile an Autotools setup from the Grill recipe to use in your distributions. That way end-user-compilers will still use the good old configure && make && sudo make install routine. Waf: It is the hope that we can some day integrate with Waf to make Waf build Grill recipes. Ant: Grill recipes are very similar to Ant in syntax and does draw on the massive experience of the development behind Ant. Ant contains some Java-isms, that are good when you develop Java, but might seem odd when developing a C program with GObjects. Therefore Grill tries a more generic approach that should seem fairly natural in most programming languages, but not optimized for any specific. [Less]