mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-21 01:05:45 +00:00
ecd47d34f4
When building Gecko/Android/aarch64 on Windows, `--target` parameter may not be incorrect value. Although `check_compiler`'s `info` is target compiler, clang on Windows is always detected as `clang-cl`, not `clang`. ``` c:/Users/mkato/.mozbuild/clang/bin/clang.exe -E -dM - < /dev/null ... #define _MSC_VER 1916 ``` So even if using clang on Windows, not clang-cl, we should detect as 'clang' correctly Differential Revision: https://phabricator.services.mozilla.com/D36422 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
docs | ||
l10n | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
safety | ||
mach_commands.py | ||
moz.build | ||
README |
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025