![]() ![]() The next time the project is built, CMake will configure it from scratch. This includes all CMake configuration output. Idf.py fullclean will delete the entire “build” directory contents. Cleaning doesn’t delete CMake configuration output and some other files. Idf.py clean will “clean” the project by deleting build output files from the build directory, forcing a “full rebuild” the next time the project is built. By default, the build tool is automatically detected but it can be explicitly set by passing the -G option to idf.py.īuilding is incremental so if no source files or configuration has changed since the last build, nothing will be done. Run the main build tool ( Ninja or GNU Make).Run CMake as necessary to configure the project and generate build files for the main build tool. ![]() The sub-directory build is used to hold build output, although this can be changed with the -B option. Idf.py build will build the project found in the current directory. Idf.py menuconfig runs the “menuconfig” tool to configure the project. Here are a summary of the most useful ones: Type idf.py -help for a full list of commands. Older style projects with a Makefile will not work with idf.py. Idf.py should be run in an ESP-IDF “project” directory, ie one containing a CMakeLists.txt file. The getting started guide contains a brief introduction to how to set up idf.py to configure, build, and flash projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |