mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
6f03a33e5f
This adds a format option to mach environment and uses it in client.mk to create a .mozconfig.json in the objdir, containing all the relevant data from mozconfig. If the mozconfig doesn't change in a way that alters that data, we still skip configure. At the same time, use mach environment in place of mozconfig2configure and mozconfig2client-mk, which makes us now have only one mozconfig reader. Also, in the mozconfig reader, keep track of environment variables (as opposed to shell variables), so that changes such as a variable that was exported not being exported anymore is spotted. At the opposite, in order for irrelevant environment variable changes not to incur in re-running configure, only a set of environment variables are stored when they are unmodified. Otherwise, changes such as using a different terminal window, or even rebooting, would trigger reconfigures. Finally, make mach environment emit both MOZ_OBJDIR and OBJDIR for client.mk, and cleanup some objdir-related things in client.mk.. At the same time, make the mozconfig reader take MOZ_OBJDIR from the environment if it is defined there and not in the mozconfig. |
||
---|---|---|
.. | ||
example | ||
moz-http2 | ||
moz-spdy | ||
node-http2 | ||
node-spdy | ||
b2g_xpcshell_venv.sh | ||
head.js | ||
mach_commands.py | ||
Makefile.in | ||
moz.build | ||
README | ||
remotexpcshelltests.py | ||
runtestsb2g.py | ||
runxpcshelltests.py | ||
selftest.py | ||
xpcshell_android.ini | ||
xpcshell_b2g.ini |
Simple xpcshell-based test harness converted from netwerk/test/unit Some documentation at http://developer.mozilla.org/en/docs/Writing_xpcshell-based_unit_tests See also http://wiki.mozilla.org/SoftwareTesting:Tools:Simple_xpcshell_test_harness