chore(core): add clean_prodtest_emu makefile target, add it to clean
What changed, and why it matters
This commit only adds a missing cleanup step in the project's build Makefile. It ensures that when developers run 'make clean', a newly introduced emulator build directory for the production-test tool is also deleted. There is no change to device firmware, no security fix, and no vulnerability.
No security action needed. Treat as routine build maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies core/Makefile to include clean_prodtest_emu in the aggregate clean target and defines a new clean_prodtest_emu rule that removes $(PRODTEST_EMU_BUILD_DIR). This is a build-hygiene chore with no functional or security-relevant code changes.
Changed components
core/MakefileInspect captured patch +4 / −1
diff --git a/core/Makefile b/core/Makefile
index 22a7d28fa..a364993c4 100644
--- a/core/Makefile
+++ b/core/Makefile
@@ -347,7 +347,7 @@ build_cross: ## build mpy-cross port
## clean commands:
clean: clean_boardloader clean_bootloader clean_bootloader_emu clean_bootloader_ci \
- clean_prodtest clean_firmware clean_kernel clean_secmon clean_unix clean_cross ## clean all
+ clean_prodtest clean_prodtest_emu clean_firmware clean_kernel clean_secmon clean_unix clean_cross ## clean all
rm -f ".sconsign.dblite"
clean_boardloader: ## clean boardloader build
@@ -365,6 +365,9 @@ clean_bootloader_emu: ## clean bootloader_emu build
clean_prodtest: ## clean prodtest build
rm -rf $(PRODTEST_BUILD_DIR)
+clean_prodtest_emu: ## clean prodtest_emu build
+ rm -rf $(PRODTEST_EMU_BUILD_DIR)
+
clean_secmon: ## clean security monitor build
rm -rf $(SECMON_BUILD_DIR)
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.