wxWidgets/wxPython/distrib/all
Robin Dunn 391a2d0e2c fix email message
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@33377 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
2005-04-06 04:36:10 +00:00
..
build-all use versioned tag names for OSX too 2005-04-04 23:21:28 +00:00
build-docs Revamped automated build system to use a Python script for the master 2004-11-08 23:55:25 +00:00
build-finalize fix email message 2005-04-06 04:36:10 +00:00
build-osx Build/distrib updates 2005-02-28 18:37:29 +00:00
build-rpm Build/distrib updates 2005-02-28 18:37:29 +00:00
build-setup Revamped automated build system to use a Python script for the master 2004-11-08 23:55:25 +00:00
build-sources Revamped automated build system to use a Python script for the master 2004-11-08 23:55:25 +00:00
build-windows Some build tweaks 2005-02-24 19:50:53 +00:00
daily Add a link to the changes file, move the log file 2004-09-04 18:06:05 +00:00
do-build-osx Be able to build with Pythons other than the System version. 2005-04-02 03:46:18 +00:00
do-build-rpm Build/distrib updates 2005-02-28 18:37:29 +00:00
do-build-windows disable debugreport option 2005-03-12 21:00:19 +00:00
dryrun Some support for parallelizing builds 2004-11-05 00:48:54 +00:00
README.txt Revamped automated build system to use a Python script for the master 2004-11-08 23:55:25 +00:00
release Add a link to the changes file, move the log file 2004-09-04 18:06:05 +00:00
subprocess.py Revamped automated build system to use a Python script for the master 2004-11-08 23:55:25 +00:00
taskrunner.py return error code upon KeyboardInterrupt 2004-11-09 03:39:32 +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.