Difference between revisions of "Autobuild/Cygwin"
Jump to navigation
Jump to search
Brad Linden (talk | contribs) |
Brad Linden (talk | contribs) m (typo) |
||
| Line 5: | Line 5: | ||
If you want to run autobuild directly from a mercurial checkout without installing, we still provide the autobuild.cmd wrapper. It can be used by executing the following: | If you want to run autobuild directly from a mercurial checkout without installing, we still provide the autobuild.cmd wrapper. It can be used by executing the following: | ||
ln -s /path/to/autobuild/checkout/bin/autobuild.cmd ~/bin/autobuild | ln -s /path/to/autobuild/checkout/bin/autobuild.cmd ~/bin/autobuild | ||
export PATH="$PATH:~/bin/ | export PATH="$PATH:~/bin/" | ||
However, as this is trickier to set up and more error prone, it is not the primary method that we recommend in [[Autobuild#Getting_Autobuild]]. | However, as this is trickier to set up and more error prone, it is not the primary method that we recommend in [[Autobuild#Getting_Autobuild]]. | ||
Revision as of 15:54, 31 March 2011
Previously, Windows users with a "native" Python install were advised to avoid the Cygwin shell like the plague.
However, things should be better now. We are now using the distribute extension of the python setuptools, so the autobuild application installed should now be equally executable by any shell.
If you want to run autobuild directly from a mercurial checkout without installing, we still provide the autobuild.cmd wrapper. It can be used by executing the following:
ln -s /path/to/autobuild/checkout/bin/autobuild.cmd ~/bin/autobuild export PATH="$PATH:~/bin/"
However, as this is trickier to set up and more error prone, it is not the primary method that we recommend in Autobuild#Getting_Autobuild.