tools/test_apps/system/g0_components/README.md

| Supported Targets | ESP32 | ESP32-C2 | ESP32-C3 | ESP32-C5 | ESP32-C6 | ESP32-C61 | ESP32-H2 | ESP32-H21 | ESP32-H4 | ESP32-P4 | 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:
```bash
idf.py set-target esp32c3
```

Then, trigger the build:
```bash
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.
feat(esp32h4): add G0 component support (stage5) 2025-02-28 14:44:28 +08:00			`\| Supported Targets \| ESP32 \| ESP32-C2 \| ESP32-C3 \| ESP32-C5 \| ESP32-C6 \| ESP32-C61 \| ESP32-H2 \| ESP32-H21 \| ESP32-H4 \| ESP32-P4 \| ESP32-S2 \| ESP32-S3 \|`
			`\| ----------------- \| ----- \| -------- \| -------- \| -------- \| -------- \| --------- \| -------- \| --------- \| -------- \| -------- \| -------- \| -------- \|`
G0: add a build example to check G0 dependencies 2022-04-28 16:41:02 +08:00
			`# "G0"-components-only app`

G0: Support Xtensa targets for G0-only compilation G0-only example now supports Xtensa targets. This means that G0 layer does not depend on G1+ layers anymore 2022-06-16 17:06:39 +08:00			`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.`
G0: add a build example to check G0 dependencies 2022-04-28 16:41:02 +08:00
G0: Support Xtensa targets for G0-only compilation G0-only example now supports Xtensa targets. This means that G0 layer does not depend on G1+ layers anymore 2022-06-16 17:06:39 +08:00			`This supports all Xtensa and RISC-V based ESP targets.`
G0: add a build example to check G0 dependencies 2022-04-28 16:41:02 +08:00
			`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`

G0: Support Xtensa targets for G0-only compilation G0-only example now supports Xtensa targets. This means that G0 layer does not depend on G1+ layers anymore 2022-06-16 17:06:39 +08:00			Set the target, `esp32c3` for example:
G0: add a build example to check G0 dependencies 2022-04-28 16:41:02 +08:00			```bash
			`idf.py set-target esp32c3`
			```

			`Then, trigger the build:`
			```bash
			`idf.py build`
			```

esp32h2: renaming esp32h2 to esp32h4 2022-10-19 15:57:24 +08:00			`Build should be successful if there is no dependency problem between G0 and upper layers.`
G0: add a build example to check G0 dependencies 2022-04-28 16:41:02 +08:00
			# 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.