Tests are split into multiple test targets based on their type and where they exist in the directory structure. This means if you launch Chrome from an SSH session, the UI output will be available in Chrome Remote Desktop. X11 - unix - maxdepth 1 - mindepth 1 - name 'X*' | Rather, you should use either $HOME or the absolute path: $ export PATH = "$PATH:$" ]] then export DISPLAY =: $ (įind / tmp /. When cloning depot_tools to your home directory do not use ~ on PATH, otherwise gclient runhooks will fail to run.
Assuming you cloned depot_tools to /path/to/depot_tools: $ export PATH = "$PATH:/path/to/depot_tools" Install depot_toolsĬ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 ~/.bashrc or ~/.zshrc). See this bug for additional details on this. There may be additional Docker-specific issues during compilation. If you choose to compile from within a container for whatever reason, you will need to make sure that the following tools are available: While it is not a common setup, Chromium compilation should work from within a Docker container. There are some instructions for other distros below, but they are mostly unsupported. Most development is done on Ubuntu (currently 18.04, Bionic Beaver).
0 kommentar(er)
