Closed
Bug 1632874
Opened 6 years ago
Closed 6 years ago
Mach bootstrap should write the mozconfig file for you if no such file exists and no MOZCONFIG env var is set and the user chooses a setup option that requires custom build options
Categories
(Firefox Build System :: Bootstrap Configuration, enhancement, P3)
Firefox Build System
Bootstrap Configuration
Tracking
(firefox79 fixed)
RESOLVED
FIXED
mozilla79
| Tracking | Status | |
|---|---|---|
| firefox79 | --- | fixed |
People
(Reporter: Gijs, Assigned: mhentges)
References
Details
Attachments
(2 files)
Some students Mike and I mentored gave us feedback about this, and I've seen other people I've mentored in the past tell me they definitely were using artifact builds... and they weren't.
If there is no existing file and no env var set, and we're run from the source dir, it seems safe to create such a file (and tell the user it's been created).
| Reporter | ||
Comment 1•6 years ago
|
||
Clarifying the summary a bit. AIUI, we'd be wanting to write the mozconfig for both types of artifact builds as well as geckoview non-artifact builds.
Summary: Mach bootstrap should write the mozconfig file for you if no such file exists and no MOZOCNFIG env var is set and the user configures builds that need specific options → Mach bootstrap should write the mozconfig file for you if no such file exists and no MOZOCNFIG env var is set and the user chooses a setup option that requires custom build options
| Reporter | ||
Updated•6 years ago
|
Summary: Mach bootstrap should write the mozconfig file for you if no such file exists and no MOZOCNFIG env var is set and the user chooses a setup option that requires custom build options → Mach bootstrap should write the mozconfig file for you if no such file exists and no MOZCONFIG env var is set and the user chooses a setup option that requires custom build options
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Assignee: nobody → mhentges
Updated•6 years ago
|
Severity: -- → S3
| Assignee | ||
Comment 2•6 years ago
|
||
Rather than always printing instructions at the end of the bootstrap phase, we will now create a mozconfig
file if one doesn't exist and there's configuration to be written.
Pushed by mhentges@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c9c52538d77d
|mach bootstrap| should write mozconfig file if it doesn't exist r=rstewart
Comment 4•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
| Assignee | ||
Comment 5•6 years ago
|
||
Pushed by mhentges@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cbd35ab77253
Update docs since mozconfig file is automatically created r=agi,geckoview-reviewers
Comment 7•6 years ago
|
||
| bugherder | ||
You need to log in
before you can comment on or make changes to this bug.
Description
•