Jérôme Duval
73de58376a
"Renaming" means the icu namespace is suffixed with the version number, atm icu_55. Using "renaming" allows to use two different versions of ICU, thus easing upgrades. For instance haikuwebkit uses a current version of ICU, while the system uses a newer one after an upgrade. * Replace all uses of the icu namespace in our public headers, with a macro defaulting to icu. As the namespace is only used for private fields pointers, there should be no impact. * Locale kit *.cpp have to import the macro from <unicode/uversion.h> *before* including any locale headers. Ditto for a Time preferences cpp file. This way, the correct current icu namespace is referenced. * Fixes bug #12057.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:
- http://grok.bikemonkey.org/source (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.