At the moment, "make distclean" relies on the TARGET_DIRS variable, set by
configure. The problem is that this variable does not always contain all
possible targets.
For example, the following will leave build data in the tree:
./configure && make && ./configure --target-list=i386-softmmu \
&& ma
Alexandre Raymond writes:
> At the moment, "make distclean" relies on the TARGET_DIRS variable, set by
> configure. The problem is that this variable does not always contain all
> possible targets.
>
> For example, the following will leave build data in the tree:
>
> ./configure && make && ./conf
Hi Markus,
> Well, I'd expect distclean to remove exactly what *this* makefile can
> build, and leave everything else alone.
I was expecting "distclean" to bring back the source directory to
however it was after checkout, removing anything that might have been
created by the build/configure proce
Alexandre Raymond writes:
> Hi Markus,
>
>> Well, I'd expect distclean to remove exactly what *this* makefile can
>> build, and leave everything else alone.
>
> I was expecting "distclean" to bring back the source directory to
> however it was after checkout, removing anything that might have bee
> There are many more object files that are built conditionally. Why is
> it okay not to delete them?
Perhaps they should be deleted too...
The GNU Make manual says the following about "distclean":
http://www.gnu.org/s/hello/manual/make/Standard-Targets.html
"Delete all files in the current dir
