There are several issue flying around here.
1) Jonathan Dickenson: We've been talking about automated unit tests using
serial output since before il2cpu was a twinkle in Chad Hower's eye. We're
just coming to the point where we are admitting that QEmu will help us pull
that off, since it would be a standard assumption about the development
environment.
2) I am usually completely against including barely-related stuff in our
repo. I don't like having the Mono corlib source in there, but since it will
be a core part of our OS, we have to be able to have a compiled copy at some
point.
3) I am mostly against including QEmu in our trunk. I think its a cheap
cop-out of not us not supporting ISO (but I'm not one to talk because I
don't have time to work on ISO, so I have to concede this point.)
4) We need automated unit testing. We need automated communication, *in
general*, between our development environment and our testbed environment.
If PC virtualization wasn't widespread, we'd probably be resorting to
something else like network or serial boot. (Which is an interesting
thought, because the set of PC emulators might support that...) But
regardless - it would be part of our trunk code set - so QEmu is a logical
component of such, in today's world.
So I vote *yes* for QEmu, out of neccessity, despite principle - on the
condition that as we develop a better solution (we have to support ISO stuff
at some point over the next 9 months), we take QEmu back out of the trunk
and work out a new solution.
So thats 4 board members saying yes, in what amounts to a unanimous board
vote. Anyone else with thoughts should speak up quickly, rationally - and
politely! - lest it be done without your utterings having been heard.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
