| commit | ac64044cc9cb2f99f1033232842b91f901816119 | [log] [tgz] |
|---|---|---|
| author | Mostyn Bramley-Moore <mostynb@vewd.com> | Wed May 08 06:48:44 2019 |
| committer | Mostyn Bramley-Moore <mostynb@vewd.com> | Wed May 08 06:49:25 2019 |
| tree | 9520b93b72520b539205dc6b265f612572891a6a | |
| parent | 2b8c86ad989425074655004ec3beca6e108bbe9b [diff] |
clang: only implicitly include the selected GCC multilib crtbegin.o Previously we would include up to three common crtbegin.o files that exist in the right location, and hope that one of them was correct. Since Clang tells us which multilib it selected, just upload that one. This works in more cases than the old hack. Also, if crtbegin.o is not found, then return an error (don't just log it). Change-Id: I096a362ddddc898109e8942a96e8e74ee87ef2a5
Goma is a distributed compiler service for open-source project such as Chromium and Android. It's some kind of replacement of distcc+ccache.
NOTE: currently the Goma backend is not available for non googlers. We're working so that chromium developers can use it. Stay tuned.
Goma hooks a compile request, and sends it to a backend compile server. If you have plenty of backend servers, a lot of compile can be processed in parallel, for example, -j100, -j500 or -j1000.
Also, the Goma backend caches the compile result. If the same compile request comes, the cached result is returned from the Goma cache server.
Goma client can be built on Linux, Mac, and Win.
$ gclient config https://chromium.googlesource.com/infra/goma/client $ gclient sync $ cd client
We assume the Goma client code is checked out to ${GOMA_SRC}. You can set this in your environment, but do not export it as it will make gomacc complain.
If you want to develop goma client, make goma client source unmanaged by gclient. Open .gclient file, and check "managed" value. If it's True, changed it to False. Otherwise, gclient will manage your repository, so your checkout can be unintentionally changed with gclient sync.
Move to client directory (which is under git repo), and configure git repository with your username and emails.
$ cd client $ git config user.email 'foo@example.com' $ git config user.name 'Your Name'
$ cd "${GOMA_SRC}/client" $ gclient sync $ gn gen --args='is_debug=false' out/Release $ ninja -C out/Release
The build option can be modified with gn args.
is_debug=true/false Do debug build if true. dcheck_always_on=true/false Enable DCHECK always (even in release build). is_asan=true/false Use ASan build (with clang). use_link_time_optimization=true/false Currently working only on Win. If true, /LTCG is enable. use_lld=true/false Use lld for link (it will be fast)
$ cd "${GOMA_SRC}/client" $ ./build/run_unittest.py --target=Release --build-dir=out
Follow Google code style.
For C++11 features, we prefer to follow chromium guideline: http://chromium-cpp.appspot.com/
Goma can be integrated with Chromium/Android development easily.
$ "${GOMA_SRC}/client/out/Release/goma_ctl.py" start
In Chromium src, specify the following args in gn args
use_goma = true
goma_dir = "${GOMA_SRC}/client/out/Release" (Replace ${GOMA_SRC} to your checkout)
Then build like the following:
$ cd /path/to/chromium/src/out/Release $ ninja -j100 chrome
More details are avairable in chromium's build instructions.
$ source build/envsetup.sh $ lunch aosp_arm-eng $ GOMA_DIR="${GOMA_SRC}/client/out/Release" USE_GOMA=true make -j4
Here, -j4 is not related to Goma parallelism. Android internally sets -j500 (or -j with NINJA_REMOTE_NUM_JOBS environment variable) for Goma.
compiler_proxy$ ./goma_ctl.py ensure_start
gomacc is prepended to compiler command. For example:$ gomacc clang++ -c foo.cc
make -j100, ninja -j100 or larger -j. Check http://localhost:8080 to see compiler_proxy is actually working.