[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.
IDF version.
5.2.2
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
I expect create_esp_enc_img to keep the encrypted image updated
What is the actual behavior?
The output image is created once and never updated when the input binary file changes
Steps to reproduce.
Create a project
Add espressif__esp_encrypted_img component
Add a call to create_esp_enc_img(${CMAKE_BINARY_DIR}/${CMAKE_PROJECT_NAME}.bin, ${project_dir}/rsa_key/private.pem, ${CMAKE_BINARY_DIR}/${CMAKE_PROJECT_NAME}.bin.enc app) in a CMakeLists.txt file
Build the project and observe that the encrypted binary is created
Change something in the project and build again
Observe the .bin update while the .bin.enc is untouched
Answers checklist.
IDF version.
5.2.2
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
I expect
create_esp_enc_img
to keep the encrypted image updatedWhat is the actual behavior?
The output image is created once and never updated when the input binary file changes
Steps to reproduce.
espressif__esp_encrypted_img
componentcreate_esp_enc_img(${CMAKE_BINARY_DIR}/${CMAKE_PROJECT_NAME}.bin, ${project_dir}/rsa_key/private.pem, ${CMAKE_BINARY_DIR}/${CMAKE_PROJECT_NAME}.bin.enc app)
in aCMakeLists.txt
fileBuild or installation Logs.
Clean build log:
Dirty build log
It can be clearly seen that the function is never called in the second log