ESP-IDF项目中CMakeLists如何引入包含源文件与头文件的子目录？

Since you're new to ESP-IDF's CMake system (which builds on standard CMake but uses its own component-based workflow), the issue here is that you're relying on generic CMake commands instead of leveraging ESP-IDF's component registration system. Let's fix this step by step:

1. Update the Metriful directory's CMakeLists.txt #

ESP-IDF treats reusable code as "components", so we need to declare your Metriful folder as an official ESP-IDF component. Replace the content of Metriful/CMakeLists.txt with:

# Metriful/CMakeLists.txt
idf_component_register(
    SRCS "Metriful_sensor.cpp" "Wifi_functions.cpp"  # List all source files in this component
    INCLUDE_DIRS "."  # Expose the current directory (where headers live) to dependent components
)

2. Modify the root CMakeLists.txt #

Instead of include_directories, we'll add the Metriful component to our project using add_subdirectory. Update your root CMakeLists.txt to:

# Root CMakeLists.txt
cmake_minimum_required(VERSION 3.5)
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
project(ESP_32_WROOM32_SENSOR_-_Metriful)
add_subdirectory(Metriful)  # Register the Metriful component directory with the project

3. Declare dependency in the main component's CMakeLists.txt #

The main component needs to explicitly depend on the Metriful component to access its headers and link its compiled code. Update main/CMakeLists.txt to:

# main/CMakeLists.txt
idf_component_register(
    SRCS "main.cpp" "wifi.cpp"
    INCLUDE_DIRS "."
    REQUIRES Metriful  # Tell ESP-IDF that main depends on the Metriful component
)

Why this works #

• ESP-IDF's idf_component_register handles all the heavy lifting: it automatically adds include directories to dependent components, compiles the source files, and links them into your final binary.
• The REQUIRES keyword in the main component's declaration ensures ESP-IDF resolves the Metriful component's include paths and builds it before building the main component.
• Your original include_directories command didn't work because ESP-IDF components have isolated build contexts—global include directory changes don't always propagate to individual component targets.

After making these changes, clean your build directory (delete the build folder) and re-run your build command. The header file not found error should be resolved.

内容的提问来源于stack exchange，提问作者The Kaese