esp-idf/examples/build_system/cmake/idf_as_lib
Armando c863a79a6d idf_as_lib: remove dependency to esp_psram
Previously this dependency is introduced by mistake. As idf_as_lib
example doesn't need esp_psram, remove this dependency.
2022-07-11 21:20:59 +08:00
..
stubs efuse: Adds major and minor versions and others 2022-07-05 14:38:27 +08:00
build-esp32.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
build-esp32c2.sh esp8684: rename target to esp32c2 2022-01-19 11:08:57 +08:00
build-esp32c3.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
build-esp32h2.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
build-esp32s2.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
build-esp32s3.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
build.sh CI: idf_as_lib is now run on all suported targets 2022-01-07 12:10:35 +08:00
CMakeLists.txt idf_as_lib: remove dependency to esp_psram 2022-07-11 21:20:59 +08:00
main.c spi_flash: Remove legacy spi_flash drivers 2022-07-01 11:01:34 +08:00
README.md examples: Move idf_as_lib sdkconfig file to the project directory 2020-10-14 19:30:30 +11:00
run-esp32.sh global: use '/usr/bin/env bash' instead of '/usr/bin/bash' in shebangs 2020-04-03 01:10:02 +02:00
run-esp32c2.sh esp8684: rename target to esp32c2 2022-01-19 11:08:57 +08:00
run-esp32c3.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
run-esp32h2.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
run-esp32s2.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
run-esp32s3.sh Build: fix idf_as_lib example not building 2022-01-06 03:17:29 +00:00
run.sh global: use '/usr/bin/env bash' instead of '/usr/bin/bash' in shebangs 2020-04-03 01:10:02 +02:00

Supported Targets ESP32

Using ESP-IDF in Custom CMake Projects

This example illustrates using ESP-IDF components as libraries in custom CMake projects. The application in this example can run on either host or on an ESP32, and the appropriate libraries are linked to the executable depending on which target is specified. If the target is an ESP32, the libraries created from ESP-IDF components are linked. On the other hand, stub libraries are linked if example is meant to be run on the host to simulate the same application behavior.

The application in this example is equivalent to the hello_world example under examples/get-started/hello_world.

Example Flow

Users looking at this example should focus on the top-level CMakeLists.txt file. This builds an application that can run on the target without relying on the typical ESP-IDF application template.

Output

Hello world!
This is ESP32 chip with 2 CPU cores, WiFi/BT/BLE, silicon revision 0, 4MB external flash
Restarting in 10 seconds...
Restarting in 9 seconds...
Restarting in 8 seconds...
Restarting in 7 seconds...
Restarting in 6 seconds...
Restarting in 5 seconds...
Restarting in 4 seconds...
Restarting in 3 seconds...
Restarting in 2 seconds...
Restarting in 1 seconds...
Restarting in 0 seconds...

Building this Example

To build this example, the user can either run build-esp32.sh to build for the ESP32 or run build.sh to build for the host:

# Builds the example for ESP32
./build-esp32.sh

Note: To build for a different target SoC, copy the build-esp32.sh file and change the -DTARGET=esp32 clause on the second line.

or

# Builds the example to run on host
./build.sh

Flashing and Running this Example

To flash and run the example, users can run either run-esp32.sh or run.sh depending on what the example was built for. In the case of run-esp32.sh, the port needs to be specified:

# Run the example on device connected to /dev/ttyUSB1
./run-esp32.sh /dev/ttyUSB1

or

# Run the example on the host
./run.sh

Configuring this Example

To modify the example ESP-IDF project configuration, first create the CMake build directory. This can be done by running build-esp32.sh or by running only the first two lines in build-esp32.sh (which won't build the actual project yet).

Then execute the menuconfig build target in the build directory:

cmake --build build -- menuconfig

If using ninja directly:

ninja -C build menuconfig

Note: ESP-IDF project configuration isn't used by the host CMake builds, the config is only read when the project is built using the ESP-IDF build system.


There is a discussion on using ESP-IDF in custom CMake projects in the programming guide under API Guides -> Build System -> Using ESP-IDF in Custom CMake Projects