docs/updating_clang.md - Issue 1544093002: Update updating_clang.md

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: docs/updating_clang.md

Issue 1544093002: Update updating_clang.md (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 5 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « no previous file | no next file » | no next file with comments »

OLD	NEW
1 # Updating clang	1 # Updating clang

2	2

3 1. Sync your Chromium tree to the latest revision to pick up any plugin	3 1. Sync your Chromium tree to the latest revision to pick up any plugin

4 changes and test the new compiler against ToT	4 changes and test the new compiler against ToT

5 1. Update clang revision in tools/clang/scripts/update.py, upload CL to	5 1. Update clang revision in tools/clang/scripts/update.py, upload CL to

6 rietveld	6 rietveld

7 1. Run tools/clang/scripts/package.py to create a tgz of the binary (mac and	7 1. Run tools/clang/scripts/package.py to create a tgz of the binary (mac and

8 linux)	8 linux)

9 1. Do a local clobber build with that clang (mac and linux). Check that	9 1. Do a local clobber build with that clang (mac and linux). Check that

10 everything builds fine and no new warnings appear. (Optional if the	10 everything builds fine and no new warnings appear. (Optional if the

11 revision picked in 1 was vetted by other means already.)	11 revision picked in 1 was vetted by other means already.)

12 1. Upload the binaries using gsutil, they will appear at	12 1. Upload the binaries using gsutil, they will appear at

13 http://commondatastorage.googleapis.com/chromium-browser-clang/index.html	13 http://commondatastorage.googleapis.com/chromium-browser-clang/index.html

14 1. Run goma package update script to push these packages to goma, send email	14 1. Run goma package update script to push these packages to goma, send email

15 1. `git cl try &&	15 1. `git cl try &&

16 git cl try -m tryserver.chromium.mac -b mac_chromium_rel_ng -b	16 git cl try -m tryserver.chromium.mac -b mac_chromium_rel_ng -b

17 mac_chromium_asan_rel_ng -b mac_chromium_gn_dbg -b ios_rel_device_ninja &&	17 mac_chromium_asan_rel_ng -b mac_chromium_gn_dbg -b ios_rel_device_ninja &&

18 git cl try -m tryserver.chromium.linux -b linux_chromium_chromeos_dbg_ng	18 git cl try -m tryserver.chromium.linux -b linux_chromium_chromeos_dbg_ng

19 -b linux_chromium_asan_rel_ng -b linux_chromium_chromeos_asan_rel_ng	19 -b linux_chromium_asan_rel_ng -b linux_chromium_chromeos_asan_rel_ng

20 -b android_clang_dbg_recipe -b linux_chromium_rel_ng	20 -b linux_chromium_rel_ng -b linux_chromium_msan_rel_ng &&

21 -b linux_chromium_msan_rel_ng &&	21 git cl try -m tryserver.chromium.android -b android_clang_dbg_recipe &&

22 git cl try -m tryserver.blink -b linux_blink_rel`	22 git cl try -m tryserver.blink -b linux_blink_rel`

23 1. Commit roll CL from the first step	23 1. Commit roll CL from the first step

24 1. The bots will now pull the prebuilt binary, and goma will have a matching	24 1. The bots will now pull the prebuilt binary, and goma will have a matching

25 binary, too.	25 binary, too.

OLD	NEW