Closed Bug 1319226 Opened 9 years ago Closed 8 years ago

Process JARManifests in the tup backend

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(firefox55 fixed)

RESOLVED FIXED
mozilla55
Tracking Status
firefox55 --- fixed

People

(Reporter: mshal, Assigned: mshal)

References

Details

Attachments

(2 files)

We'll need to handle the JARManifest moz.build objects in the tup backend. Some of the logic for these is in rules.mk, which ends up invoking the jar_maker py_action.
glandium pointed out that these can be handled easily by using the CommonBackend:_consume_jar_manifest() function, which essentially converts them into the FinalTargetFiles / FinalTargetPreprocessedFiles that the tup backend already handles.
Assignee: nobody → mshal
Comment on attachment 8871980 [details] Bug 1319226 - allow symlinks to point to files with a different basename; https://reviewboard.mozilla.org/r/143522/#review148122
Attachment #8871980 - Flags: review?(cmanchester) → review+
Attachment #8871981 - Flags: review?(cmanchester) → review+
Pushed by mshal@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9bce19249d9b allow symlinks to point to files with a different basename; r=chmanchester https://hg.mozilla.org/integration/autoland/rev/9e738d40b62d Process JARManifests in the tup backend; r=chmanchester
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: