# OpenCV test application This section describes how to enable OpenCV library and run OpenCV test application getting-started-workflow Rectangle.8 Sheet.2 Prerequisites Prerequisites Sheet.3 Build procedure Enable OpenCV library and test package · Build procedure · Enable OpenCV library and test package Sheet.4 Implement Implement Sheet.6 Test Test Sheet.11 Sheet.13 Sheet.14 Compile build Flash images on the device · Compile build · Flash images on the device Sheet.15 Run test application · Run test application ## Prerequisites - Set up your infrastructure as described in the [Qualcomm Linux Build Guide](https://docs.qualcomm.com/bundle/publicresource/topics/80-70030-254/introduction.html) - Flash the latest software release to the development board. - Set up SSH connection: Enable SSH in Permissive mode by performing the steps mentioned in [Use SSH](https://docs.qualcomm.com/bundle/publicresource/topics/80-70030-254/how_to.html#use-ssh) - Confirm that the `libopencv_fastcv` library is present `/usr/lib` on the target. Occasionally, downloading the `fastcv_linux_aarch64_2025_02_12.tgz` fails, resulting in the `libopencv_fastcv` libraries not being generated. If the library is missing, [download the latest bitbake file](https://github.com/qualcomm-linux/meta-qcom-hwe/blob/scarthgap/recipes-support/opencv/opencv_4.11.0.qcom.bb) (`opencv_4.11.0.qcom.bb`) and recompile the build. After flashing the build, confirm that the `libopencv_fastcv` library is present in `/usr/lib`. ## Enable the OpenCV library and test package 1. To enable the **tests** package, include `tests` in `PACKAGECONFIG` in the `/layers/meta-qcom-hwe/recipes-support/opencv/opencv_4.11.0.qcom.bb` recipe file as follows. PACKAGECONFIG ??= "gapi python3 eigen jpeg png tiff v4l libv4l samples tbb gphoto2 tests \ ${@bb.utils.contains("DISTRO_FEATURES", "x11", "gtk", "", d)} \ Copy to clipboard By default, only libraries shown in the compiled build as test bins are cleaned up. 2. To retain test bins, include the following code in the `/layers/meta-qcom-hwe/recipes-support/opencv/opencv_4.11.0.qcom.bb` recipe file: RM_WORK_EXCLUDE += "opencv" Copy to clipboard 3. When the build is already compiled, OpenCV must be cleaned before compilation. To clean OpenCV, run the following command: bitbake -fc cleanall opencv Copy to clipboard During compilation no code is modified, so a direct compilation doesn’t generate the corresponding bins. 4. To compile OpenCV, run the following command: bitbake opencv Copy to clipboard The path to the libraries is `tmp-glibc\sysroots-components\armv8-2a\opencv\usr\lib`. The path to the bins is `tmp-glibc\work\armv8-2a-qcom-linux\opencv\4.11.0.qcom\build\bin`. ## Run the existing test application To invoke the OpenCV API, native OpenCV test examples can reference sample applications. Use the following procedure to invoke applications on the Snapdragon target. Compile the full build image to ensure that all libraries are part of the application images. 1. Flash the images on the device as described in the [Qualcomm Linux Build Guide](https://docs.qualcomm.com/bundle/publicresource/topics/80-70030-254/). OpenCV libraries are on the device at `/usr/lib`. 2. For test data, `git clone` the projects at [https://github.com/opencv/opencv_extra/tree/4.11.0](https://github.com/opencv/opencv_extra/tree/4.11.0). 3. To avoid read only errors while trying to push test data and bins to the device, use the device IP address to log in to an SSH terminal and run the following command to remount the device. mount -o remount,rw /usr Copy to clipboard 4. Use the `scp` command to push the test data to a preferred host location. For example: `scp -r [file] root@[IP-ADDR]:/tmp` 5. Use the `scp` command to push the required test bin to `/usr/bin`. For example: `scp -r [test] root@[IP-ADDR]:/usr/bin/` 6. Sign in to an SSH terminal and run the following commands. chmod 777 /usr/bin/ cd /usr/bin export OPENCV_LOG_LEVEL=DEBUG export OPENCV_VIDEOIO_DEBUG=1 export OPENCV_TEST_DATA_PATH=/tmp ./ --gtest_output=json:/tmp/results.json --gtest_also_run_disabled_tests exit Copy to clipboard Results are stored in `/tmp/results.json`. To change the results filename, modify the `--gtest_output=json:/tmp/{results.json}` argument. Last Published: Jun 19, 2026 [Previous Topic Overview](https://docs.qualcomm.com/bundle/publicresource/80-70030-21/topics/overview.md) [Next Topic Implement new sample app](https://docs.qualcomm.com/bundle/publicresource/80-70030-21/topics/sample-applications.md)