The Haiku project has been accepted to participate in Google Summer of Code&trade 2010! Qualifying students can apply for a Haiku project (see the list of suggested projects below) between March 29th and April 9th, 2010. For details about how to apply, please check out Students: How to Apply for a Haiku Idea.
According to other mentor organizations, the most successful Google Summer of Code projects are the ones proposed by the students themselves.
This year, 5 out of 7 students completed their projects
Atis Elsts - IPv6 support Janito Vaqueiro Ferreira Filho - EXT3 filesystem Lucian Adrian Grijincu - Linux Kernel in Haiku userspace (failed - student disappeared for several weeks) Cristopher Humphries - DVD playback in MediaPlayer (failed - student had to withdraw because of misunderstanding with his school) Cristophe Huriaux - HTTP client implementation Nathan Mentley - x86_64 port (failed - project was too complex for the student) Alex Wilson - layout API finalization
Haiku single sheet flier (2010 version) Mid-resolution PDF (adequate for on-demand printing): US Letter | A4 Original files in InDesign format: US Letter Designed by Jorge G. Mare. Released under a Creative Commons Attribution, Noncommercial, Share Alike license.
Additionally, Haiku's Haiku Vector Icon Format (HVIF) icons are available in Haiku's source repository, along with miscellaneous artwork files.
Accessing BFS outside of Haiku What is FUSE? FUSE is an acronym for "Filesystem in USErspace" and in essence allows an operating system to communicate with a file system through a userland progam. By providing this functionality outside of kernel space, adding support for a new filesystem is a simple matter of installing the respective FUSE module. As a comparison, the typical paradigm involves altering the operating system's kernel to support the filesystem.
The tools you need to compile software for Haiku, or to compile Haiku itself, depend on the platform that you are using for building Haiku.
The Haiku operating system can be a very convenient development environment for working on Haiku, but using Haiku is not strictly necessary. It may also not be practical to use Haiku in some very special cases, such as when writing some drivers - using a virtual machine to test your changes may be much more practical.
Due to the various ways that extended attributes are implemented in various file systems, some will present issues that need to be considered and others will simply be unusable. This page aims to clarify which file systems have extended attribute implementations compatible enough with Haiku’s that they can be utilized during cross-builds.
Note that configure auto-detects the extended attribute capabilites of the filesystem you have asked it to configure a build on, and will automatically select “full”, “ref”, or no usage at all based on the filesystem’s capabilites.
There are a wide range of options and configurations available to boot Haiku, from from modifying the boot sector, to configuring (and possibly installing) a boot manager. For an overview of the various booting options available to Haiku, please check out this page of the Haiku User Guide
Using Makebootable makebootable is a low-level Haiku tool to enable x86 MBR (legacy bios) systems to boot from the active Haiku partition.
As you should know, Ryan and I worked actively on the WebKit port during this summer.
I won't say this port is perfect, because many parts need to be improved and stabilized.
Anyhow, I think it's a good idea to provide a way for people to build it and not moving in the dark.
Building WebKit on Haiku isn't so hard but can be really long.
This is the top page to be used as the index for all the guides.
Using a USB flash drive is one of the best ways to install Haiku. It is also the only way to really try and enjoy all the features of Haiku without touching your hard drives. The Haiku live CD is limited by the slow access time of CDs and still lacks a few features due to the added complexity to run on a read-only media. Note that running off a USB flash drive might still be a lot slower than a real hard drive depending on your model.
