1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
# Windows doesn't have a way to exec python files
# UNSUPPORTED: platform=Windows
# Check that we communicate properly with the Swift compiler.
#
# RUN: rm -rf %t.build
# RUN: mkdir -p %t.build/temps/nested
# RUN: sed -e "s#SOURCEDIR#%S#g" -e "s#TMPDIR#%t#g" < %s > %t.build/build.swift-build
# RUN: %{swift-build-tool} --no-db --chdir %t.build > %t.out
# RUN: %{swift-build-tool} --no-db -v --chdir %t.build > %t-verbose.out
# RUN: %{FileCheck} --input-file=%t.out %s
# RUN: %{FileCheck} --check-prefix=CHECK-VERBOSE --input-file=%t-verbose.out %s
#
# CHECK: Compiling Swift Module 'Foo'
# FIXME: This should quote output paths.
# CHECK-VERBOSE: swiftc -module-name Foo -emit-dependencies -emit-module -emit-module-path Foo.swiftmodule -output-file-map temps/output-file-map.json -parse-as-library -incremental -c "s 1.swift" "s 2.swift" -I "import A" -I "import B" -Onone -I "path with spaces"
# Sanity check the output file map.
#
# RUN: %{FileCheck} --check-prefix=CHECK-OUTPUT-FILE-MAP --input-file=%t.build/temps/output-file-map.json %s
# CHECK-OUTPUT-FILE-MAP: "s 1.swift": {
# CHECK-OUTPUT-FILE-MAP-NEXT: "dependencies": "temps/s 1.d"
# CHECK-OUTPUT-FILE-MAP: "s 2.swift": {
# CHECK-OUTPUT-FILE-MAP-NEXT: "dependencies": "temps/nested/s 2.d"
client:
name: swift-build
targets:
"": ["<output>"]
commands:
C1:
tool: swift-compiler
outputs: ["<output>"]
executable: SOURCEDIR/Inputs/pseudo-swiftc
module-name: Foo
module-output-path: Foo.swiftmodule
sources: ["s 1.swift", "s 2.swift"]
import-paths: ["import A", "import B"]
# FIXME: We can't use spaces in filenames here yet, because of a Swift compiler bug.
objects: ["temps/s1.o", "temps/nested/s2.o"]
other-args: ["-Onone", "-I", "path with spaces"]
temps-path: temps
is-library: true
|
