Closed
Bug 1432643
Opened 7 years ago
Closed 7 years ago
Prevent gn configs from multiple project overwriting one another
Categories
(Firefox Build System :: General, enhancement)
Firefox Build System
General
Tracking
(firefox60 fixed)
RESOLVED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: chmanchester, Assigned: chmanchester)
References
Details
Attachments
(1 file)
Sharing a single directory in the objdir for `gn gen` output simply doesn't work in the presence of multiple gn projects in the tree.
Comment hidden (mozreview-request) |
Comment 2•7 years ago
|
||
mozreview-review |
Comment on attachment 8944933 [details]
Bug 1432643 - Store `gn gen` output in the objdir per project.
https://reviewboard.mozilla.org/r/215076/#review221792
There are a ton of hits for `gn-output` in the tree. Why doesn't https://searchfox.org/mozilla-central/search?q=gn-output&path= need to be updated? (It kind of looks like $objdir was intended to be $topobjdir, so it's correct after your patch by being incorrect now. Yay?)
There's a number of JSON files checked into the tree that must have been generated by dminor. Do they need to be revved? Should dminor review this?
If you're happy with these issues, r+ to avoid a re-review cycle.
Attachment #8944933 -
Flags: review+
Updated•7 years ago
|
Attachment #8944933 -
Flags: review?(core-build-config-reviews)
Assignee | ||
Comment 3•7 years ago
|
||
mozreview-review-reply |
Comment on attachment 8944933 [details]
Bug 1432643 - Store `gn gen` output in the objdir per project.
https://reviewboard.mozilla.org/r/215076/#review221792
I don't think the differences we end up causing in the JSON configs will be an issue. This is the destination for the generated JSON config, the paths aren't ending up in the generated moz.build files.
Pushed by cmanchester@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/59ac85f05650
Store `gn gen` output in the objdir per project. r=nalexander
Comment 5•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
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
•