Hi Mike
On Mon, Sep 19, 2011 at 2:59 PM, Mike Frysinger vapier@gentoo.org wrote:
On Sunday, September 18, 2011 09:08:35 Graeme Russ wrote:
On 18/09/11 18:22, Mike Frysinger wrote:
On Sunday, September 18, 2011 03:26:38 Wolfgang Denk wrote:
Mike Frysinger wrote:
The top level Makefile does not do any recursion into subdirs when cleaning, so these clean/distclean targets in random arch/board dirs never get used. Punt them all.
[snip]
Can we not have make distclean/mrproper traverse ALL arch/SoC/board directories and call their distclean/mrproper? Or have distclean/mrproper read the .mk file for all arch/SoC/board directories?
if it wasn't clear in my last e-mail, i want to move in the direction of .mk files that the top level would include them and thus all the specific cruft would be kept there
after all, the list of things to clean should be obvious once we have more kbuild style system: if it's listed as a file to build, then it should get cleaned.
'make distclean' and 'make mrproper' should delete ALL intermediate build files and basically return the local git repository to the same state that it would be in if you did a fresh git-clone regardless of what config options git set. So if one does:
make board_x-config make all cp u-boot.bin <somewhere> make board_y-config make all cp u-boot.bin <somewhere else> make mrproper
nothing should be left over from the build of 'board_x', even if it is a completely different arch that 'board_y'
The list of files to delete should be in the board_x and board_y config.mk files. Similiarly for arches and SoCs
Regards,
Graeme