Searched refs:clean (Results 1 – 25 of 34) sorted by relevance
12
15 .PHONY: help clean apidoc breathe_apidoc Makefile18 clean: target24 @$(SPHINXBUILD) -M clean "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
62 make clean72 make clean106 make clean126 make clean
87 make clean
70 make clean >/dev/null
118 neat: clean
21 .PHONY: all no_test programs lib tests install uninstall clean test check lcov apidoc apidoc_clean149 clean: clean_more_on_top target150 $(MAKE) -C library clean151 $(MAKE) -C programs clean152 $(MAKE) -C tests clean
22 .PHONY: all check test clean42 clean: target
74 make clean241 make clean
276 --restore First clean up the build tree, restoring backed up316 command make clean414 make clean2036 make clean2259 make clean4449 make clean4840 make clean4847 make clean4856 make clean4867 make clean[all …]
19 clean: target
15 clean: target
24 clean: target
47 clean: target
101 clean)
241 ./script/gcda-tool clean697 clean)
14 git clean -xfd
17 ./script/test clean build cert tests/scripts/thread-cert/Cert_5_1_01_RouterAttach.py
228 .PHONY: all static shared clean388 clean: target398 neat: clean
29 make clean
109 .PHONY: all check test clean169 clean: target
109 .PHONY: all clean list fuzz417 clean: target428 $(MAKE) -C fuzz clean
102 * clean build and to ensure that tests treating warnings as errors do not
102 RUN apt-get purge -y unzip wget git && apt-get -y autoremove && apt-get -y clean && rm -rf /var/lib…
115 When code should clean up resources, how do we know that they have truly been cleaned up?145 …metimes. For example, the main purpose of `mbedtls_psa_crypto_free` is to clean up all resources i…288 …jobs with a memory leak detector, each test function or test program must clean up after itself. U…
86 Prior to submitting your pull request, you might want to do a few things to clean up your branch an…
