Add asan-specific CleanSpec
ASAN builds run as two consecutive builds. The cleanspec is applied by the first one, which cleans the obj directory, and ignored by the second. This can result in old entries in the obj_asan directory. Test: obj_asan dirs are deleted Change-Id: I54b8ec9cff581fcd9ec2a843aa7126805340c387
This commit is contained in:
parent
2d1cddd567
commit
4e2da3277a
1 changed files with 5 additions and 0 deletions
|
@ -475,6 +475,11 @@ $(call add-clean-step, rm -rf $(TARGET_OUT_COMMON_INTERMEDIATES)/APPS/*_intermed
|
|||
$(call add-clean-step, rm -rf $(TARGET_OUT_COMMON_INTERMEDIATES)/JAVA_LIBRARIES/*_intermediates/java-source-list)
|
||||
$(call add-clean-step, rm -rf $(OUT_DOCS)/*-timestamp)
|
||||
|
||||
$(call add-clean-step, rm -rf $(TARGET_COMMON_OUT_ROOT)/obj_asan/APPS/*_intermediates/src)
|
||||
$(call add-clean-step, rm -rf $(TARGET_COMMON_OUT_ROOT)/obj_asan/JAVA_LIBRARIES/*_intermediates/src)
|
||||
$(call add-clean-step, rm -rf $(TARGET_COMMON_OUT_ROOT)/obj_asan/APPS/*_intermediates/java-source-list)
|
||||
$(call add-clean-step, rm -rf $(TARGET_COMMON_OUT_ROOT)/obj_asan/JAVA_LIBRARIES/*_intermediates/java-source-list)
|
||||
|
||||
# ************************************************
|
||||
# NEWER CLEAN STEPS MUST BE AT THE END OF THE LIST
|
||||
# ************************************************
|
||||
|
|
Loading…
Reference in a new issue