From: Bernhard Held <bernhard@be...> - 2003-02-09 17:59:46
It's high time to inform you about the nightly builds.
First of all I apologize about the noise I was and I will generate with the
nightly builds. Thank you for your patience. But most of the work (and with
it the potential errors) is done.
For the people, who have never seen the nightly builds: Sourceforge (SF)
supplies a great compile farm, and Michael Hope supplied a great framework to
run the nightly build and the regression tests. This framework is in CVS, the
module is sdcc-build.
The stripped down output of the builds is sent to sdcc-devel, the raw output
is available through the list sdcc-buildlogs.
My job was to supply a mingw32 cross compiler, because SF uninstalled it some
time ago. Furthermore I've hired a new virtual developer: "sdcc-builder". I
installed everything (cross compiler, cvs/ssh keys, cronjobs) on this
I share the password for this account with every sdcc-developer. I really
hope, that there will be some interest from your side, so that not everything
depends on one single person.
Finally I didn't integrate the Makefile.doc for building the docs into
sdcc-build. It's easier for me to handle this in a separat Makefile. It's
still a mess to build the docs on SF, and the docs should be built much more
often than the snapshots. At the moment the docs are rebuilt each hour (!),
if something changes in CVS.
Makefile.doc is doing following:
- checkout sdcc/doc and sim/ucsim/doc (aslink will come soon, I simply forgot
- build pdf and html files if necessary
- copy built files to http://sdcc.sf.net/doc/
- pack two archives and move it to http://sdcc.sf.net/snapshots/docs/
Still to do:
- include aslink doc's
- clarify further handling of docs (separate posting) and implement it
- build sdcc.src.tar.gz and sdcc-src.zip with sdcc-build
- write some documentation for Makefile.doc and what's happening on