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
cf1b222cac
esp-idf/tools/test_apps/system/g1_components
History
Marius Vikhammer cf1b222cac build system: removed target component 
After refactoring the target components (e.g. esp32) no longer contained any real functionality.
What remained in these components have been moved elsewhere and the component itself deleted from the
build system.
2022-05-24 09:12:59 +08:00
..
main tools: add a test app to check "G1-only" build 2021-12-02 15:29:00 +01:00
CMakeLists.txt build system: removed target component 2022-05-24 09:12:59 +08:00
README.md esp8684: rename target to esp32c2 2022-01-19 11:08:57 +08:00

README.md

Supported Targets ESP32 ESP32-S2 ESP32-S3 ESP32-C3

ESP32-C2 Not support this test currently, because some of components have not been supported. IDF-4135

"G1"-components-only app

This test application checks the list of components included into the build when "G1" components are added to the build. If G1 components don't have any dependencies outside of G1, then only G1 components themselves should be built.

Currently, this is not the case, and many other components are added to the build. See extra_components_which_shouldnt_be_included list inside CMakeLists.txt.

The purpose of this example is to:

  • Document which extra components are known to be included into G1 build.
  • Fail the build if additional components are added to G1 build, preventing new dependencies outside of G1 from being added to G1 components.

Once all the unwanted dependencies of G1 components are removed, the extra_components_which_shouldnt_be_included list should become empty.

Please note, if an extra component B is already added to the build as a dependency of component A (A -> B), the build of this example will not fail when a new dependency onto the same component is added (C -> B). It will only fail when a new component is added to the build. Diff-ing build/component_deps.dot (see below) against a known-good one could be an alternative, but it will likely be quite fragile.

Using this test app

To check G1 components using this app, run:

idf.py reconfigure

(optionally, set IDF_TARGET to check this for a different target than the default one)

Troubleshooting

If you get a build error in this example,

Unexpected components list in G1 build. Expected: <list>. Actual: <list>.

it means that the list of extra components added to G1 build has changed compared to extra_components_which_shouldnt_be_included.

  • If "Expected" contains more components than "Actual" — great! You have simplified the build dependency graph. Identify the component which is no longer added to the build and remove it from extra_components_which_shouldnt_be_included.
  • If "Actual" contains more components than "Expected" — not so great. It means that some change has caused additional component to be "pulled into" the build. If you don't know which additional component was added, check component_deps.dot file in the build directory (see below).

Please try very hard not to increase the number of components in extra_components_which_shouldnt_be_included.

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.