OpenHarmony Build

Use nativeAddonBuild from @import("zig-napi").napi_build to build OpenHarmony shared libraries.

nativeAddonBuild

napi_build.nativeAddonBuild(
    build: *std.Build,
    option: NativeAddonBuildOptionsWithModule,
) !NativeAddonBuildResult

Minimal build file:

const std = @import("std");
const napi_build = @import("zig-napi").napi_build;

pub fn build(b: *std.Build) !void {
    const target = b.standardTargetOptions(.{});
    const optimize = b.standardOptimizeOption(.{});

    const zig_napi = b.dependency("zig-napi", .{});
    const napi = zig_napi.module("napi");

    _ = try napi_build.nativeAddonBuild(b, .{
        .name = "hello",
        .napi_module = napi,
        .root_module_options = .{
            .root_source_file = b.path("./src/hello.zig"),
            .target = target,
            .optimize = optimize,
        },
    });
}

Targets

The helper knows the supported OpenHarmony target triples:

NativeAddonBuildResult stores the compile step for each enabled target.

If root_module_options.target is an OpenHarmony target, the helper builds only the matching output slot. Otherwise it builds all supported OpenHarmony targets.

Options

NativeAddonBuildOptionsWithModule accepts:

The helper clones the provided root module options for each target and injects configured build_options plus the configured napi import.

SDK Resolution

The helper resolves the OHOS native SDK from:

• OHOS_NDK_HOME, using $OHOS_NDK_HOME/native
• ohos_sdk_native

It then links ace_napi.z, enables libc, and adds the platform include and library directories.

Node-API Options

OpenHarmony builds use Node-API v8 by default. If the addon exports wrappers gated by a newer Node-API version, pass .node_api and also pass .napi_module = napi.

.node_api = .{
    .version = .v10,
    .experimental = false,
},

Passing napi_module lets the configured version flow into both the addon root module and the napi wrapper module.

QEMU Runtime Regression

OHOS regression uses a signed UIAbility HAP installed in a real OpenHarmony QEMU guest. The shared E2E suites run through the application's native host and verify fresh result IDs, exact test groups, finalizers and allocator cleanup across repeated launches.

The repository's pnpm test:e2e:qemu <runner arguments> pipeline builds and runs the five OHOS HAP suites in the OHOS QEMU guest. Node.js native addons and both WASI flavors run directly on the host with pnpm test:e2e:node --output zig-out/e2e-node. See OHOS QEMU setup and Node host regression.

Helper Functions