Moving to IDF 5.x

[sle118]

This is a discussion covering the move to the esp-idf version 5.x, which is being done in branch "refactoring".

[emlynmac]

EDIT: Fresh clone seemed to resolve the error, but the tools/protodot folder is empty.

@sle118 I just tried to take a checkout of the refactoring branch and ran into a git error:
fatal: No url found for submodule path 'tools/protodot' in .gitmodules

Did the submodules get missed somehow?

[sle118]

I have not had a chance to check. But the tool comes from this project. I might change the build to ignore when it's not there, as it is only used to generate a graph representation of the protocol buffer data model, so not mandatory for generating code.

https://github.com/seamia/protodot

[emlynmac]

I've finally found some time to start on this!

I'm keeping changes here: https://github.com/emlynmac/squeezelite-esp32/tree/emlynmac-migration

First issue seems to be around protobuf; I'm using WSL with ubuntu 24 and I'm seeing this:

CMake Warning (dev) at tools/protoc_utils/protobuf_utils.cmake:37 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

Call Stack (most recent call first):
  spiffs_src/CMakeLists.txt:3 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

Do i need a specific version of protobuf here?

[emlynmac]

~/code/squeezelite-esp32/tools/protoc_utils/protoc-gen-dump.py: program not found or is not executable
Please specify a program using absolute path or make sure the program is available in your PATH system variable
--dump_out: protoc-gen-dump: Plugin failed with status code 1.

Looks like the python environment is hard-coded here?

#!/opt/esp/python_env/idf4.4_py3.8_env/bin/python

Running from the command line I get:

./protoc-gen-dump.py
-bash: ./protoc-gen-dump.py: cannot execute: required file not found

And then below that

FAILED: spiffs/CMakeFiles/spiffs_spiffs_bin ~/code/squeezelite-esp32/build/spiffs/CMakeFiles/spiffs_spiffs_bin 
cd ~/code/squeezelite-esp32/build/spiffs && ~/.espressif/python_env/idf5.4_py3.12_env/bin/python ~/esp/esp-idf/components/spiffs/spiffsgen.py 0x4b000 ~/code/squeezelite-esp32/build/spiffs/data ~/code/squeezelite-esp32/build/spiffs.bin --page-size=256 --obj-name-len=32 --meta-len=4 --use-magic --use-magic-len
Traceback (most recent call last):
  File "~/esp/esp-idf/components/spiffs/spiffsgen.py", line 590, in <module>
    main()
  File "~/esp/esp-idf/components/spiffs/spiffsgen.py", line 582, in main
    spiffs.create_file('/' + os.path.relpath(full_path, args.base_dir).replace('\\', '/'), full_path)
  File "~/esp/esp-idf/components/spiffs/spiffsgen.py", line 407, in create_file
    raise RuntimeError("object name '%s' too long" % img_path)
RuntimeError: object name '/www/js/node_vendors.bundle.js.gz' too long

[toannmwork91]

@emlynmac : Have you resolved the issues related to protobuf and version incompatibility in your migration branch? If so, could you please share any specific advice or solutions you implemented? I greatly appreciate your assistance in addressing these errors during the upgrade to version 5.4.1.

[emlynmac]

@toannmwork91 , I've had zero time to put towards this.

[wizmo2]

Slightly off topic, but I am considering an attempt at migrating this squeezelite code as a ESPHOME component.

I've been playing with a new Waveshare ESP32-S3 Touch device. With some help, it works well as an HA Assist client. I was thinking that it would be nice to replace the basic media_player component with one that integrates with Lyrion.

I had a quick review of the external component documentation and some examples. @gnumpi did some work with esp-idf adf pipelines which looks like it has now been merged with the core. I'm thinking that it should be possible to load @philippe44 squeezelite component and then utilize ESPHOME for audio pipeline, display functions, device compatibility, etc..

I'm going to have a deeper dive into it.

[emlynmac]

Oh that looks interesting! I'm a big fan of HomeAssistant and having a direct link would be nice.

[haldi4803]

Slightly off topic, but I am considering an attempt at migrating this squeezelite code as a ESPHOME component.

That fits?