Validate Your Package with Strict ABI Check

Strict Application Binary Interface (ABI) Check is a build-time validation tool that ensures your Vega app maintains binary compatibility with Vega OS and meets AppStore submission requirements. The Strict ABI Check validates that your package:

Prevents runtime conflicts: Avoids bundling system-provided binaries that could cause linker mismatches and application crashes
Reduces package size: Eliminates redundant system binaries to keep your VPKG lean
Ensures platform compatibility: Guarantees your app uses the correct, platform-tested binary versions
Meets AppStore requirements: Required validation before AppStore submission

How it works

The Strict ABI Check enforces binary compatibility by validating two critical requirements during the build process:

Rule 1: Don’t bundle system ABI binaries

If a binary appears on the official Vega ABI list, it’s provided by the system. Your package must not bundle these binaries. What to do instead: Link against system binaries dynamically. They are available at runtime on all Vega devices.

Rule 2: Satisfy all binary dependencies

Every binary dependency in your package must be either:

Bundled within your VPKG, or
Available on the official Vega ABI list

Missing dependencies cause the ABI check to fail.

Validate your package

By default, vega exec vpt validate performs a Strict ABI Check to ensure your package meets AppStore submission requirements. To skip this check, pass the --no-strict-abi-check flag (see Use VPT for Vega App Packages). In the prompt, enter:

vega exec vpt validate <your-app>.vpkg

On success, the command reports ABI check passed and exits with code 0. ABI check fails with “bundled system binary” error Your package includes a binary that’s provided by the system. Remove the binary from your package and ensure you’re linking against it dynamically instead. ABI check fails with “unsatisfied dependency” error Your package has a binary dependency that’s neither bundled nor available on the system. Either bundle the required binary in your VPKG or verify it’s available on the official Vega ABI list. See the Use VPT for Vega App Packages for additional validation options and detailed usage.

Official Vega ABI list

The following system libraries are provided by Vega OS and must not be bundled in your package:

Standard C libraries:

libc.so.6
libdl.so.2
libm.so.6
libpthread.so.0
librt.so.1
libutil.so.1

Platform-specific libraries:

libapmf.so
libkeplerscript.so

Dynamic Linker:

ld-linux-*

Common workflows

Before AppStore submission

Always run Strict ABI Check before submitting your app to the AppStore. In the prompt, enter:

vega exec vpt validate <your-app>.vpkg

A passing result confirms your package is ready for AppStore submission.

CI/CD integration

Integrate ABI validation into your continuous integration pipeline to catch compatibility issues early. In the prompt, enter:

# Example CI/CD validation step
vega exec vpt validate ${BUILD_ARTIFACT}

The command exits non-zero on failure, which fails the CI step.

​How it works

​Rule 1: Don’t bundle system ABI binaries

​Rule 2: Satisfy all binary dependencies

​Validate your package

​Official Vega ABI list

​Standard C libraries:

​Platform-specific libraries:

​Dynamic Linker:

​Common workflows

​Before AppStore submission

​CI/CD integration

​Related topics