Linked by Thom Holwerda on Thu 22nd Aug 2013 21:00 UTC
BeOS & Derivatives

Although I have been a lazy blogger lately we haven't been lazy working on our remaining tasks at all. So, unsurprisingly, since my previous post we have reached and passed a few nice milestones. The latest one is that we're finally able to build the gcc2/gcc4 hybrid Haiku images again, including all the software needed for the official release.

While that in itself isn't a particularly impressive feat - after all we were already able to build the complete gcc 2 part before - the interesting aspect is how we are doing it.

Interesting progress for Haiku.

Thread beginning with comment 570346
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by v_bobok
by drcouzelis on Thu 22nd Aug 2013 22:23 UTC in reply to "Comment by v_bobok"
drcouzelis
Member since:
2010-01-11

At last.

:) I really think Haiku development will explode when package management is done / refined. Users and developers will finally be able to update the OS to the latest nightly build and install packages with just a few quick clicks.

Next big hurdle: Should the backend of the native API be replaced with Qt? (For those not following, yes, that is a serious consideration!) ;)

Reply Parent Score: 5

RE[2]: Comment by v_bobok
by Luke McCarthy on Thu 22nd Aug 2013 23:46 in reply to "RE: Comment by v_bobok"
Luke McCarthy Member since:
2005-07-06

That might be a good idea for the long term. Nobody is going to port applications to the Be API, as nice as it is, but there are many Qt apps and it is probably the dominant cross-platform API.

Reply Parent Score: 5

RE[2]: Comment by v_bobok
by testadura on Fri 23rd Aug 2013 08:21 in reply to "RE: Comment by v_bobok"
testadura Member since:
2006-04-14

Sounds like a neat plan. Although I cannot exactly imagine how this will materialize. How will this differ from running QT apps in a QT runtime? Or will Haiku be the QT runtime itself?
Does a QT application have access to Haiku specific API's like messaging/translators/etc? If so, you loose the benefit somewhat, since an application is not cross platform anymore and QT Haiku development still needs customization.

Edited 2013-08-23 08:38 UTC

Reply Parent Score: 1

RE[3]: Comment by v_bobok
by drcouzelis on Fri 23rd Aug 2013 14:19 in reply to "RE[2]: Comment by v_bobok"
drcouzelis Member since:
2010-01-11
RE[2]: Comment by v_bobok
by andrewclunn on Fri 23rd Aug 2013 12:32 in reply to "RE: Comment by v_bobok"
andrewclunn Member since:
2012-11-05

Version 1 to support old Be apps of course. After that, hell yes to a Qt backend!

Reply Parent Score: 2