Difference between revisions of "Autobuild"

From Second Life Wiki

Latest revision as of 10:21, 29 September 2022

Autobuild

Autobuild is a framework for building packages and for managing the dependencies of a package on other packages. It provides a common interface to configuring and building any package, 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.

Linden Lab Autobuild is not the same as or derived from GNU Autobuild, but they are similar enough to cause confusion. We regret this error.

Getting Autobuild

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

You should use Python 3.7+ for autobuild 3.x.

To install with the appropriate python package dependencies, use a tool such as pip or pipx:

pip install autobuild

depending on how your permissions are defined and whether or not you are working within a python virtualenv, you may need to adjust your system PATH.

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
--verbose	Display verbose output. Useful in diagnosing errors in your configuration.
--dry-run	Run tool in dry run mode. This mode will print information about what would have been done. It is supported for most subcommands.
--help [command]	Find all valid Autobuild tools and show help
--quiet	Display minimal output
-V, --version	Show version information for autobuild
--debug	Display debug information; very very verbose, probably of interest only if you are modifying autobuild itself

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.

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.
- Testing procedures for patch submissions are documented here: Autobuild/Integration

Retrieved from "https://wiki.secondlife.com/w/index.php?title=Autobuild&oldid=1212492"

Categories:

@@ Line 1: / Line 1: @@
 {{Autobuild Nav}}
+__NOTOC__
-== Overview ==
+Autobuild is a framework for building packages and for managing the dependencies of a package on other packages. It provides a common interface to configuring and building any package, 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.
-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.
-{{KBcaution|Linden Lab Autobuild is not the same as or derived from [http://josefsson.org/autobuild/ GNU Autobuild], but they are similar enough to cause confusion.}}
-For Linden old hands: Autobuild is designed as a replacement for the old [https://svn.lindenlab.com/svn/lindenlib/trunk lindenlib] policies; doing the right thing so you don't have to.
+__TOC__
+'''Linden Lab Autobuild is not the same as or derived from [http://josefsson.org/autobuild/ GNU Autobuild], but they are similar enough to cause confusion. We regret this error.'''
 == Getting Autobuild ==
-Autobuild is available as a Mercurial repository:
+Autobuild is under active development, so it's recommended that you get the latest version and keep it up to date.
- https://bitbucket.org/lindenlab/autobuild
-=== Installing Autobuild ===
+You should use Python 3.7+ for autobuild 3.x.
-You can either run the autobuild command directly from the "bin" directory in a working copy of that repository, or install it as a normal python package by running
+To install with the appropriate python package dependencies, use a tool such as pip or [https://pypa.github.io/pipx/ pipx]:
-  python setup.py install
+  pip install autobuild
-from the top level directory of the working copy.  You may need administrative privilege on your system to install into system command directories.
+depending on how your permissions are defined and whether or not you
-{{KBwarning| Windows users with a "native" Python install, should add the Autobuild "bin" directory to their PATH and avoid the Cygwin shell like the plague ;-) }}
+are working within a [http://docs.python-guide.org/en/latest/dev/virtualenvs/ python virtualenv],
-{{KBnote|If you are using Cygwin on Windows, use <code>python setup.py install</code> rather than running Autobuild directly from the checkout.  This ensures that Cygwin paths are translated to native Windows paths.  You must also add your Python scripts directory (for example <code>C:/Program Files/python26/Scripts</code>) to your PATH.}}
+you may need to adjust your system <tt>PATH</tt>.
-{{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 alternatively use [http://www.virtualenv.org/en/latest/index.html virtualenv] and [http://www.pip-installer.org/en/latest/ pip], e.g.:
+== Running Autobuild ==
- mkdir ~/virtualenvs  # or any directory for your Python-package environments
- VENV{{=}}~/virtualenvs/autobuild
- virtualenv "$VENV"
- . "$VENV/bin/activate"
-Then your <code>pip install</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.)
+=== Building the Viewer ===
- pip install -e "hg+http://hg.secondlife.com/autobuild/#egg{{=}}autobuild"
+See [[Building the Viewer with Autobuild]]
- which autobuild
-}} <!-- end pip/virtualenv tip -->
-== Running Autobuild ==
+=== Changing or Adding Build Configuration Details ===
 Usage:
 {{Syntax|autobuild ''options'' ''sub-command''
@@ Line 49: / Line 43: @@
 |--
-| --debug
+| --verbose
-| Display debug information
+| Display verbose output. Useful in diagnosing errors in your configuration.
 |--
 | --dry-run
-| Run tool in dry run mode if available
+| Run tool in dry run mode.  ''This mode will print information about what would have been done. It is supported for most subcommands.''
 |--
@@ Line 65: / Line 59: @@
 |--
-| --verbose
+| -V, --version
-| Display verbose output
+| Show version information for autobuild
 |--
-| -V, --version
+| --debug
-| Show version information
+| Display debug information; very very verbose, probably of interest only if you are modifying autobuild itself
 |}
@@ Line 109: / Line 103: @@
 | [[autobuild uninstall|uninstall]]
 | Uninstall package archives.
-|--
-| [[autobuild upload|upload]]
-| Upload tool for autobuild
 |}
@@ Line 139: / Line 130: @@
 * Discussion of and help with Autobuild are available on the [https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev opensource-dev mailing list] and the [irc://irc.freenode.org/%23opensl #opensl channel on the freenode.org IRC network].
 * Bug reports and feature suggestions are tracked in the [https://jira.secondlife.com/browse/OPEN Open Development project on jira.secondlife.com].
-** Suggested patches for issues from the jira are reviewed on our [https://codereview.secondlife.com code review system] (see [[Code Review Tool|the documentation on how to use it]]).
+** Testing procedures for patch submissions are documented here: [[Autobuild/Integration]]
 [[Category:Autobuild]] [[Category:Open Source Portal]]