Currently, this is what happens when we do directory traversal for $target: - do a bit of $target in current directory - do $target in PARALLEL_DIRS - do a bit more $target in current directory - do $target in DIRS - do a bit more $target in current directory The fun part is that some parts of the build rely on this weird order so that we effectively have some directories relying on their parents having been built and some others relying on their children having been built. Which is all too fragile, and gets in the way of pseudo-derecursification. I have a WiP that changes the order to: - do $target in the current directory - do $target in PARALLEL_DIRS - do $target in DIRS which I /think/ is the order that requires fixing up the less.

This builds fine on linux, I'm pretty sure it will fail on windows and android (from different past experiments)

As mentioned on irc, i didn't feel like spending time actually fixing those awful rules.

Comment on attachment 799481 [details] [diff] [review] Always traverse sub-directories after executing rules in the current directory Review of attachment 799481 [details] [diff] [review]: ----------------------------------------------------------------- Don't forget to add license headers to the new files.

Comment on attachment 799481 [details] [diff] [review] Always traverse sub-directories after executing rules in the current directory Review of attachment 799481 [details] [diff] [review]: ----------------------------------------------------------------- Nice. This may also unbust bug 909508 and some other NONRECURSIVE_* rules issues. ::: config/recurse.mk @@ +1,1 @@ > +ifndef INCLUDED_RULES_MK Moar MPL.

https://hg.mozilla.org/integration/mozilla-inbound/rev/fc9fb405796e https://hg.mozilla.org/integration/mozilla-inbound/rev/0413092be43d

https://hg.mozilla.org/mozilla-central/rev/fc9fb405796e https://hg.mozilla.org/mozilla-central/rev/0413092be43d Note that this appears to have caused intermittent Android build bustage in bug 913134.