CMake and Project Structure

Read the standalone ESP-IDF tree and understand how generated sources and assets enter the build.

Exported structure

text

project/
├── CMakeLists.txt
├── sdkconfig.defaults
└── main/
    ├── CMakeLists.txt
    ├── main.c
    ├── 01_FG_Runtime.c
    ├── 90_Studio_Export.c
    ├── 90_Studio_Export.h
    ├── 95_UserEvents.c
    ├── 95_UserEvents.h
    └── assets/
        ├── defaults/*.c
        └── uploads/*.c

Component registration

cmake

idf_component_register(
    SRCS
        "main.c"
        "01_FG_Runtime.c"
        "90_Studio_Export.c"
        "95_UserEvents.c"
        "assets/uploads/fg_upload_...c"
    INCLUDE_DIRS "."
    REQUIRES driver esp_event esp_wifi fatfs sdmmc
)

Normal ESP-IDF build

The exporter materializes normal CMake source registration. There is no proprietary build wrapper in the standalone project; ESP-IDF consumes the project through its standard CMake flow.