Getting Autobuild

Autobuild is available as a PyPI package:

easy_install autobuild

or

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

Note: Windows' users need to create an environment variable to tell autobuild it should use VC 2010, as otherwise it will default to VC 2003. Find a "My Computer" icon, there are several ways to do this which vary depending on which version of Windows you are using. Usually you can find one through the "Start" menu button. Right-click the icon and select "Properties". When the Properties dialogue opens, click the "Advanced" tab followed by the "Environmental Variables" button. This will open a new dialogue with a list of System and User variables. In the User section, click "New". Your "Variable Name" should be AUTOBUILD_VSVER and the "Variable Value" is 100. Once you have done that, click the OK/Close buttons to clear the dialogues.

Note: On Windows there is no need to perform this install step. Stop here and resume following the Windows build instructions. python setup.py install 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.

Note: If you are using Cygwin on Windows, you must also add your Python scripts directory (for example C:/Program Files/python27/Scripts) to your PATH. If you have further problems, please see Autobuild/Cygwin

Tip: 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 virtualenv, e.g.: mkdir ~/virtualenvs # or any directory for your Python-package environments VENV=~/virtualenvs/autobuild virtualenv "$VENV" . "$VENV/bin/activate" Then your pip install autobuild command will install autobuild under $VENV instead of into system directories. (Note that this pip install 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.)