8d27b645e7
In our C library we try to provide a "clean" POSIX/ISO-C set of include files that strictly conforming applications can use. However, we also want to provide some extensions that are commonly available in BSD or GNU systems. These are normally provided in a separate directory (headers/compatibility/bsd) and additionally guarded by compiler defines that can either be explicitly set, or enabled by default if the language standard (selected from the compiler command line) is one with GNU extensions (this is the default for GCC). This is controlled by a header file called features.h. However, for some headers it is not so simple to split the GNU extensions apart from the other parts of the file, because it's not just extra functions, but additional flags and defines. So, we need the "features.h" mechanism to be available even in the base set of headers, but not enable anything if the BSD headers are not in the search path. The simplest way to achieve this is to have an empty features.h in the base set of headers, that can then be overriden by the one in headers/compatibility/bsd if needed. Fixes #18732 Change-Id: Ia54d1206c2fba378ae276ed4232aee8443180afb Reviewed-on: https://review.haiku-os.org/c/haiku/+/7287 Reviewed-by: waddlesplash <waddlesplash@gmail.com> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
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://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- 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.