How should the win16 test suite be arranged?
dank at kegel.com
Mon Jul 16 06:11:07 CDT 2007
On 7/16/07, Alexandre Julliard <julliard at winehq.org> wrote:
> I don't think there's any point in putting into the tree test cases
> what won't be built or executed. They will just bitrot. We already
> have a hard time keeping the normal test suite in a usable state.
So if I want these in the tree, they should be built and run
by default. Got it. Next question: is it acceptable to
require OpenWatcom? (That's the only free compiler I
know of that targets win16. Turbo C++ is also a free
download, but it's not open source.)
Since it's not available via apt-get install,
the easiest way to use it might be to have
'make test' install the windows version, and then use
it to compile the test cases. The download and install for the
compiler could be cached, so that part would only be slow
the first run.
Alternately, I could recode the win16 test cases in
assembly. Since the usual tools can't link win16
executables, the assembly would have to also encode
the executable headers. This would make sure the
test cases got run every time, but would make
adding new test cases hard. (Doesn't sound like
a good idea to me.)
Or would you prefer the win16 tests stay out of tree
forever? That's an option, too; people who want
to run them could download them from kegel.com or
something, and it wouldn't stop Codeweavers from
running them in cxtest.
More information about the wine-devel