This quarterly goal involves giving mozbuild the data and smarts it needs to link libxul.

With the set of bugs that I just filed with patches, we don't have any outstanding LOCAL_INCLUDES variables in Makefile.in files unless where they depend on a variable which is not available in moz.build files. I do not know how to move those ones. Tips appreciated.

It's worth noting that comm-central still has LOCAL_INCLUDES that I don't want to move until after bug 648979 lands since I don't want to have to write more rules in my auto-path-munging portion of the script.

(In reply to comment #2) > It's worth noting that comm-central still has LOCAL_INCLUDES that I don't want > to move until after bug 648979 lands since I don't want to have to write more > rules in my auto-path-munging portion of the script. Thanks for the notice. That should not affect my work at all, so it's fine as far as I'm concerned. :-)

(In reply to :Ehsan Akhgari (needinfo? me!) (slow responsiveness, emailapocalypse) from comment #1) > With the set of bugs that I just filed with patches, we don't have any > outstanding LOCAL_INCLUDES variables in Makefile.in files unless where they > depend on a variable which is not available in moz.build files. I do not > know how to move those ones. Tips appreciated. The plan is to move the variable munging code from .mk files to Python. See bug 930703. I looked at that bug within the last 2 weeks. It likely warrants an IRC convo if you want to start working on it.

We have this ability now.