Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-browser-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 217
    • Issues 217
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-browser-build
  • Issues
  • #29041
Closed
Open
Created Jan 10, 2019 by Georg Koppen@gkDeveloper

Compile clang closer to how Mozilla does it

We compile clang differently to how Mozilla does it: Mozilla has an elaborate setup with three stages (if needed) (see: https://hg.mozilla.org/releases/mozilla-esr60/file/248ca5c585f8/build/build-clang/build-clang.py) while we essentially "just" do what is outlined on https://clang.llvm.org/get_started.html.

We should change that and get our toolchain closer to what Mozilla provides.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking