hello_world

# ESP-GSP Hello World

This example is the minimum application path:

1. initialize an ESP-LCD target with `hw_init`;
2. create the generated bundle configuration with `gsp_bundle_config()`;
3. start GSP with `esp_gsp_esp_lcd_start()`;
4. update one named control through its generated typed API.

The scene contains static text and one progress control. Advanced media,
navigation, component and performance workloads live in `../benchmark`.

## Preview in a browser

Build the real example scene and run it with the ESP-GSP WASM runtime:

```sh
export GSPC_EXECUTABLE=/absolute/path/to/gspc
./preview_wasm.sh
```

The command opens a local interactive preview. Set
`GSP_WASM_PREVIEW_NO_OPEN=1` for AI or headless environments; the printed URL
can be opened by browser automation. A Component Registry copy of this example
may need `idf.py reconfigure` once to install ESP-GSP before previewing.

Export the matching ESP-IDF environment, then build with one board profile:

```sh
idf.py -B build_esp32c3 \
  -D SDKCONFIG=build_esp32c3/sdkconfig \
  -D SDKCONFIG_DEFAULTS=sdkconfig.defaults \
  set-target esp32c3 build
```

Native RGB888 uses the same minimal scene:

```sh
idf.py -B build_esp32p4_rgb888 \
  -D SDKCONFIG=build_esp32p4_rgb888/sdkconfig \
  -D SDKCONFIG_DEFAULTS=sdkconfig.defaults \
  -D GSP_HELLO_RGB888=ON \
  set-target esp32p4 build
```

ESP-IDF automatically loads the matching `sdkconfig.defaults.<target>` after
the base file. See the [Kconfig guide](../../docs/kconfig.md) before changing
framework capacities, features, or task memory placement.