Projects

CMake

CMake is a cross-platform, open-source build system. It is used to control the software compilation process using simple platform and compiler independent configuration files. CMake generates native makefiles and workspaces that can be used in the compiler environment of your choice, such as GNU Make, Visual Studio, and Xcode.

Pre Make Kit

The Pre Make Kit project is a toolkit providing a collection of tools aimed to ease a lot of stages in project development. It provides a scanner that generates template source components such as configuration file or makefile. It also provides a dependency checker that sets up templates files ... [More] depending on the system components (such as auto* tools or similar projects). For portability purpose, a BSD like install program is also part of the kit. [Less]

protoj

Roadmap Version 2.0.0 Work on version 2.0.0 has already started that will: greatly solidify the code-base and depart from the maven-style command line include full and extensive documentation transform the jboss demonstration project into a quickfix based trading application introduce beanshell ... [More] to make every part of the project as clean as possible This will take months to complete. If you believe in pure java builds and you have a real contribution to make then please email me at ashpublic@mac.com Ashley Williams June 2009 Introducing ProtoJ The Pure Java Build APIProtoJ is a pure java build, installation and deployment library that hands control over to you. There's no third-party ProtoJ application directory to maintain, no environment variables to set up and absolutely no other required software. Simply add the ProtoJ library to your project and get ready to experience the joy of a friction-free development cycle. So why not give ProtoJ a try right now, it really is as easy as 1-2-3: Download the ProtoJ executable jar file. Create a new "basic" project by executing java -jar protoj-exe-jdk5-1.9.2.jar -sample basic. Try a few commands from the basic/bin directory: ./basic.sh compile archive hello-basic. When you're feeling more adventurous take a look at the jboss demonstration that demonstrates how ProtoJ can be used to build, store persistent configurations and launch a jboss project with considerable ease. You may be amazed at how easy this is to accomplish: not because ProtoJ is rocket science, but because it is based on java rather than xml. Features to Enhance Any ProjectProtoJ abandons build scripts. It's "unique selling point" is that all use-cases are accessible in-code through the api, with just one call to Java in just one starter script! If you ever wished you could get rid of your build scripts then look no further: ProtoJ is targeted at you!!! ProtoJ is part of your project. You don't have to hide away use-cases related to the build inside some xml file, to be handled by some other tool merely at the start of your project life-cycle. Compilation and jar creation for example belong to your project just as much as your core business use-cases and are accessible at build-time through to run-time. ProtoJ plays nicely with maven. ProtoJ uses a traditional lib directory and support for filling it up from a maven repository is provided right out of the box. And going in the other direction, you can easily deploy your project artifacts to a maven repository so that they can be shared with other ivy or maven projects. Or indeed with other ProtoJ projects! ProtoJ plays nicely with aspectj. Aspectj compiler support can be enabled with just a single method call, as can support for load-time-weaving. Then just drop your .aj files alongside your .java files and they will be picked up by the ajc compiler without any additional aspectj installation. ProtoJ is available on all major platforms. Each release of ProtoJ is subjected to rigorous testing on Linux (Ubuntu), Unix (Mac OS X) and Windows (XP) and also on Java 5 and Java 6. If you work with any other platform then you can easily check for compatibility by following the instructions in the BuildingFromSource page. [Less]

sconfigure

SCons is a great build system. Sure, it can be a little slow for larger projects, but it really gets the job done right. My only criticism is the tragic lack of a good configuration system. SConfigure attempts to rectify this. SConfigure implements a dependency driven package configuration ... [More] system. The inspiration for this comes from BuildSystem, written mainly by Matt Knepley, which also uses a dependency graph to determine which order packages need to be configured. A project specifies which packages (MPI, libXML, OpenGL, for example) it depends on and SConfigure takes care of the rest. It searches common locations for these packages, provides default configuration options (with, without, etc.), allows the user to specify details about the package configuration (requires shared libraries, exports a preprocessor definition if found, etc.) and exports the results for later use with SCons. [Less]

QBS

Qt Build Suite (QBS) is a tool that helps simplify the build process for developing projects across multiple platforms.