ESP32 Forum

We have a complex software solution and want to use ESP32P4 as an affordable evaluation platform for customers. We would like to integrate the IDF into our own build process that is not CMake-based. With other vendor SDKs it is often possible to configure a project, and to export build artifacts for later use. We would like to export:

• prebuilt libraries
• generated headers
• linker scripts
• public headers or at least a list of include paths pointing into the IDF

This is usually called a bundle or similar. We do NOT want to use the the IDF build system for application development. How is it possible to achieve that goal with the IDF build system? I don't mind some hand-work. I would even simply crawl the build folder for the needed artifacts and extract include paths from the command lines, but I was hoping for a cleaner way.

I had a look at the idf_as_lib project in the IDF which seems to describe our scenario, but that requires a CMake-based build flow in the application project and is not the 2-step build that I was hoping for.

I don't have a direct solution, but ESP32-Arduino also has the same issue and they developed a tool for it. Maybe you can get inspiration from there?