What is Autoproj
----------------
Autoproj allows to easily install and maintain software that is under source
code form (usually from a version control system). It has been designed to support a
package-oriented development process, where each package can have its own
version control repository (think "distributed version control"). It also
provides an easy integration of the local operating system (Debian, Ubuntu,
Fedora, maybe MacOSX at some point).

This tool has been developped in the frame of the RubyInMotion project
(http://sites.google.com/site/rubyinmotion), to install robotics-related
software -- that is often bleeding edge. Unlike [the ROS build
system](http://ros.org), it is not bound to one build system, one VCS and one
integration framework. The philosophy behind autoproj
is:
 * supports both CMake and autotools, and can be adapted to other tools
 * supports different VCS: cvs, svn, git, plain tarballs.
 * software packages are plain packages, meaning that they can be built and
   installed /outside/ an autoproj tree, and are not tied *at all* to the
   autoproj build system.
 * leverage the actual OS package management system. Right now, only Debian-like
   systems (like Ubuntu) are supported, simply because it is the only one I have
   access to.
 * handle code generation properly

It tries as much as possible to follow the lead of Willow Garage on the package
specification. More specifically, the package manifest files are common between
ROS package management and autoproj (more details in the following of this
document).

Overview of an autoproj installation
-------------------------------------

The idea in an autoproj installation is that people share _definitions_ for a
set of packages that can depend on each other. Then, anyone can cherry-pick in
these definitions to build its own installation (in practice, one builds a
complete configuration per-project).

Each package definition includes:

 * how to get the package's source code
 * how to build the package
 * on what the package depends. This can be either another package built by
   autoproj, or an operating system package.

See [this page](structure.html) for more information.

Bootstrapping
-------------
"Bootstrapping" means getting autoproj itself before it can work its magic ...
The canonical way is the following:

 * install Ruby by yourself. On Debian or Ubuntu, this is done with
   done with

   sudo apt-get install wget ruby
   {.cmdline}

 * then, [download this script](autoproj_bootstrap) *in the directory where
   you want to create an autoproj installation*, and run it. This can be done with

   wget http://doudou.github.com/autoproj/autoproj\_bootstrap <br />
   ruby autoproj\_bootstrap
   {.cmdline}

 * follow the instructions printed by the script<tt>manifest</tt>.

Additionally, if you are given a reference to a source code repository in which
an autoproj configuration is stored (i.e. a directory in which a manifest is
present), you can bootstrap this configuration directly:

   wget http://doudou.github.com/autoproj/autoproj\_bootstrap <br />
   ruby autoproj\_bootstrap VCS 
   {.cmdline}

For instance, to build all packages made available by the RubyInMotion project,
do

   wget http://doudou.github.com/autoproj/autoproj\_bootstrap <br />
   ruby autoproj\_bootstrap git git://github.com/doudou/rubim.all.git
   {.cmdline}

Additional options can be given for the version control system. For instance,

   wget http://doudou.github.com/autoproj/autoproj\_bootstrap <br />
   ruby autoproj\_bootstrap git git://github.com/doudou/rubim.all.git branch=stable
   {.cmdline}

Software packages in Autoproj
-----------------------------
In the realm of autoproj, a software package should be a self-contained build
system, that could be built outside of an autoproj tree. In practice, it means
that the package writer should leverage its build system (for instance, cmake)
to discover if the package dependencies are installed, and what are the
appropriate build options that should be given (for instance, include
directories or library names).

As a guideline, we recommend that inter-package dependencies are managed by
using pkg-config.

To describe the package, and more importantly to setup cross-package
dependencies, [an optional manifest file can be
added](package_sets/manifest-xml.html).