gecko-dev/build/build-clang/macosx64.json

{
    "target": "x86_64-apple-darwin"
}
Bug 1745115 - Refactor clang configs. r=firefox-build-system-reviewers,andi We separate the patchset from the per-platform configuration, which will ensure we keep the same patchset across them (spoiler alert: we weren't). Also, as most builds are PGO, use that in per-platform configurations, and add an override config that sets it back to 2-stages for the builds we don't want to PGO. Differential Revision: https://phabricator.services.mozilla.com/D133317 2021-12-10 03:29:58 +03:00			`{`
Bug 1915778 - Clean up the clang toolchain json configs. r=firefox-build-system-reviewers,sergesanspaille By separating the "use this compiler" configuration from other items, we avoid redundancies, and at the same time simplify how the aarch64 variants are configured by having the $os_variant.json files only contain the `target`. Overall, each build now only uses at most 4 configs: - one for the compiler it uses - one for the target (optional when the host is the same as the target) - one for the patches applied to the clang/llvm source - one for the build type (stage-1, profile or stage-4-pgo) And a similar pattern for clang-tidy. Also remove the setting for ld, which hasn't been used since bug 1799423, and ranlib and ar for builds using clang-cl, as it's not used either. Differential Revision: https://phabricator.services.mozilla.com/D220652 2024-09-04 08:43:03 +03:00			`"target": "x86_64-apple-darwin"`
Bug 1745115 - Refactor clang configs. r=firefox-build-system-reviewers,andi We separate the patchset from the per-platform configuration, which will ensure we keep the same patchset across them (spoiler alert: we weren't). Also, as most builds are PGO, use that in per-platform configurations, and add an override config that sets it back to 2-stages for the builds we don't want to PGO. Differential Revision: https://phabricator.services.mozilla.com/D133317 2021-12-10 03:29:58 +03:00			`}`