Auditing an architecture before you promise it

Adding a CPU-architecture target to a desktop build is not a build-system question: everything compiles, packages and launches, then the first call into a dependency carrying a compiled binary fails, because it shipped slices for four architectures and yours was not one of them.

One missing native takes the whole target down. No partial success, no graceful degradation: a database driver with no slice for your architecture cannot open a connection — the app is not "missing a feature", it is finished.

The failure is at first use, not at build time. Compile, package, sign, install, launch — none of that touches the native. Only exercising the feature does, which is why this must be an audit you run deliberately, not something you expect CI to tell you.

The audit

Native code reaches the JVM in three packaging shapes, and only the second is visible in your dependency list: