Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revamped automated build system to use a Python script for the master

Browse Source 
control script, make parallel builds the only way to do it
(facilitated by the taskrunner module) split out the guts of build-all
into separate scripts, etc.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@30377 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2004-11-08 23:55:25 +00:00
parent 17dc7ddd7c
commit e4bb599887
14 changed files with 2144 additions and 646 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
wxPython/distrib/all/README.txt
View File

@@ -1,8 +1,8 @@
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 shared folders
on network drives, and ssh commands to the remote machines. So this
will likly only work in my somewhat unique environment.
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
@@ -12,7 +12,7 @@ may be copied to a public server for others to play with.
Types of builds:
dry-run
dryrun
Nothing extra is done with the build, this is just for
my own testing.
@@ -21,14 +21,17 @@ Types of builds:
datestamp, and if the build is successful the results
are copied to a daily build folder on starship.
release-cantidate
release
The results are uploaded to the previews foler on
starship if the build is successful.
The master script in this folder is "make-all" which will setup and
control the whole process. The other scripts are what are run on each
build machine, most of which will also call out to other scripts that
already exist, etc.
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.