Support GOMACC_PATH env injection
Currently, compilation of simple chrome build is done like below. gomacc -> chromeos's compiler wrapper -> actual compiler binary But chromeos's compiler wrapper modifies some flags inside it before invoking actual compiler binary. This prevents goma from knowing some information for build cache sharing. To know all the flags passed to compiler binary, this change supports the way not using gomacc prefix. If we set has_gomacc_path = true, we don't prepend gomacc and lets compiler wrapper find gomacc from GOMACC_PATH env and invoke gomacc inside wrapper. By doing this, gomacc can know all the flags passed to compiler binary. This is a part of effort to share build cache between goma users for simple chrome build. chromite side change is https://chromium-review.googlesource.com/c/chromiumos/chromite/+/1140099 BUG=chromium:846610 Change-Id: I84174b12a7f286d1b911f4d0a4e167883a4891c7 Reviewed-on: https://chromium-review.googlesource.com/1151040Reviewed-by:Dirk Pranke <dpranke@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#579680}
Showing
Please register or sign in to comment