Hi,

Just as a curiosity, I setup GitHub to build the v5 branch with "GitHub actions".

You can find the latest runs here : https://github.com/llange/Open-Vehicle-Monitoring-System-3/actions

The configuration file is here : https://github.com/llange/Open-Vehicle-Monitoring-System-3/blob/experimental-esp-idf-build-workflow/.github/workflows/build-ovms.yml

Note: It's a specific branch because I had to add some configuration files (default sdkconfig options for example), change the reference to wolfssl submodule, add a patch for our mongoose version, ... ; but in the future I could make a PR for this feature if we find it useful.

(I also would like to experiment a little bit with static code analysis, unit tests, etc...)

Regards,

Le 06/02/2023 à 15:23, Ludovic LANGE a écrit :

Hi again,

Additionally, I've just verified that the official docker image for ESP-IDF (doc: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-docker-image.html ) is able to build the branch.

The only thing to add to the image is the "dos2unix" utility ("apt update && apt-get install dos2unix"), after that you'll be able to build the image.

Do not forget to update your sdkconfig (enabling FreeRTOS compatibility and unchecking SSL for mongoose) before building, and to do the patches for mongoose / wolfssl as described here: https://github.com/llange/Open-Vehicle-Monitoring-System-3/blob/experimental-esp-idf-v5/README.md

Then "idf.py build" should work - at least !

I've used the `docker run --rm -v $PWD:/project -w /project -it espressif/idf:release-v5.0` command to have a shell prompt (launch that in your source file path)

Then install dos2unix, launch menuconfig, then build.

Tell me how it works for you.

(You may have some component build failure ; depending on the sdkconfig flags, I'm still trying to document it)

Regards,