Call for win16 tests
markus.amsler at oribi.org
Mon Jul 9 21:59:56 CDT 2007
Dan Kegel wrote:
> On 7/9/07, Markus Amsler <markus.amsler at oribi.org> wrote:
>> We have to distinguish between win16 and dos tests.
> Absolutely. dos .com executables currently don't work,
> but win16 .exe's with the same contents do work.
> I plan to test DOS .com files using very simple pure assembly.
> (That was the real way to write DOS programs anyway :-)
>> IMO it should be possible to run them with make test like
>> any other test. And if openwatcom/turbo c is available it should be
>> possilbe to run make crosstest to build win16/dos binaries.
>> For dos I had a test (I think I really have lost it) which compiled on
>> linux with gcc and in dos6.2 with turbo C. In linux/wine it emulated an
>> interrupt with DOSVM_EmulateInterruptPM, and in dos it used real
>> interrupts. I'm not sure whether this approach would be acceptable, but
>> I was able to run make test and build dos binaries from the same
> Sounds like too much magic for me. I would rather simply
> require openwatcom; it's free software.
License fun. It's OSI approved, but it looks it isn't good enough even
for debian non-free
>> For win16 I have no idea what thunking/linking voodoo is required.
> No voodoo required; openwatcom Just Works.
You're right it's a lot simpler. Perhaps we should check for win16
compiler in configure, so if openwatcom is present make test builds/runs
also the win16/dos tests.
>> Its perhaps also noteworthy that wines win16 implementation differs
>> fundamentally from the windows one. Wine calls win32 functions, while
>> windows calls dos functions (directly or via vdm).
> Shouldn't affect our tests, though, should it?
I don't think so.
More information about the wine-devel