diff options
| author | andybons <andybons@chromium.org> | 2015-08-24 14:37:09 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-08-24 21:39:36 +0000 |
| commit | 3322f7611ba1444e553b2cce4de3a1a32ad46e72 (patch) | |
| tree | dfb6bbea413da0581b8d085b184a5e6ceea5af3e /docs/updating_clang.md | |
| parent | 5d58c9eb2baa203be1b84ac88cde82c59d72f143 (diff) | |
| download | chromium_src-3322f7611ba1444e553b2cce4de3a1a32ad46e72.zip chromium_src-3322f7611ba1444e553b2cce4de3a1a32ad46e72.tar.gz chromium_src-3322f7611ba1444e553b2cce4de3a1a32ad46e72.tar.bz2 | |
Per https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/irLAQ8f8uGk
Initial migration of wiki content over to src/docs
There will be a follow-up CL to ensure docs are following chromium’s style guide, links are fixed, etc. The file auditing was becoming too much for a single change and per Nico’s suggestion, it seems to be better to do
+ Bulk import with initial prune.
+ Follow-up CLs to clean up the documentation.
So that each CL has its own purpose.
BUG=none
Review URL: https://codereview.chromium.org/1309473002
Cr-Commit-Position: refs/heads/master@{#345186}
Diffstat (limited to 'docs/updating_clang.md')
| -rw-r--r-- | docs/updating_clang.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/updating_clang.md b/docs/updating_clang.md new file mode 100644 index 0000000..1721dce --- /dev/null +++ b/docs/updating_clang.md @@ -0,0 +1,11 @@ +# Updating clang + + 1. Sync your Chromium tree to the latest revision to pick up any plugin changes and test the new compiler against ToT + 1. Update clang revision in tools/clang/scripts/update.sh, upload CL to rietveld + 1. Run tools/clang/scripts/package.py to create a tgz of the binary (mac and linux) + 1. Do a local clobber build with that clang (mac and linux). Check that everything builds fine and no new warnings appear. (Optional if the revision picked in 1 was vetted by other means already.) + 1. Upload the binaries using gsutil, they will appear at http://commondatastorage.googleapis.com/chromium-browser-clang/index.html + 1. Run goma package update script to push these packages to goma, send email + 1. `git cl try -m tryserver.chromium.mac -b mac_chromium_rel_ng -b mac_chromium_asan_rel_ng -b mac_chromium_gn_dbg -b ios_rel_device_ninja && git cl try -m tryserver.chromium.linux -b linux_chromium_gn_dbg -b linux_chromium_chromeos_dbg_ng -b linux_chromium_asan_rel_ng -b linux_chromium_chromeos_asan_rel_ng -b android_clang_dbg_recipe -b linux_chromium_trusty32_rel -b linux_chromium_rel_ng && git cl try -m tryserver.blink -b linux_blink_rel` + 1. Commit roll CL from the first step + 1. The bots will now pull the prebuilt binary, and goma will have a matching binary, too.
\ No newline at end of file |