Closed
Bug 1259876
Opened 9 years ago
Closed 9 years ago
A define in mobile/android/installer/moz.build will not make it to mobile/android/installer/package-manifest.in
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: chmanchester, Assigned: chmanchester)
References
Details
Attachments
(1 file)
This moz.build actually isn't read, because no parent has 'installer' in dirs (right now it's empty, so that's fine). But even with that, mobile/android/installer/Makefile.in defines STANDALONE_MAKEFILE, so backend.mk isn't included once we generate it.
Assignee | ||
Comment 1•9 years ago
|
||
... but since that's the only thing setting STANDALONE_MAKEFILE does, we can just leave that out.
Assignee: nobody → cmanchester
Assignee | ||
Comment 2•9 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/42517/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/42517/
Attachment #8735013 -
Flags: review?(nalexander)
Comment on attachment 8735013 [details]
MozReview Request: Bug 1259876 - Ensure defines in mobile/android/installer/moz.build make it to mobile/android/installer/package-manifest.in. r=nalexander
https://reviewboard.mozilla.org/r/42517/#review39031
I'm fine with this, but none of the other `installer/Makefile.in` need it. Perhaps the l10n preprocessing shoudl be happening somewhere else?
Attachment #8735013 -
Flags: review?(nalexander) → review+
Comment 4•9 years ago
|
||
You probably don't want to open the can of worms that adding a moz.build to an installer directory is.
It might work, but that would be luck, and would be pretty much fragile.
Updated•9 years ago
|
Attachment #8735013 -
Flags: review-
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•