The rule to add an executable or shared library to the Haiku image automatically also includes the corresponding locale catalogs and MIME database entries. The locale catalogs for .a files linked in the executable are also included, since .a files are not themselves added to the same package. This makes sure the executable has all the catalogs it needs. The jam rule was written assuming that NEEDLIBS would only contain .a files, but that is not the case when compiling Haiku. Libroot for example is also in NEEDLIBS (this makes sure it is linked by absolute file path, whereas LINKLIBS would instead use -lroot and may link the host system one). Filter out .so files from the NEEDLIBS list when determining which catalogs to include. Fixes #19721. Change-Id: I04604bd37c656f987dd17be8db6edffe88cee651 Reviewed-on: https://review.haiku-os.org/c/haiku/+/10144 Reviewed-by: Adrien Destugues <[email protected]> Tested-by: Commit checker robot <[email protected]>
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 web-based source code browsers:
- https://grok.nikisoft.one/opengrok/ (OpenGrok, provided by Niklas Poslovski)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
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.
Contributing to our infrastructure
See Infrastructure.