FFI-bindings for the native API of OpenHarmony OS. See the documentation for a list of supported components. This crate is under active development, and not officially affiliated with OpenHarmony OS.
Here is an overview of the available C header directories in the OpenHarmony sysroot, and for which of them this crate already provides bindings. The API-level column denotes up to which api level the bindings have already been generated.
| API name | status | API-level |
|---|---|---|
| AbilityKit | ||
| BasicServicesKit | ||
| ConnectivityKit | ||
| CryptoArchitectureKit | ||
| DataProtectionKit | ||
| IPCKit | ||
| LocationKit | ||
| NotificationKit | ||
| accesstoken | ||
| ace/xcomponent | ✅ | 14 |
| ark_runtime | ||
| arkui | ✅ | 14 |
| asset | ||
| bundle | ||
| database | ||
| ddk | ||
| ffrt | ||
| filemanagement | ||
| hiappevent | ||
| hicollie | ||
| hid | ||
| hidebug | ||
| hilog | ✅ | 14 |
| hitrace | ✅ | 14 |
| huks | ||
| info | ||
| inputmethod | ✅ | 14 |
| mindspore | ||
| multimedia | ||
| multimodalinput | ||
| napi | ✅ | 13 |
| native_buffer | ✅ | 14 |
| native_color_space_manager | ||
| native_display_soloist | ||
| native_drawing | ✅ | 14 |
| native_effect | ||
| native_image | ✅ | 14 |
| native_vsync | ✅ | 14 |
| native_window | ✅ | 14 |
| network | ||
| neural_network_runtime | ||
| ohaudio | ||
| ohcamera | ||
| purgeable_memory | ||
| qos | ||
| rawfile | ✅ | 14 |
| resourcemanager | ||
| sensors | ||
| telephony | ||
| transient_task | ||
| usb | ||
| web | ||
| window_manager |
The current bindings are generated with bindgen using scripts/generate_bindings.sh.
Bindings are currently generated with the OpenHarmony SDK API level 13, but with items
added after API level 10 feature guarded behind api-XX features. this is handled
automatically by the tool based on the documentation comments in the C header files.
There are still quite a few OpenHarmony APIs missing. Feel free to contribute missing APIs, but be sure to adapt
the script, so your bindings are reproducible!
The OpenHarmony SDK can be downloaded from the release notes of the respective release, e.g. the
5.0.0 release notes.
Navigate to the Acquiring Source Code from Mirrors section, select the Public SDK package for the standard system
for your host Operating System (Windows / Linux / Mac) click download and optionally verify the SHA-256 checksum
of the downloaded archive.
Extract the archive to a suitable location. Please note that the <os_name> subfolder contains more archives.
For the purpose of generating the bindings extracting the native archive is sufficient.
Once you have setup your local SDK, you should set the environment variable OHOS_SDK_NATIVE to
/path/to/ohos-sdk/<your_host_os>/native. Afterwards you can run the script to generate the bindings
and adapt it to incorporate new modules.
Please also check the following:
- Preferably generate the bindings with libclang in
Cmode. However, if a header file is not C-compliant due to an issue of the OpenHarmony SDK, then settinglibclangto C++ mode is fine. - Be sure to guard the new component behind a cargo feature and document the feature in Cargo.toml.
This crate is licensed under the Apache-2.0 license, matching the OpenHarmony OS SDK.