Closed Bug 1544568 Opened 7 months ago Closed 7 months ago

cleanup how runtime libraries are built in build-clang


(Firefox Build System :: Toolchains, task)

Not set


(firefox68 fixed)

Tracking Status
firefox68 --- fixed


(Reporter: froydnj, Assigned: froydnj)




(4 files)

I had to write all these while trying to get arm64 linux fuzzing patches working; we might as well get these landed as a part of a separate bug.

The setup for compiler-rt is currently done before the stage 2 build,
which happens to be the final stage for our android runtime libraries
build. But we may also want to build runtime libraries on 3-stage
bootstrap builds, in which case we don't want compiler-rt to be active
for the second stage. Move the setup into build_one_stage so that the
setup is controllable by is_final_stage, which is set in all the place
that we care about.

We don't need them and we might as well be explicit about not building them.

Depends on D27592

android_targets here is a dict, not a sequence, and while iter on a
dict object implicitly means dict.iterkeys(), that's not really
obvious. We should instead be explicit about what we're doing here.

Depends on D27593

It seems better to set switches enabling runtime libraries and switches
enabling runtime libraries to build in different places, as future
changes might only enable runtime libraries for certain targets, but not
need any special switches for building.

Depends on D27594

Type: defect → task
Pushed by
move compiler-rt runtimes setup into build_one_stage; r=firefox-build-system-reviewers,chmanchester
don't build XRay libraries; r=firefox-build-system-reviewers,chmanchester
make setting of `LLVM_*_TARGETS` more explicit; r=firefox-build-system-reviewers,chmanchester
pull out runtime library-related settings in; r=firefox-build-system-reviewers,chmanchester
You need to log in before you can comment on or make changes to this bug.