New: make clean/distclean does not remove BR2_DL_DIR and BR2_HOST_DIR

https://bugs.busybox.net/show_bug.cgi?id=12276

Bug ID: 12276
Summary: make clean/distclean does not remove BR2_DL_DIR and
BR2_HOST_DIR
Product: buildroot
Version: 2019.08.1
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: br-max at re-gister.com
CC: buildroot at uclibc.org
Target Milestone: ---

If the buildroot configuration has a custom BR2_DL_DIR and/or BR2_HOST_DIR (in my case it points to a path outside of the buildroot tree), then the 'make clean' and 'make distclean' commands do not remove the content of these directories.

Is it a bug or normal behaviour that custom download and host directories are excluded from the cleanup?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12276

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #1 from Thomas Petazzoni <[email protected]> --- For BR2_DL_DIR, this is clearly an intended behavior.

However, for BR2_HOST_DIR, it does remove it properly. See:

$ grep ^BR2_HOST_DIR .config
BR2_HOST_DIR="/tmp/foobar-host"

$ ls /tmp/foobar-host/
arm-buildroot-linux-uclibcgnueabi  bin  etc  include  lib  lib64  opt  share 
usr

$ make clean
rm -rf /home/thomas/projets/buildroot/output/target
/home/thomas/projets/buildroot/output/images /tmp/foobar-host
/home/thomas/projets/buildroot/output/host \
        /home/thomas/projets/buildroot/output/build
/home/thomas/projets/buildroot/output/staging \
        /home/thomas/projets/buildroot/output/legal-info
/home/thomas/projets/buildroot/output/graphs

$ ls /tmp/foobar-host/
ls: cannot access '/tmp/foobar-host/': No such file or directory

I used "make clean", but "make distclean" implies "make clean".

So I think it all works as intended.

You are receiving this mail because:
You are on the CC list for the bug.