#126 batch build Bochs with different options
Sometimes code changes break certain compile options or
introduces bugs. Depending on how often that part of
the code gets used, the broken code can go a long time
before it is noticed. For example, in the Bochs 1.3
you could not compile with SMP and the debugger, until
a minor bug was fixed. This was not discovered until
almost time for the 1.4 release.
Especially at release time, it would be good to verify
that Bochs compiles with a large variety of compile
options. I'm imagining some kind of batch build script
that does a series of compiles with different options.
It could simply test that a binary is created with no
errors, or copy the binary so that we have a collection
of compiled binaries with different switches.
Another variable could be cvs checkout options such as
a CVS tag, a date, etc. At times, I've wished I could
easily make a bochs binary from each day in a range of
dates, to help figure out when a bug was introduced.
Personally, my first try would be a perl script that
reads some kind of configuration file telling it which
bochses to build. It could even start the builds in
parallel (if that actually helped). Other people might
prefer some other approach that is more familiar to
them.
Logged In: YES
user_id=185114
I added build/batch-build.perl this week. It sets up a
whole bunch of VPATH builds using the same source code,
which is very useful for testing new code for problems in
different environments.
There's nothing in there about doing a new checkout with a
different cvs tag. That could be handy at times, for
example doing a compile of cvs from every day in a range of
dates, to find when a certain bug was introduced.
Anyway, for now it's quite useful so I'll close this item.