mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-23 12:51:06 +00:00
297fff3aa4
On clang-cl builds, the compiler and the linker are two completely different things. The linker thankfully ignores the flags it doesn't know but it's not optimal that it has to complain about them. The historical reason we add compiler flags to linker flags is that some flags, mostly related to optimization, such as -flto or --profile-generate, need to be applied to both. This generally keeps being true for builds using clang or GCC, although ideally we'd set things separately. Anyways, generally speaking, we don't expect such flags to be necessary for host linking, so let's start by cleaning up those. This does affect all builds, but shouldn't matter. It is worth noting that commands to link target things on clang-cl builds actually use a different set of flags, so the linker doesn't end up complaining about unknown arguments there. Differential Revision: https://phabricator.services.mozilla.com/D213524 |
||
|---|---|---|
| .. | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| sites | ||
| 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