Build problem with OpenCV IDF component (IEC-85)

[Ncouch64]

Answers checklist.

• I have read the documentation of the component in question and the issue is not addressed there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Hello! I am reaching out here with a build problem with the OpenCV component mentioned here in this PR: #94. At first I was thinking it was a problem with my idf but I have been able to get projects build with various other components, as soon as I add the OpenCV component as a dependency I get the build failure. This may be something super simple that I am overlooking but after all my searching around I have not been able to find a solution. Thank you for your time!

Edit: Also should probably mention that this is while doing just one of the examples "features2d" that you can find mentioned on the idf component registry here: https://components.espressif.com/components/espressif/opencv.

The build failure I am getting when using the component:
-- Found Git: C:/Users/na258588/.espressif/tools/idf-git/2.39.2/cmd/git.exe (found version "2.39.2.windows.1")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/Users/na258588/.espressif/tools/xtensa-esp32s3-elf/esp-12.2.0_20230208/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-gcc.exe
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Users/na258588/.espressif/tools/xtensa-esp32s3-elf/esp-12.2.0_20230208/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-gcc.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Users/na258588/.espressif/tools/xtensa-esp32s3-elf/esp-12.2.0_20230208/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-g++.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- git rev-parse returned 'fatal: not a git repository (or any of the parent directories): .git'
-- Could not use 'git describe' to determine PROJECT_VER.
-- Building ESP-IDF components for target esp32s3
Processing 3 dependencies:
[1/3] espressif/esp32-camera (2.0.6)
[2/3] espressif/opencv (4.7.0~3)
[3/3] idf (5.1.2)
-- Found Git: C:/Users/na258588/.espressif/tools/idf-git/2.39.2/cmd/git.exe (found version "2.39.2.windows.1")
CMake Error at C:/Users/na258588/esp/esp-idf/tools/cmake/component.cmake:224 (message):
CMake Warning (dev) at build_properties.temp.cmake:8:

Syntax Warning in cmake code at column 47

Argument not separated from preceding token by whitespace.

Call Stack (most recent call first):

C:/Users/na258588/esp/esp-idf/tools/cmake/scripts/component_get_requirements.cmake:3 (include)

This warning is for project developers. Use -Wno-dev to suppress it.

fatal: not a git repository (or any of the parent directories): .git

CMake Error at
C:/Users/na258588/.espressif/tools/cmake/3.24.0/share/cmake-3.24/Modules/ExternalProject.cmake:1253
(define_property):

define_property command is not scriptable

Call Stack (most recent call first):

C:/Users/na258588/esp/esp-idf/tools/cmake/kconfig.cmake:1 (include)
C:/Users/na258588/esp/esp-idf/tools/cmake/idf.cmake:43 (include)
C:/Users/na258588/esp/esp-idf/tools/cmake/project.cmake:29 (include)
E:/work/Project/features2d/CMakeLists.txt:5 (include)
C:/Users/na258588/esp/esp-idf/tools/cmake/scripts/component_get_requirements.cmake:106 (include)
C:/Users/na258588/esp/esp-idf/tools/cmake/scripts/component_get_requirements.cmake:124 (__component_get_requirements)

Call Stack (most recent call first):
C:/Users/na258588/esp/esp-idf/tools/cmake/build.cmake:574 (__component_get_requirements)
C:/Users/na258588/esp/esp-idf/tools/cmake/project.cmake:547 (idf_build_process)
CMakeLists.txt:6 (project)

-- Configuring incomplete, errors occurred!
See also "E:/work/Project/features2d/build/CMakeFiles/CMakeOutput.log".

The terminal process "C:\Windows\System32\cmd.exe /d /c cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -B e:\work\Project\features2d\build -S e:\work\Project\features2d" terminated with exit code: 1.

[dmitry1945]

@Ncouch64 the new version of IDF opencv component released. Please take a look.

[Ncouch64]

Ok, I was able to get the example features2d project to build with 4.7.0~4 - YAY! Now I am running into a separate problem. So creating the project from the example using idf.py create-project-from-example "espressif/opencv^4.7.0~4:features2d" it is unable to find any of these source files -
#include <esp_log.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_system.h"
#include "esp_timer.h"
#include "esp_camera.h"
and for whatever reason when it is flashed to my ai-thinker board I get this out

I (2717) gpio: GPIO[5]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:2
I (2727) cam_hal: cam init ok
I (2727) sccb: pin_sda 18 pin_scl 23
I (2727) sccb: sccb_i2c_port=1
E (2747) camera: Camera probe failed with error 0x105(ESP_ERR_NOT_FOUND)
E (2747) CAM: Camera Init Failed
I (2747) main_task: Returned from app_main()
None

I am assuming that I am doing something wrong here. It has been a good few months since I was fully dug in to ESP work so there is likely some processes that I am overlooking. I thank you @igrr & @dmitry1945 for the continued assistance.

[dmitry1945]

@Ncouch64 let me check...

[dmitry1945]

@Ncouch64 I've now created a project from idf.py create-project-from-example "espressif/opencv^4.7.0~4:features2d"
and it's compiled without problems....
Could you please update to the latest IDF version, if it's possible? Or do you have one already?

[Ncouch64]

Hmm, now this is odd. I am pretty sure I am on the latest IDF version, I will check now and make sure. Ill then try and create another project from the example. Is there anything I should be doing outside of creating the project and building it?

Edit: Currently on 5.1.2 using VSCode.
Edit 2: Ok, did a fresh install of IDF just as a sanity check. Using the above command created a features2d example project, set my target for my ESP32 device and build the project. It completes the build without errors, but none of those header files are found and when I flash the build to my device I get the output mentioned above.

[dmitry1945]

@Ncouch64 just to be sure, did you run git submodule update --init --recursive after switch to 5.2 (I always forger to do this...)?
And, did you select the AI-Thinker in menuconfig?

And, see you tomorrow.

[Ncouch64]

You are totally right these are things I should look into tomorrow. Thanks for the continued assistance. I will be going back at the ESP work tomorrow morning so I will test and post my findings here.

[Ncouch64]

@Ncouch64 just to be sure, did you run git submodule update --init --recursive after switch to 5.2 (I always forger to do this...)? And, did you select the AI-Thinker in menuconfig?

And, see you tomorrow.

Ok, updated to 5.2 (was previously 5.1.2), running the submodule update in the features2d project doesn't work for me as it says it is not a git repository - this is after creating a brand new project from the features2d example. After attempting to run the example again I finally got an output of detected features! Weirdly enough it is telling me it still cannot locate the source files. For example its saying it cannot open esp_err.h source file (dependency of esp_camera.h). I will try to do some of my own testing using the CV component now that I got an output to see if I can get a simple project to work.

Edit: I also want to mention here, I am not sure if its just my IDF or what but if I have the CV component added into the project it takes anywhere from 10-20 minutes just to open the sdk config and to build the project a similar amount of time. Is this expected or have I done something wrong? Also fixed the above paragraph, something happened in the edit that messed it up.

[Ncouch64]

@dmitry1945 Have you tested the FAST algorithm running this component? I am having an issue where features are not being detected.

[dmitry1945]

@Ncouch64 no, I'be tested with some default one... What kind of problem do you have with a FAST?

[Ncouch64]

@Ncouch64 no, I'be tested with some default one... What kind of problem do you have with a FAST?

Its really interesting actually. So if I use for example goodFeaturesToTrack() it is able to detect features in images. If I use Fast() it is never able to detect features in the image. I am not quite sure what the problem is.

[Ncouch64]

I also did want to throw out another question, would using the findEssentialMat() function and related functions be too intense for an esp chip to handle? I am wondering if there are too many operations to properly run on ESP. Currently when trying to use this function I get this during build: region `dram0_0_seg' overflowed by 465872 bytes.

[dmitry1945]

@Ncouch64 it's possible to calculate the findEssentialMat(), but for that you will need to make some changes in opencv. And anyway, it will not be very fast. It will be possible with new Espressif chips.
If you want, you can try with esp32. For that, you will need to change double type to float, and remove some big arrays to the constant memory.

[Ncouch64]

@Ncouch64 it's possible to calculate the findEssentialMat(), but for that you will need to make some changes in opencv. And anyway, it will not be very fast. It will be possible with new Espressif chips. If you want, you can try with esp32. For that, you will need to change double type to float, and remove some big arrays to the constant memory.

Do you feel like an S3 would have a better chance at this? I have one of those on the way.

Also thank you for the continued assistance with this component.