What's New in Haiku development
The Haiku source is continually built and released for testing purposes nearly every day. You can download and install these latest snapshots to check out the latest features and bug-fixes.
Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.
If you're OK with this, you can find further instructions at our Nightly image page.
Hello everyone, apparently we made it to 2021! This year we will see the 20th anniversary of Haiku.
This report covers hrev54806-hrev54947.
Architectures, ports, bootloaders PulkoMandy fixed the build of the openfirmware bootloader for PowerPC. It had been broken by changes for SPARC support. The openfirmware code to set up the splash screen was also fixed to work on sparc.
tqh continues his work on cleaning and simplifying our EFI support.
Debugging early bootloader code can be extremely difficult. The lack of printf and other classical black-box debugging tools means you’re limited to one of the following methods of debugging lockups:
Arm chair debugging, Changing code, compiling, booting, repeat. Using GDB or another debugger tool and stepping through code watching outcome. Obviously #2 above is more ideal than #1. Welcome to debugging by attaching gdb to qemu!
The steps below really should apply to any architecture.
Hi there, I’m jt15s, a new Haiku community member! I’ve been following the project for a few years now since I stumbled upon an article about Haiku.
If you read the title (which I’m assuming you did), you’re probably going, “wait, we have a promotion team?” Well, yes, now we do. As an informal “team” of two (currently), we are super excited to share our plans to help promote Haiku and make more people aware of it.
Welcome to the November-December activity report!
This report covers hrev54716-hrev54805 (about 5 weeks of work).
Code cleanup mt fixed various warnings, use-after-free, memory leaks, and dead code problems detected by the clang static analyzer.
X512 reworked app_server memory management to use owning pointers and avoid some memory leaks and use-after-free cases. This led to a rework of the classes used for that purpose, in particular AutoDeleter and its variants, to be more efficient and more flexible.
Contest for Haiku System Sounds is finally over; and ladies and gentlemen, we have a winner!
Before going into details, lots of thanks to all participants and voters are in order. Thanks to you, Haiku now has a cohesive high-quality sound set, that will hopefully make using Haiku even more pleasant and accessible.
Without further ado, the winner is Garrett Kabler, with the sound theme “grubs-sparkly-tones” (previously named as “burgs-sparkly-tones”, name changed by the author due to a possible identity mixup)!
HaikuDepot displays icons through a number of areas of its user interface. Early in the history of the Haiku packaging system, there were very few packages and very few icons. HaikuDepot started off by downloading each individually from HaikuDepotServer.
Download as Tar then Unpack Downloading each icon file individually was fine for a while, but as the package and hence icon count grew it became necessary to rework this system. HaikuDepotServer later provided the icons as a compressed tar-ball containing all of the icons.
Welcome to the October activity report!
I had managed to get other people to write the report for a few months, but not for October, apparently. So, I’m back!
This report covers hrev54609-hrev54715 (about a month and a half work).
The focus is not much on new and exciting features this month, there is a lot of bug fixing and cleanup work going on, as well as some performance improvements, and compatibility fixes for easier application porting.
One of the most common feedback that we receive is that Haiku needs some nice colourful wallpapers shipping with its releases. We definitely want to improve the current situation. And we need your help.
Haiku currently ships with only one (1) wallpaper, and it’s not a complete wallpaper per se, it’s just the Haiku logo positioned at fixed coordinates on the screen. To be fair, there is a reason we only use the Haiku logo as the default wallpaper; we want Haiku to be usable on systems that have memory as low as 256 MB, therefore each byte that we can spare counts.
