Difference between revisions of "Getting Autobuild"

From Second Life Wiki
Jump to: navigation, search
(added link to correct instructions on setting up in windows)
(Deleted all the incorrect information about autobuild on windows)
Line 6: Line 6:
  
 
For setting up Visual Studio to use Autobuild, see [[Viewer_2_Microsoft_Windows_Builds#Install_Autobuild]]
 
For setting up Visual Studio to use Autobuild, see [[Viewer_2_Microsoft_Windows_Builds#Install_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|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.}}
 
 
{{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 -->
 

Revision as of 07:29, 30 June 2011

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://hg.secondlife.com/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