On Mon, 24 Jan 2022 11:52:51 +0100 Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxx> wrote: > Logical is that `make clean` cleans everything done from build, not only > parts. Leaving the documentation unclean requires additional step > when building for example Debian packages: > > $ dpkg-buildpackage -us -uc > ... > dpkg-source: info: local changes detected, the modified files are: The reason we did this is because docs are not made by default. (Yes you can say the same about utest, src and samples but those are all code). I've always kept the doc build (and cleanup) separate from the normal build. Is it normal to remove the docs in other projects? -- Steve > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxx> > --- > Makefile | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Makefile b/Makefile > index 544684c1c37c..4650d15d64e9 100644 > --- a/Makefile > +++ b/Makefile > @@ -375,6 +375,7 @@ samples: libtracefs.a force > $(Q)$(call descend,$(src)/samples,all) > > clean: > + $(Q)$(call descend_clean,Documentation) > $(Q)$(call descend_clean,utest) > $(Q)$(call descend_clean,src) > $(Q)$(call descend_clean,samples)
|