Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor Browser
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,529
    • Issues 1,529
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #27493

Closed
Open
Opened Sep 06, 2018 by Matthew Finkel@sysrqbDeveloper

'mk_add_options' or 'export' MOZILLA_OFFICIAL

In legacy/trac#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
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/applications/tor-browser#27493