Haiku Port Status

Haiku builds for several computer architectures, below is a list of each architecture with additional information. The interest column does not reflect any architecture preference by the Haiku project, only current real-world developer interest. x86 (Tier 1)The platform of choice for most traditional desktop and laptop computers PlatformInterestTargetHaiku LoaderHaiku KernelApplication ServerStatus 32-bit x86 PC (Compat)Highx86_gcc2Production 32-bit x86 PCHighx86Stable 64-bit x86 PCHighx86_64Production ARM (Tier 2)Newly revitalized line of processors excelling at low power consumption and low cost.

Compiling for x86_64

x86_64 Compiler Toolset Building the x86_64 compiler toolset is quite easy and involves generating GCC binaries for your platform. For a complete list of flags for the configure script, see Haiku’s Configure Options. x86_64 exclusively uses gcc13, this differs from our 32-bit x86_gcc2 builds which include both gcc2 (for BeOS compatibility) and gcc13 as a secondary architecture. From the Haiku source directory, run the following to compile the build tools (be sure to adjust the options to match your build environment):

Compiling Haiku for x86

gcc2h / gcc13 hybrid builds Haiku can be build as a hybrid image meaning that it contains gcc2 as well as gcc13 binaries. More information on this can be found on the gcc-hybrid page. This configuration is the default and is required to run both BeOS legacy applications as well as modern one using the recent programming language features available in newer gcc versions. Please ensure that you have obtained a copy of Haiku's source code as described in Get the Haiku Source Code if you have not already done so.

Compiling Haiku for Arm

Haiku can be compiled for devices leveraging the ARMv7 or later processor architecture. Please ensure that you have obtained a copy of Haiku’s source code as described in Get the Haiku Source Code if you have not already done so. Unstable The state of the ARM port is extremely early. Roll up your sleeves and help out! Create a Compiler Toolchain Building the ARM compiler toolchain is quite easy using Haiku’s configure tool.

BeTeX and LaTeX back

So here is the result : More precise mathematical formulas (note antialiasing and italic/roman mathematical characters): (a little easter egg : ocaml toplevel in a window) As soon as i can do a package i will post it on haikuware, with instructions for latex installation. UPDATE : See my last comment : the zip is ready but not available yet on the internet ; Instructions for installation will follow those of TeXLive with custom binaries (see the comment for details).

Building Haiku on Mac OS X 10.6 or 10.7 with Homebrew

The recommended method for building Haiku on Mac OS X is to use MacPorts, but, with a little bit of work it is possible to build Haiku using homebrew on Mac OS X 10.6 or 10.7 instead. You’ll need to install Xcode or at least the Command Line Tools before installing homebrew. If you don’t want to install all of XCode you can install just gcc from the packages available here:

Accepted Students

Five students to be mentored by Haiku in Google Summer of Code 2012!

For this year's Google Summer of Code™ program, we at Haiku have been allocated five students! In 2012, 406 mentoring organizatins applied and 4258 students submitted 6685 proposals. Haiku is proud to be one of the 180 accepted mentoring organizations, with five accepted students.

Over the years, Haiku's goals for Google Summer of Code have evolved. Originally the ability to evaluate the students' capabilities was lacking and the attention was simply on choosing projects that filled a need. Now, the emphasis is placed on choosing the best students, as they are more important than their short term code contributions. During the application process, those students instilled a sense of hope and confidence in Haiku's mentors that they will mature into full project contributors. In other words, this is our opportunity to grow and refine young, intelligent, and highly motivated students into people who will continue to develop Haiku in the years to come.

For the past three years, students applying to Haiku were (at first encouraged and later) required to submit a code contribution. By requiring potential students to submit a code contribution during the application period, Haiku's mentors achieve several things. First and foremost, it shows that each student possesses basic skills that many of us take for granted -- using a bug tracker and compiling Haiku's sources. More importantly, it provides our mentors with some insight into each individual student's motivation and abilities. This year a total of 17 patches were submitted during the application period. 13 of which were submitted by our top 5 selected students!

Ideas

Qualifying students can apply for a Haiku project (see the list of suggested projects below) between March 26th and April 6th, 2012. 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. The following list represents our ideas and wishes of our project.

Students

This year, 5 students participated into GSoC and all completed their projects Yongcong Du - cpuidle support Pawel Dziepak - NFSv4 client Andreas Henriksson - BFS partition resizer Hamish Morrison - OpenJDK (Java) port Alex Smith - x86_64 port

How to document a class in the API documentation (Haiku Book)

The very first thing you need to do is install Doxygen and git onto your system if you haven’t already done that. The best version of Doxygen to use is 1.7.3 since that is what is used on the server to automatically build the documentation, but, the latest one should work fine. Next grab the Haiku source from git by running: git clone git://git.haiku-os.org/haiku in the directory you wish to work (note it will automatically create a haiku/ sub-directory for you.