infer_clone/infer/lib/xcode_wrappers/clang

#!/bin/bash

SCRIPT_PATH="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
BIN_PATH="${SCRIPT_PATH}/../../bin"

if [ "${0%++}" != "$0" ]; then XX="++"; else XX=""; fi

"${BIN_PATH}/InferClang${XX}" "$@"
initial synchronization 10 years ago			`#!/bin/bash`

			`SCRIPT_PATH="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"`
[clang] convert filter_args_and_run_fcp_clang to OCaml Summary: This also adds `-a compile` support to `InferClang`. This is needed for the `xcodebuild` integration, which is hard to fold into the same binary as the rest. Reviewed By: jberdine Differential Revision: D4008262 fbshipit-source-id: 0bbd53f 8 years ago			`BIN_PATH="${SCRIPT_PATH}/../../bin"`
initial synchronization 10 years ago
[clang] Remove INFER_XX environment variable Summary: InferClang knows what to do if its name ends in ++. So it is not necessary to pass whether or not the original clang executable ended in ++ to InferClang using the the INFER_XX environment variable. Instead, create an InferClang++ symbolic link and make the clang wrapper call either InferClang or InferClang++ as needed. Reviewed By: jvillard Differential Revision: D4078416 fbshipit-source-id: 3b5d5d0 8 years ago			`if [ "${0%++}" != "$0" ]; then XX="++"; else XX=""; fi`
initial synchronization 10 years ago
[clang] Remove INFER_XX environment variable Summary: InferClang knows what to do if its name ends in ++. So it is not necessary to pass whether or not the original clang executable ended in ++ to InferClang using the the INFER_XX environment variable. Instead, create an InferClang++ symbolic link and make the clang wrapper call either InferClang or InferClang++ as needed. Reviewed By: jvillard Differential Revision: D4078416 fbshipit-source-id: 3b5d5d0 8 years ago			`"${BIN_PATH}/InferClang${XX}" "$@"`