Haiku Activity & Contract Report, April 2026 | Haiku Project

This report covers hrev59570 through hrev59671.

GSoC selection happened at the end of last month; you can read the news post announcing this year’s selectees. Thanks to everyone who applied!


This is a companion discussion topic for the original entry at https://www.haiku-os.org/blog/waddlesplash/2026-05-11-haiku_activity_contract_report_april_2026
23 Likes

It seems a lot of cleanup and improvement has been done, thanks for making haiku better to everyone involved

1 Like

Not yet. A WebPositive release is pending, and there are a few other bugs in Haiku that need to be fixed, too.

The WebPositive release has been tagged and is ready. However, Haikuports buildbots failed to download the archive from Codeberg.

And we need a beta6 builder (with the new memory allocator) if we want to have a chance of a succesful 32 bit build, too.

4 Likes

That sounds pretty soonish …

Looking forward to it

1 Like

Yes, because Codeberg chokes on generating such large archives. It sounds like @nephele discovered the WebKit script to make small release tarballs, so that should hopefully avoid the problem?

I personally tested the recipe before pushing the changes, and the download went fine.

Unlike Github where this didn’t work at all.

As far as I know, the script is used by WebKitGTK and will require changes for Haiku support, so it’s not an option at the moment. I can generate archives with “git export” as I did before, but according to Codeberg people, everything should work already. Maybe it was just a temporary problem the day I made the release, or maybe we can show them our problem more closely (by opening a ticket there) and getting it fixed (isn’t it nice to work with a tool that cares about us and will provide support?)

4 Likes

Yes, I do have the script, it basically is just an ordered list of instructions on how to copy which files into the archive. This does need some adjustments to work properly for us (we need to include all files our build needs)

I’ve not finished that yet, though I can provide my WIP work if someone else wants to have a go at it.

With the progress on Haiku ARM64, is there a particular hardware platform that will be targeted? Raspberry Pi for example?

It would also make a lot of sense if Qualcomm ARM winbooks are targeted as well. I figure the platform differences will be less than Chromebooks.

2 Likes

Ahoy @The123king ,

Well, @smrobtzz who actively works and release patches to the Haiku source tree

to IMPROVE ARM64 port
reported in the introductory post to target an Apple M1 MacBook Air

Besides this visible progress,

there were an announcement and a promising presentation in a VM from another forum member - @dodo75 - who named its ARM64 port target in Raspberry PI500+, a keyboard computer variant of RPI5 !

However there’s no more progress info about that port attempt since 30th of March ,
where it was promised that results - to that day - will be shared after Easter

So, in a nutshell, Haiku for ARM64 highly anticipated for both ARM64 world

Apple M* chips built machines with running originally macOS
and
SBCs, tablets and similar gadgets which now have ARM64 CPUs,

and usually run Linux distros or even some level of Android OS on them.

Ahoy devs and contributors !

Thank you for your reshaping, continous business and care !..

May you be filled with joy in the end results, and may it bear fruit in valuable lessons for those who are still learning all this.

We are very close to Beta 6!?

2 bugs are still open!

Who is working on them, and when will the Beta 6 happen?

Glad to hear you are close to R1Beta6! Cannot wait to play with it as my daily drtiver…thanks to all who will make this happen!!