Build and test KleidiCV on macOS
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Run the test binary at
./build-kleidicv-benchmark-SME/test/api/kleidicv-api-test. It prints the number of tests executed and their results to confirm the build works.Expect output similar to a vector length report and a summary of tests run and passed. A clean pass indicates the build and public API are functioning.
KleidiCV auto-detects your CPU and selects the fastest path: Neon, SVE2, or SME2. Review the test output in the SME verification step. On supported Apple silicon, SME support is exercised during the tests.
No. KleidiCV automatically detects the hardware and chooses the optimal implementation, so your code doesn’t need to change.
Confirm the build finished without errors and run the binary from the path shown. If issues persist, confirm that you installed the required tools, then rebuild and rerun the tests.