Re: [AD] Porting Allegro to Haiku

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


On Friday 22 August 2008, scott mc wrote:
> I've been looking over the Allegro 4.3.x and 4.9.x source and it appears
> that the BeOS stuff has been dropped from the 4.9.x branch.  I do porting
> work for HaikuPorts: http://ports.haiku-files.org/ and am planning to start
> working on porting the 4.3.x branch over.  Haiku is the open source
> recreation of BeOS.  It is nearing it's first alpha release, which will
> probably happen before the end of 2008.  For many of the ports we've done
> so far we've found that we've have to undo many of the BeOS workarounds, as
> Haiku is more POSIX compliant than BeOS was.  But in the cases where there
> was prior BeOS gui code that has for the most part just worked.  It seems
> that the BeOS gui code was part of what was dropped in the move to 4.9. 
> How much has changed between the 4.3.x branch and the 4.9.x branch in
> regards to the gui?  Would porting the 4.3.x branch to Haiku only then be
> lost once Allegro 5.0 comes out, or could the 4.3.x Haiku port code be
> brought forward?  Just asking before I go to far into this.
> -Scott McCreary
> (scottmc)

Allegro 4.9/5 is significantly different from Allegro 4.x. The BeOS code was 
removed because there was no one working on porting it (or rewriting it) for 
Allegro 5's new system.

Note though that even once Allegro 5 is released, Allegro 4 won't be dropped 
(right away). Allegro 4 will continue to live on as Allegro 4.4 once the 4.3 
wip series is completed. So a port to Haiku for 4.3 wouldn't entirely be in 
vain. But a new 5.0 port would probably be more useful.

-- 
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/