Yeah, I'm pretty sure we need to make sure "parent" moz.builds need to be read before "child" moz.builds. So in this case, the `moz.build` files need to be read in this order: ``` moz.build accessible/moz.build accessible/interfaces/moz.build accessible/interfaces/ia2/moz.build ``` There's an algorithm that already yields moz.builds in this order in the `find_relevant_mozbuilds` function: https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/frontend/reader.py#1243 Though not sure if you can repurpose that for your use case or ont. Note, it would be helpful if you changed `all_mozbuild_paths` to yield them in an order that doesn't break things.
Bug 1580914 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yeah, I'm pretty sure we need to make sure "parent" moz.builds need to be read before "child" moz.builds. So in this case, the `moz.build` files need to be read in this order: ``` moz.build accessible/moz.build accessible/interfaces/moz.build accessible/interfaces/ia2/moz.build ``` There's an algorithm that already yields moz.builds in this order in the `find_relevant_mozbuilds` function: https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/frontend/reader.py#1243 Though not sure if you can repurpose that for your use case or not. Note, it would be helpful if you changed `all_mozbuild_paths` to yield them in an order that doesn't break things.