LVGL dependency is not properly removed from noglib BSP variants (BSP-740)

[qsaramo]

Board

esp32_p4_function_ev_board_noglib & esp32_p4_eye_noglib affected currently, but I expect every new noglib BSP release having this issue from now on.

Hardware Description

IDE Name

Operating System

Description

BSP noglib variants created in Espressif's CI have still LVGL dependency because component's manifest is not properly written back after removing dependencies from manifest_tree.

I have not investigated this thoroughly, but if I read the code correctly this is what happens when generating noglib variant of a BSP:

• remove_esp_lvgl_port() gets manifest_tree
• ManifestManager's manifest_tree property returns a dump generated from underlying model
• LVGL dependencies are removed
• when manager.dump() is called, it gets another manifest_tree dump from the underlying model and writes it onto disk.
  --> changes get lost

Sketch

• open https://components.espressif.com/components/espressif/esp32_p4_function_ev_board_noglib/versions/5.1.0/readme in browser
• click "download_archive"
• check file esp32_p4_function_ev_board_noglib/idf_component.yml from downloaded archive
• BSP component has following dependencies when it should not have

  espressif/esp_lvgl_port:
    public: true
    version: ^2
  ...
  lvgl/lvgl: '>=8,<10'

Other Steps to Reproduce

No response

I have checked existing issues, README.md and ESP32 Forum

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[github-actions]

Hi @qsaramo! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

Thank you for reporting this issue regarding the noglib BSP variants (such as esp32_p4_function_ev_board_noglib and esp32_p4_eye_noglib) still including LVGL dependencies in their idf_component.yml manifests.

Based on the official documentation and the README for these noglib variants, the intention is clear: noglib versions are meant to be used without LVGL or graphical libraries. The README for both esp32_p4_function_ev_board_noglib and esp32_p4_eye_noglib explicitly state that if you want to use LVGL, you should use the non-noglib variant instead.

However, the current published manifests for these noglib variants still list espressif/esp_lvgl_port and lvgl/lvgl as dependencies, which is not expected and contradicts the intended purpose of the noglib variants. This can be confirmed by inspecting the manifest and README files for these components, which show the LVGL dependencies present even in the noglib versions:

⚠️ This is No Graphical Library version of esp32_p4_function_ev_board BSP. If you want to use this BSP with LVGL use esp32_p4_function_ev_board component.

— esp32_p4_function_ev_board_noglib README

The issue appears to be with the process that generates the noglib variants: although the code attempts to remove the LVGL dependencies from the manifest, the changes are not persisted due to how the manifest tree is handled and written back, as you described.

Summary:

• The noglib variants are not supposed to have LVGL dependencies.
• The current manifests for these variants still include LVGL dependencies, which is a bug.
• The root cause seems to be in the CI script or manifest management logic, where dependency removal is not properly saved.

Recommendation:
This issue should be addressed in the BSP generation process to ensure that noglib variants do not include LVGL dependencies in their manifests. Until this is fixed, users of the noglib variants may encounter unexpected LVGL-related dependencies.

Thank you for highlighting this; it will help improve the BSP packaging process for all users.

References:

• esp32_p4_function_ev_board_noglib README
• esp32_p4_eye_noglib README