Commit e549bc63 authored by Erik Chen's avatar Erik Chen Committed by Commit Bot

Specify explicit path for libtool

Bug: 971452
Change-Id: I980b4113a011d37af3ba2582883604cc40b87fe3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648736Reviewed-by: default avatarNico Weber <thakis@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#667177}
parent cd77134f
......@@ -267,15 +267,8 @@ template("mac_toolchain") {
rspfile = "{{output}}.rsp"
rspfile_content = "{{inputs_newline}}"
# libtool is part of the default path at /usr/bin/libtool. That binary is
# just a shim that calls out to xcrun to find the actual libtool. If we're
# using hermetic xcode, then we can explicitly specify the path to avoid
# invoking xcrun.
if (use_system_xcode) {
libtool = "libtool"
} else {
libtool = "$hermetic_xcode_path/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool"
}
# Specify explicit path for libtool.
libtool = "$mac_bin_path" + "libtool"
command = "$env_wrapper rm -f {{output}} && TOOL_VERSION=${tool_versions.filter_libtool} python $script $libtool -static {{arflags}} -o {{output}} -filelist $rspfile"
description = "LIBTOOL-STATIC {{output}}"
outputs = [
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment