[openbeos] Re: [haiku-development] Coordinating ports (#2) (was: Re: Distributed Version Control Tools)

  • From: "Michael Lotz" <mmlr@xxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Mon, 21 Apr 2008 20:58:45 +0200

Hello Andreas

> Better than just announcing finished ports, the real way of avoiding  
> duplicated work would be to announce the beginnings of a port.

Well, better than just starting a port of QEMU, the real way would have 
been to first look around for what is already there. The BeOS port of 
QEMU is up to date (0.9.1) and maintained by me. It is available at 
http://bebits.com/app/4208, where the BONE version works without issues 
on Haiku (including the kqemu accellerator module). This is a fully 
native port, including native GUI and audio backends. I have pretty 
exact knowledge on how QEMU fits together internally and know what 
parts could profit from new Haiku provided functionality. Therefore I 
will do a native Haiku version as soon as there is a real benefit in it 
(which there currently isn't). So it really makes no sense to start a 
completely new port using the SDL GUI dependency and the extremly dated 
BeOS reference implementation in the QEMU tree.

Sorry to be so blunt about it, but it also requires some research by 
whoever starts a port prior to just downloading a tar and hacking away. 
Many applications for example exist already for BeOS and these should 
at least be used as a reference. For others there may have been porting 
attempts already. Looking through BeBits first or googling for a BeOS 
port of the application in question should IMO be the first thing to do 
before starting something like a port.

Regards
Michael

Other related posts: