wxWidgets/wxPython/distrib/all
2006-11-06 20:50:25 +00:00
..
build-all build tweaks, also drop most Python 2.3 builds 2006-09-25 20:24:42 +00:00
build-docs Build and distrib tweaks ported over from the 2.6 branch 2006-07-05 05:23:28 +00:00
build-environ.cfg upload to wxpython.wxcommunity.com instead of starship 2006-11-06 20:50:25 +00:00
build-finalize upload to wxpython.wxcommunity.com instead of starship 2006-11-06 20:50:25 +00:00
build-osx enable building just the unicode version, or both unicode and ansi 2006-07-13 02:40:46 +00:00
build-rpm enable building just the unicode version, or both unicode and ansi 2006-07-13 02:40:46 +00:00
build-setup Build and distrib tweaks ported over from the 2.6 branch 2006-07-05 05:23:28 +00:00
build-sources Build and distrib tweaks ported over from the 2.6 branch 2006-07-05 05:23:28 +00:00
build-windows enable building just the unicode version, or both unicode and ansi 2006-07-13 02:40:46 +00:00
daily
do-build-osx enable building just the unicode version, or both unicode and ansi 2006-07-13 02:40:46 +00:00
do-build-rpm enable building just the unicode version, or both unicode and ansi 2006-07-13 02:40:46 +00:00
do-build-windows Fixed some (out) typemaps 2006-10-26 15:22:43 +00:00
dryrun
README.txt
release
subprocess.py
taskrunner.py Adding TaskRunnerThread class, for threaded operations, along with errorOccurred and elapsedTime methods for getting information about a process. 2006-09-02 22:00:06 +00:00
tr_setup.py renamed setup.py to tr_setup.py because build-all does an import of 2006-07-05 05:25:25 +00:00

The collection of scripts in this directory are an attempt to fully
automate the build of the wxPython source and binary packages on all
build platforms.  It does this through creative use of ssh and scp
commands to the remote build machines, so this will likely only work
in my somewhat unique environment.

The goal here is to be able to start a build on one machine and have
it take care of all the steps, including moving the source tarball to
the other build machines, initiating the build there, and collecting
the results.  Depending on the type of build, (see below) the results
may be copied to a public server for others to play with.

Types of builds:

      dryrun
		Nothing extra is done with the build, this is just for
		my own testing.  

      daily 
		The version number is temporarily adjusted to include a
		datestamp, and if the build is successful the results
		are copied to a daily build folder on starship.

      release
		The results are uploaded to the previews foler on
		starship if the build is successful.


The master script in this folder is build-all (written in Python)
which will setup and control the whole process.  The other scripts
(using bash) are launched from build-all either to do specific tasks
locally, or to run on each individual build machine to manage the
build process there, usually by calling out to other scripts that
already exist.  The build-all script uses the taskrunner.py and
subprocess Python modules.