Dear Michael Schwingen, In message <4dc5259c.7040...@discworld.dascon.de> you wrote: > > If I put rules in arch/arm/config.mk, then the first of these rules > becomes the default rule which is executed in subdir makes (like "make > -C arch"), which breaks compilation completely, since config.mk is > included before the rules are defined in the subdir Makefiles.
You are not suppoed to put any make rules in config.mk files. > It seems the current scheme allows only variable definitions in > config.mk files, which is not sufficient here. As the name implies, these files contain configuration (= variable) settings. Nothing else. > rules.mk would be fine, however, there is no provision to include rules > from lower directories, since all the building in subdirectories is > handled by recursively calling make (this is one of the problems that > arise by recursively calling make for each directory, but that is a > different topic). But lower level directories inherit all settings from the top level Makefile? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de It's a small world, but I wouldn't want to paint it. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
