Dear Mike Frysinger, In message <201109190059.55664.vap...@gentoo.org> you wrote: > > 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
Why should we do that? Having all build rules in a single, huge Makefile does not sound like something that is desirable (and in this context it does not make any difference if the file is actually a concatenation of all these build rules, or if it's hidden in a set of [probably even nested] includes). I'm still a big friend of organizing complex stuff in small, hierarchical structured pieces, so I have to u nderstand it only a small bit at a time. Yes, running a number of nested makes may have some performance penalty. But frankly: I care a ship about that when I can have the sofware design simpler and easier to maintain. > 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. Keep in mind that you said yourslef we always want to remove _all_ build results - this includes evne those not "listed as a file to buil" for a specific configuration setting. 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 Here is an Appalachian version of management's answer to those who are concerned with the fate of the project: "Don't worry about the mule. Just load the wagon." - Mike Dennison's hillbilly uncle _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
