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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
import("//clang/lib/ARCMigrate/enable.gni")
import("//clang/lib/StaticAnalyzer/Frontend/enable.gni")
import("//llvm/utils/gn/build/toolchain/compiler.gni")
group("default") {
deps = [
"//clang/test",
"//lld/test",
"//llvm/test",
]
if (android_ndk_path != "") {
# FIXME: This should be a dependency of a test target instead of being
# depended on from here.
android_aarch64_toolchain =
"//llvm/utils/gn/build/toolchain:stage2_android_aarch64"
deps += [
"//compiler-rt/lib/hwasan:hwasan_shared($android_aarch64_toolchain)",
"//llvm/tools/llvm-symbolizer($android_aarch64_toolchain)",
]
}
testonly = true
}
# Symlink handling.
# On POSIX, symlinks to the target can be created before the target exist,
# and the target can depend on the symlink targets, so that building the
# target ensures the symlinks exist.
# However, symlinks didn't exist on Windows until recently, so there the
# binary needs to be copied -- which requires it to exist. So the symlink step
# needs to run after the target that creates the binary.
# In the cmake build, this is done via a "postbuild" on the target, which just
# tacks on "&& copy out.exe out2.exe" to the link command.
# GN doesn't have a way to express postbuild commands. It could probably be
# emulated by having the link command in the toolchain be a wrapper script that
# reads a ".symlinks" file next to the target, and have an action write that
# and make the target depend on that, but then every single link has to use the
# wrapper (unless we do further acrobatics to use a different toolchain for
# targets that need symlinks) even though most links don't need symlinks.
# Instead, have a top-level target for each target that needs symlinks, and
# make that depend on the symlinks. Then the symlinks can depend on the
# executable. This has the effect that `ninja lld` builds lld and then creates
# symlinks (via this target), while `ninja bin/lld` only builds lld and doesn't
# update symlinks (in particular, on Windows it doesn't copy the new lld to its
# new locations).
# That seems simpler, more explicit, and good enough.
group("clang") {
deps = [
"//clang/tools/driver:symlinks",
]
}
group("lld") {
deps = [
"//lld/tools/lld:symlinks",
]
}
group("llvm-ar") {
deps = [
"//llvm/tools/llvm-ar:symlinks",
]
}
group("llvm-dwp") {
deps = [
"//llvm/tools/llvm-dwp:symlinks",
]
}
group("llvm-nm") {
deps = [
"//llvm/tools/llvm-nm:symlinks",
]
}
group("llvm-cxxfilt") {
deps = [
"//llvm/tools/llvm-cxxfilt:symlinks",
]
}
group("llvm-objcopy") {
deps = [
"//llvm/tools/llvm-objcopy:symlinks",
]
}
group("llvm-objdump") {
deps = [
"//llvm/tools/llvm-objdump:symlinks",
]
}
group("llvm-readobj") {
deps = [
"//llvm/tools/llvm-readobj:symlinks",
]
}
group("llvm-size") {
deps = [
"//llvm/tools/llvm-size:symlinks",
]
}
group("llvm-strings") {
deps = [
"//llvm/tools/llvm-strings:symlinks",
]
}
group("llvm-symbolizer") {
deps = [
"//llvm/tools/llvm-symbolizer:symlinks",
]
}
# A pool called "console" in the root BUILD.gn is magic and represents ninja's
# built-in console pool. (Requires a GN with `gn --version` >= 552353.)
pool("console") {
depth = 1
}
|
