lldb/test/Shell/BuildScript/compiler-full-path.test

RUN: %build -n --mode=compile --verbose --arch=64 --compiler=/path/to/my/clang \
RUN:    -o foo foobar.c | FileCheck %s --check-prefix=CHECK-CLANG
RUN: %build -n --mode=compile --verbose --arch=64 \
RUN:    --compiler=/path/to/my/x64/cl.exe -o foo foobar.c | \
RUN:    FileCheck %s --check-prefix=CHECK-MSVC

CHECK-CLANG: Command Line: /path/to/my/clang
CHECK-SAME: -o

CHECK-MSVC: Command Line: /path/to/my{{(\/|\\)(arm64|x64)(\/|\\)}}cl.exe
CHECK-SAME: /Fo
[lldb] [lit] Pass --mode=compile to fix compiler-full-path.test Pass '--mode=compile' to fix compiler-full-path.test failure on NetBSD buildbot (apparently due to lack of 'link' executable). Fixes r360355. Acked by Pavel Labath. llvm-svn: 360761 2019-05-15 10:48:55 +00:00			`RUN: %build -n --mode=compile --verbose --arch=64 --compiler=/path/to/my/clang \`
			`RUN: -o foo foobar.c \| FileCheck %s --check-prefix=CHECK-CLANG`
			`RUN: %build -n --mode=compile --verbose --arch=64 \`
			`RUN: --compiler=/path/to/my/x64/cl.exe -o foo foobar.c \| \`
			`RUN: FileCheck %s --check-prefix=CHECK-MSVC`
[lldb] build.py: fix behavior when passing --compiler=/path/to/compiler All the other paths in the find_toolchain function return a tuple (detected_toolchain_type, compiler_path), but when the parameter to --compiler is not one of the predefined names it only returns the detected toolchain type, which causes an error when trying to unpack the result. This patch changes it to return also the compiler path passed as a parameter. Differential Revision: https://reviews.llvm.org/D61713 llvm-svn: 360355 2019-05-09 16:47:07 +00:00
			`CHECK-CLANG: Command Line: /path/to/my/clang`
			`CHECK-SAME: -o`

[LLDB] Adjust compiler-full-path.test for Windows/Arm64 This patch updates compiler-full-path.test to make sure it passes on Windows Arm64 platform with MSVC. 2021-11-09 19:33:07 +00:00			`CHECK-MSVC: Command Line: /path/to/my{{(\/\|\\)(arm64\|x64)(\/\|\\)}}cl.exe`
[lldb] build.py: fix behavior when passing --compiler=/path/to/compiler All the other paths in the find_toolchain function return a tuple (detected_toolchain_type, compiler_path), but when the parameter to --compiler is not one of the predefined names it only returns the detected toolchain type, which causes an error when trying to unpack the result. This patch changes it to return also the compiler path passed as a parameter. Differential Revision: https://reviews.llvm.org/D61713 llvm-svn: 360355 2019-05-09 16:47:07 +00:00			`CHECK-SAME: /Fo`