Intro
Tutorials
Core
- Base Types
- Build System
- Bootstrapping
- Basic Usage
- Customizing the Installation
- Adding Packages
- The Manifest File
- Understanding Autoproj Error Messages
- The osdeps system
- Advanced Usage
- Tooling with Shell Scripts
- The manifest.xml File
- Creating a Package Set
- Writing Autobuild Scripts
- Writing Package Handlers
- Package Import
- Package Dependencies
- Cross-Set Dependencies
- osdeps - Operating System Dependencies
- Supporting new OSes
- Autoproj API
- Autobuild API
- Developing Components
- Running Components
- System Management
- Data Analysis
- Graphical User Interface
- Simulating a Robot
Additional Core Functionality
The manifest.xml File
The manifest.xml is an optional (but very recommended) file that lies in the root of every source package. This file describes both what the package is (i.e. short description, contact information), and dependency information (what should be installed for that package to be built successfully).
The general form of the file is:
<package>
<description brief="one line of text">
long description goes here,
<em>XHTML is allowed</em>
</description>
<author>Alice/alice@somewhere.bar, Bob/bob@nowhere.foo</author>
<license>BSD</license>
<url>http://sites.google.com/site/rubyinmotion</url>
<logo>http://sites.google.com/site/rubyinmotion</logo>
<!-- add dependency to another autoproj-built
package -->
<depend package="pkgname"/>
<depend package="common"/>
<!-- add dependency to an OS-provided package -->
<rosdep name="os-pkgname" />
</package>