alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
1e8b9f8b9c
esp-idf/tools/test_apps/system/g0_components
History
Armando ac86ef31c1 g0: resolve MMU_PAGE_SIZE not defined in g0 build issue
2023-02-23 12:35:52 +08:00
..
main G0: Support Xtensa targets for G0-only compilation 2022-06-20 11:34:20 +00:00
CMakeLists.txt g0: resolve MMU_PAGE_SIZE not defined in g0 build issue 2023-02-23 12:35:52 +08:00
README.md docs: changes docs supported targets tables 2022-07-14 08:26:32 +08:00

README.md

Supported Targets ESP32 ESP32-C2 ESP32-C3 ESP32-H2 ESP32-S2 ESP32-S3

"G0"-components-only app

This test application will compile ESP-IDF and this test's main component with G0 components only. The goal is to make sure that no G0 component depends on G1 or higher component.

This supports all Xtensa and RISC-V based ESP targets.

The purpose of this example is to make sure that any modification to ESP-IDF doesn't violate the G0-G1+ dependency rule.

Using this test app

Set the target, esp32c3 for example:

idf.py set-target esp32c3

Then, trigger the build:

idf.py build

Build should be successful if there is no dependency problem between G0 and upper layers.

Component dependencies graph (component_deps.dot)

When this project is configured, component_deps.dot file in the build directory is generated. This file contains a Graphviz graph showing the component dependencies. You can visualize this graph (using dot tool or online at https://dreampuf.github.io/GraphvizOnline/) to see why an extra component got added. You can also build the project for the base branch, to compare the graph to a known good one.