update frozen_mpy(modules) without recompile everything #9332
-
I have successfully compile mpy 1.19.1 for esp32/c ports using IDF 4.3.4 with some addition modules at ports/esp32/modules. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Yes and no. You have to re-create the firmware binary. If you just change individual files and keep the build directory, calling Make will just re-compile the changed files. You will still have a lot of output form CMake, which just tells that it did nothing. That's irritating. If you add or remove not-registered files from the modules directory, then Make might not notice the change. Then it helps to delete the |
Beta Was this translation helpful? Give feedback.
-
FYI @puppet13th I think this is a bug in the ESP32 build scripts. I ran into it myself the other day. On other ports it just works automatically. (The ESP32 build is extremely complicated due to how we integrate with the ESP IDF and in particular these sorts of custom rules that the IDF doesn't know about are hard to get right) |
Beta Was this translation helpful? Give feedback.
Yes and no. You have to re-create the firmware binary. If you just change individual files and keep the build directory, calling Make will just re-compile the changed files. You will still have a lot of output form CMake, which just tells that it did nothing. That's irritating. If you add or remove not-registered files from the modules directory, then Make might not notice the change. Then it helps to delete the
build-xxxx/frozen_mpy
directory before callingmake
. That will force to rebuild the frozen bytecode.