OLD | NEW |
---|---|
1 #!/usr/bin/env bash | 1 #!/usr/bin/env bash |
2 # Copyright (c) 2012 The Chromium Authors. All rights reserved. | 2 # Copyright (c) 2012 The Chromium Authors. All rights reserved. |
3 # Use of this source code is governed by a BSD-style license that can be | 3 # Use of this source code is governed by a BSD-style license that can be |
4 # found in the LICENSE file. | 4 # found in the LICENSE file. |
5 | 5 |
6 # This script will check out llvm and clang into third_party/llvm and build it. | 6 # This script will check out llvm and clang into third_party/llvm and build it. |
7 | 7 |
8 # Do NOT CHANGE this if you don't know what you're doing -- see | 8 # Do NOT CHANGE this if you don't know what you're doing -- see |
9 # https://code.google.com/p/chromium/wiki/UpdatingClang | 9 # https://code.google.com/p/chromium/wiki/UpdatingClang |
10 # Reverting problematic clang rolls is safe, though. | 10 # Reverting problematic clang rolls is safe, though. |
(...skipping 279 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
290 cd "${LLVM_BUILD_DIR}" | 290 cd "${LLVM_BUILD_DIR}" |
291 make -C tools/clang/runtime/ \ | 291 make -C tools/clang/runtime/ \ |
292 LLVM_ANDROID_TOOLCHAIN_DIR="../../../llvm-build/android-toolchain" | 292 LLVM_ANDROID_TOOLCHAIN_DIR="../../../llvm-build/android-toolchain" |
293 cd - | 293 cd - |
294 fi | 294 fi |
295 | 295 |
296 # Build Chrome-specific clang tools. Paths in this list should be relative to | 296 # Build Chrome-specific clang tools. Paths in this list should be relative to |
297 # tools/clang. | 297 # tools/clang. |
298 # For each tool directory, copy it into the clang tree and use clang's build | 298 # For each tool directory, copy it into the clang tree and use clang's build |
299 # system to compile it. | 299 # system to compile it. |
300 for CHROME_TOOL_DIR in ${chrome_tools}; do | 300 for CHROME_TOOL_DIR in ${chrome_tools}; do |
hans
2014/01/21 21:22:12
It looks like this for loop only runs one iteratio
| |
301 TOOL_SRC_DIR="${THIS_DIR}/../${CHROME_TOOL_DIR}" | 301 TOOL_SRC_DIR="${THIS_DIR}/../${CHROME_TOOL_DIR}" |
302 TOOL_DST_DIR="${LLVM_DIR}/tools/clang/tools/chrome-${CHROME_TOOL_DIR}" | 302 TOOL_DST_DIR="${LLVM_DIR}/tools/clang/tools/chrome-${CHROME_TOOL_DIR}" |
303 TOOL_BUILD_DIR="${LLVM_BUILD_DIR}/tools/clang/tools/chrome-${CHROME_TOOL_DIR}" | 303 TOOL_BUILD_DIR="${LLVM_BUILD_DIR}/tools/clang/tools/chrome-${CHROME_TOOL_DIR}" |
304 rm -rf "${TOOL_DST_DIR}" | 304 rm -rf "${TOOL_DST_DIR}" |
305 cp -R "${TOOL_SRC_DIR}" "${TOOL_DST_DIR}" | 305 cp -R "${TOOL_SRC_DIR}" "${TOOL_DST_DIR}" |
306 rm -rf "${TOOL_BUILD_DIR}" | 306 rm -rf "${TOOL_BUILD_DIR}" |
307 mkdir -p "${TOOL_BUILD_DIR}" | 307 mkdir -p "${TOOL_BUILD_DIR}" |
308 cp "${TOOL_SRC_DIR}/Makefile" "${TOOL_BUILD_DIR}" | 308 cp "${TOOL_SRC_DIR}/Makefile" "${TOOL_BUILD_DIR}" |
Nico
2014/01/21 21:08:49
I thought it would get build here. Maybe the new p
| |
309 MACOSX_DEPLOYMENT_TARGET=10.5 make -j"${NUM_JOBS}" -C "${TOOL_BUILD_DIR}" | 309 MACOSX_DEPLOYMENT_TARGET=10.5 make -j"${NUM_JOBS}" -C "${TOOL_BUILD_DIR}" |
310 done | 310 done |
311 | 311 |
312 if [[ -n "$run_tests" ]]; then | 312 if [[ -n "$run_tests" ]]; then |
313 # Run a few tests. | 313 # Run a few tests. |
314 PLUGIN_SRC_DIR="${THIS_DIR}/../plugins" | 314 for CHROME_TOOL_DIR in ${chrome_tools}; do |
315 "${PLUGIN_SRC_DIR}/tests/test.sh" "${LLVM_BUILD_DIR}/Release+Asserts" | 315 TOOL_SRC_DIR="${THIS_DIR}/../${CHROME_TOOL_DIR}" |
316 if [[ -f "${TOOL_SRC_DIR}/tests/test.sh" ]]; then | |
317 "${TOOL_SRC_DIR}/tests/test.sh" "${LLVM_BUILD_DIR}/Release+Asserts" | |
318 fi | |
319 done | |
316 cd "${LLVM_BUILD_DIR}" | 320 cd "${LLVM_BUILD_DIR}" |
317 make check-all | 321 make check-all |
318 cd - | 322 cd - |
319 fi | 323 fi |
320 | 324 |
321 # After everything is done, log success for this revision. | 325 # After everything is done, log success for this revision. |
322 echo "${CLANG_REVISION}" > "${STAMP_FILE}" | 326 echo "${CLANG_REVISION}" > "${STAMP_FILE}" |
OLD | NEW |