CHROMIUM OS APP FOR MAC INSTALL
Optional: You can also install API keys if you want your build to talk to some Google services, but this is not necessary for most development and testing purposes. The remaining instructions assume you have switched to the src directory: $ cd src gclient file and a directory called src in the working directory. When fetch completes, it will have created a hidden. You can call git fetch -unshallow to retrieve the full history later.Įxpect the command to take 30 minutes on even a fast connection, and many hours on slower ones. If you don't need the full repo history, you can save time by using fetch -no-history chromium. Run the fetch tool from depot_tools to check out the code and its dependencies. In System Preferences, check that “Energy Saver” -> “Power Adapter” -> “Prevent computer from sleeping automatically when the display is off” is checked so that your laptop doesn't go to sleep and interrupt the long network connection needed here.Ĭreate a chromium directory for the checkout and change to it (you can call this whatever you like and put it wherever you like, as long as the full path has no spaces): $ mkdir chromium & cd chromium Assuming you cloned depot_tools to /path/to/depot_tools (note: you must use the absolute path or Python will not be able to find infra tools): $ export PATH = "$PATH:/path/to/depot_tools" Get the codeĮnsure that unicode filenames aren't mangled by HFS: $ git config - global core. Building with a newer SDK usually works too (please fix it if it doesn't), but the releases currently use Xcode 12.2 and the macOS 11.0 SDK.Ĭlone the depot_tools repository: $ git clone https : ///chromium/tools/depot_tools.gitĪdd depot_tools to the end of your PATH (you will probably want to put this in your ~/.bash_profile or ~/.zshrc).
Run $ ls `xcode-select -p` / Platforms / MacOSX.
Avoiding the incoming network connections dialogĪ Mac running 10.15.4+, Intel or Arm.
0 kommentar(er)
