In #27472 (moved), we added export MOZILLA_OFFICIAL=1 in .mozconfig-android because we found the compiled APK wasn't releasable (it was still debuggable). This was due to MOZILLA_OFFICIAL not being set correctly at build-time. After exporting MOZILLA_OFFICIAL, the resulting APK is for release. Do we need both mk_add_options and export or do we only need export? Should we use export on the desktop builds, too?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
In #27472 (moved), we added export MOZILLA_OFFICIAL=1 in .mozconfig-android because we found the compiled APK wasn't releasable (it was still debuggable). This was due to MOZILLA_OFFICIAL not being set correctly at build-time. After exporting MOZILLA_OFFICIAL, the resulting APK is for release. Do we need both mk_add_options and export or do we only need export?
Where did you get that mk_add_options trash? From pre-esr era? Mozilla removed almost all occurences of it, read https://dxr.mozilla.org/mozilla-esr60/source/build/docs/mozconfigs.rst#31
Should we use export on the desktop builds, too?
Not you, but tbb-team, and long ago. That's #27623 (moved) now.
This looks good to me. The change is deleting non-existant options, deleting deprecated syntax, deleting comments, or adding ac_add_options --enable-proxy-bypass-protection.
This looks good to me. The change is deleting non-existant options, deleting deprecated syntax, deleting comments, or adding ac_add_options --enable-proxy-bypass-protection.
Thanks! Merged to master (commit ec79824470dcd6815ffd903c8c9974808859f9e5).