Difference between revisions of "Autobuild"

Autobuild

Overview

Autobuild is a framework for maintaining and building libraries. It acts as director providing a common interface to build and package libraries, but it is not a build system like make or cmake. You will still need platform-specific make, cmake, or project files to configure and build your library. Autobuild will, however, allow you invoke these commands and package the product with a common interface.

Important: Linden Lab Autobuild is not the same as or derived from GNU Autobuild, but they are similar enough to cause confusion.

For Linden old hands: Autobuild is designed as a replacement for the old lindenlib policies; doing the right thing so you don't have to.

Getting Autobuild

Deletion Requested
The deletion of this article was requested for the following reason: This page is out of date, orphaned, and replaced by Autobuild
If there is a need to discuss the deletion of this article, please add your comment(s) here.

Autobuild is under active development, so it's recommended that you get the latest version and keep it up to date:

CD to where you want to install autobuild. Do not have any spaces in the path to this directory.
Do:

hg clone http://bitbucket.org/lindenlab/autobuild

Modify your path statement to include the autobuild \bin directory

For setting up Visual Studio to use Autobuild, see Viewer_2_Microsoft_Windows_Builds#Install_Autobuild

Running Autobuild

Building the Viewer

See: Building the Viewer with Autobuild

Changing or Adding Build Configuration Details

Usage:

autobuild options sub-command

Supply zero or more options, and one sub-command.

Options:

Option	Description
--debug	Display debug information
--dry-run	Run tool in dry run mode if available
--help [command]	Find all valid Autobuild tools and show help
--quiet	Display minimal output
--verbose	Display verbose output
-V, --version	Show version information

Sub-commands

Sub-command	Description
build	Build platform targets.
configure	Configure platform targets.
edit	Manage build and package configuration.
install	Fetch and install package archives.
installables	Manipulate installable package entries in the autobuild configuration.
manifest	Manipulate manifest entries to the autobuild configuration.
package	Create an archive of build output.
print	Print configuration.
source_environment	Print the shell environment Autobuild-based build scripts to use (by calling 'eval').
uninstall	Uninstall package archives.
upload	Upload tool for autobuild

Background and Tutorials

Autobuild How To: A tutorial introduction to using autobuild
Autobuild Lexicon: A list of terms and how they are used in the context of autobuild
Autobuild Package Layout: Describes the standard directory tree for packages managed with autobuild
Autobuild Quick Start: A basic walkthrough of how to add autobuild management to an existing software project
Autobuild Class Model: Describes the fundamental objects in the autobuild design and the relationships between them.
Autobuild Examples: Links to packages built with autobuild.
Build Script Anatomy: An annotated build script typical of those used to build third party libraries.
Autobuild Shell Functions: A description of all shell functions provided by Autobuild for use in build scripts.

Contributing to Autobuild

Autobuild is open source. Improvements are most welcome.

Discussion of and help with Autobuild are available on the opensource-dev mailing list and the #opensl channel on the freenode.org IRC network.
Bug reports and feature suggestions are tracked in the Open Development project on jira.secondlife.com.
- Suggested patches for issues from the jira are reviewed on our code review system (see the documentation on how to use it).
- Testing procedures for patch submissions are documented here: Autobuild/Integration

@@ Line 10: / Line 10: @@
 == Getting Autobuild ==
-Autobuild is available as a PyPI package:
+{{:Getting Autobuild}}
- [http://pypi.python.org/pypi/setuptools easy_install] autobuild
-or
- [http://pypi.python.org/pypi/pip pip] install autobuild
-of if you don't have pip or easy_install
- hg clone http://hg.secondlife.com/autobuild
- cd autobuild
- python setup.py install
-{{KBnote| On Windows there is no need to perform this install step.  Stop here and resume following the Windows build instructions. <code>python setup.py install</code> does not work correctly. You will need to edit/rename some files to make it work!  See [[Autobuild/Cygwin]] for an alternative.}}
-You may need administrative privilege on your system to install into system command directories.
-{{KBnote|If you are using Cygwin on Windows, you must also add your Python scripts directory (for example <code>C:/Program Files/python27/Scripts</code>) to your PATH. If you have further problems, please see [[Autobuild/Cygwin]]}}
-{{KBtip|If you do not have administrative privilege on your system, or for any reason you wish to avoid adding autobuild into system-level Python or command directories, you can use [http://www.virtualenv.org/en/latest/index.html virtualenv], e.g.:
- mkdir ~/virtualenvs  # or any directory for your Python-package environments
- VENV{{=}}~/virtualenvs/autobuild
- virtualenv "$VENV"
- . "$VENV/bin/activate"
-Then your <code>pip install autobuild</code> command will install autobuild under <code>$VENV</code> instead of into system directories. (Note that this <code>pip install</code> command will work either way. If you have an active virtualenv, it will install into the virtualenv; if not it will attempt to install into system directories.)
-}} <!-- end pip/virtualenv tip -->
 == Running Autobuild ==

Difference between revisions of "Autobuild"

Revision as of 09:30, 2 June 2011

Contents