From 4906c17c622fb15acea9005be11c56bab70c10c7 Mon Sep 17 00:00:00 2001 From: Lei Zhang Date: Wed, 12 May 2021 11:31:01 +0000 Subject: [PATCH] Update Clang doc section for using a custom clang binary. Give better instructions on how to check the toolchain.ninja file. Change-Id: I259d29bf22b4f2858716f2a7e1c16dced2864e66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2889482 Reviewed-by: Nico Weber Commit-Queue: Nico Weber Cr-Commit-Position: refs/heads/master@{#881979} --- docs/clang.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/clang.md b/docs/clang.md index ce7cca8152e32f..c856cbdd7949a3 100644 --- a/docs/clang.md +++ b/docs/clang.md @@ -80,8 +80,8 @@ On Windows, for `clang_base_path` use something like this instead: clang_base_path = "c:/src/llvm-build" ``` -You can then run `head out/gn/toolchain.ninja` and check that the first to -lines set `cc` and `cxx` to your clang binary. If things look good, run `ninja +You can then look in `out/gn/toolchain.ninja` and check that the `rule cc` and +`rule cxx` commands run your clang binary. If things look good, run `ninja -C out/gn` to build. Chromium tries to be buildable with its currently pinned clang, and with clang