2021-04-10 01:05:01 +03:00
|
|
|
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
|
2022-03-25 17:46:59 +02:00
|
|
|
load("@bazel_tools//tools/build_defs/repo:utils.bzl", "read_user_netrc", "use_netrc")
|
2023-04-21 17:00:03 +03:00
|
|
|
load("@hermetic_cc_toolchain//toolchain/private:defs.bzl", "target_structs", "zig_tool_path")
|
2022-09-26 10:14:08 +03:00
|
|
|
|
|
|
|
# Directories that `zig c++` includes behind the scenes.
|
|
|
|
_DEFAULT_INCLUDE_DIRECTORIES = [
|
|
|
|
"libcxx/include",
|
|
|
|
"libcxxabi/include",
|
|
|
|
"libunwind/include",
|
|
|
|
]
|
2021-04-10 01:05:01 +03:00
|
|
|
|
2022-01-25 11:05:35 +02:00
|
|
|
# Official recommended version. Should use this when we have a usable release.
|
2022-06-02 06:16:39 +03:00
|
|
|
URL_FORMAT_RELEASE = "https://ziglang.org/download/{version}/zig-{host_platform}-{version}.{_ext}"
|
2022-01-25 11:05:35 +02:00
|
|
|
|
2023-04-21 17:00:03 +03:00
|
|
|
# Caution: nightly releases are purged from ziglang.org after ~90 days. Use the
|
|
|
|
# Bazel mirror or your own.
|
2022-06-02 06:16:39 +03:00
|
|
|
URL_FORMAT_NIGHTLY = "https://ziglang.org/builds/zig-{host_platform}-{version}.{_ext}"
|
2022-01-25 11:05:35 +02:00
|
|
|
|
2023-03-01 16:25:16 +02:00
|
|
|
# Official Bazel's mirror with selected Zig SDK versions. Bazel community is
|
|
|
|
# generous enough to host the artifacts, which we use.
|
|
|
|
URL_FORMAT_BAZELMIRROR = "https://mirror.bazel.build/" + URL_FORMAT_NIGHTLY.lstrip("https://")
|
2021-12-07 09:51:14 +02:00
|
|
|
|
2023-04-24 14:34:20 +03:00
|
|
|
_VERSION = "0.11.0-dev.2619+bd3e248c7"
|
2021-12-06 08:07:28 +02:00
|
|
|
|
2022-03-18 06:30:38 +02:00
|
|
|
_HOST_PLATFORM_SHA256 = {
|
2023-04-24 14:34:20 +03:00
|
|
|
"linux-aarch64": "e72aedc7b9ecf20164dc5aae952499f03402383ca9fb84e72bbb8598f45f693f",
|
|
|
|
"linux-x86_64": "019dbe76a9035ae4c775483ccb860a740759e22c8bbebd0234f8eaa2a7458cd7",
|
|
|
|
"macos-aarch64": "3a62f5a535c532978c6a7d248a1f141004de0812fa4b432d50f5dcc9e29e2a55",
|
|
|
|
"macos-x86_64": "eb4e409cc84991dc0ea8e3e550edb2254d0b15be5f59f2cff4bdc406a9b1ec46",
|
|
|
|
"windows-x86_64": "01004e422e7e7d48f1df403e368422ce7150428f827f3d579cd44e28f53dba2c",
|
2022-05-29 19:35:16 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
_HOST_PLATFORM_EXT = {
|
|
|
|
"linux-aarch64": "tar.xz",
|
|
|
|
"linux-x86_64": "tar.xz",
|
|
|
|
"macos-aarch64": "tar.xz",
|
|
|
|
"macos-x86_64": "tar.xz",
|
|
|
|
"windows-x86_64": "zip",
|
2022-03-18 06:30:38 +02:00
|
|
|
}
|
|
|
|
|
2023-03-21 12:43:08 +02:00
|
|
|
_MCPU = {
|
|
|
|
"linux-aarch64": "baseline",
|
|
|
|
"linux-x86_64": "baseline",
|
|
|
|
"macos-aarch64": "apple_a14",
|
|
|
|
"macos-x86_64": "baseline",
|
|
|
|
"windows-x86_64": "baseline",
|
|
|
|
}
|
|
|
|
|
2023-02-28 10:08:43 +02:00
|
|
|
_compile_failed = """
|
|
|
|
Compilation of launcher.zig failed:
|
|
|
|
command={compile_cmd}
|
|
|
|
return_code={return_code}
|
|
|
|
stderr={stderr}
|
|
|
|
stdout={stdout}
|
|
|
|
|
2023-03-20 10:25:41 +02:00
|
|
|
You stumbled into a problem with Zig SDK that bazel-zig-cc was not able to fix.
|
|
|
|
Please file a new issue to github.com/uber/bazel-zig-cc with:
|
|
|
|
- Full output of this Bazel run, including the Bazel command.
|
|
|
|
- Version of the Zig SDK if you have a non-default.
|
|
|
|
- Version of bazel-zig-cc.
|
|
|
|
|
|
|
|
Note: this *may* have been https://github.com/ziglang/zig/issues/14815, for
|
|
|
|
which bazel-zig-cc has a workaround and you may have been "struck by lightning"
|
|
|
|
three times in a row.
|
2023-02-28 10:08:43 +02:00
|
|
|
"""
|
|
|
|
|
2022-04-13 17:52:25 +03:00
|
|
|
def toolchains(
|
2021-12-06 08:07:28 +02:00
|
|
|
version = _VERSION,
|
2023-03-01 16:25:16 +02:00
|
|
|
url_formats = [URL_FORMAT_BAZELMIRROR, URL_FORMAT_NIGHTLY],
|
2022-05-29 19:35:16 +03:00
|
|
|
host_platform_sha256 = _HOST_PLATFORM_SHA256,
|
|
|
|
host_platform_ext = _HOST_PLATFORM_EXT):
|
2021-08-11 09:36:20 +03:00
|
|
|
"""
|
2022-04-13 17:52:25 +03:00
|
|
|
Download zig toolchain and declare bazel toolchains.
|
|
|
|
The platforms are not registered automatically, that should be done by
|
|
|
|
the user with register_toolchains() in the WORKSPACE file. See README
|
|
|
|
for possible choices.
|
2021-08-11 09:36:20 +03:00
|
|
|
"""
|
2021-04-10 01:05:01 +03:00
|
|
|
zig_repository(
|
2021-06-10 09:34:59 +03:00
|
|
|
name = "zig_sdk",
|
2021-12-06 08:07:28 +02:00
|
|
|
version = version,
|
2022-03-18 06:44:22 +02:00
|
|
|
url_formats = url_formats,
|
2022-03-18 06:30:38 +02:00
|
|
|
host_platform_sha256 = host_platform_sha256,
|
2022-05-29 19:35:16 +03:00
|
|
|
host_platform_ext = host_platform_ext,
|
2021-04-10 01:05:01 +03:00
|
|
|
)
|
|
|
|
|
2022-08-29 12:46:33 +03:00
|
|
|
_ZIG_TOOLS = [
|
|
|
|
"c++",
|
|
|
|
"ar",
|
|
|
|
]
|
|
|
|
|
2022-04-13 17:52:25 +03:00
|
|
|
def _quote(s):
|
|
|
|
return "'" + s.replace("'", "'\\''") + "'"
|
|
|
|
|
2021-04-10 01:05:01 +03:00
|
|
|
def _zig_repository_impl(repository_ctx):
|
2022-03-25 17:46:11 +02:00
|
|
|
arch = repository_ctx.os.arch
|
|
|
|
if arch == "amd64":
|
|
|
|
arch = "x86_64"
|
2021-09-13 08:44:58 +03:00
|
|
|
|
2022-03-25 17:46:11 +02:00
|
|
|
os = repository_ctx.os.name.lower()
|
|
|
|
if os.startswith("mac os"):
|
2022-02-11 01:22:37 +02:00
|
|
|
os = "macos"
|
2022-03-25 17:46:11 +02:00
|
|
|
|
2022-05-29 19:35:16 +03:00
|
|
|
if os.startswith("windows"):
|
|
|
|
os = "windows"
|
|
|
|
|
2022-02-11 01:22:37 +02:00
|
|
|
host_platform = "{}-{}".format(os, arch)
|
2021-04-10 01:05:01 +03:00
|
|
|
|
2021-04-10 03:49:14 +03:00
|
|
|
zig_sha256 = repository_ctx.attr.host_platform_sha256[host_platform]
|
2022-05-29 19:35:16 +03:00
|
|
|
zig_ext = repository_ctx.attr.host_platform_ext[host_platform]
|
2021-04-10 01:05:01 +03:00
|
|
|
format_vars = {
|
2022-06-02 06:16:39 +03:00
|
|
|
"_ext": zig_ext,
|
2021-06-16 12:44:16 +03:00
|
|
|
"version": repository_ctx.attr.version,
|
|
|
|
"host_platform": host_platform,
|
2021-04-10 01:05:01 +03:00
|
|
|
}
|
2022-03-18 06:30:42 +02:00
|
|
|
|
2022-09-15 21:20:21 +03:00
|
|
|
# Fetch Label dependencies before doing download/extract.
|
|
|
|
# The Bazel docs are not very clear about this behavior but see:
|
|
|
|
# https://bazel.build/extending/repo#when_is_the_implementation_function_executed
|
|
|
|
# and a related rules_go PR:
|
|
|
|
# https://github.com/bazelbuild/bazel-gazelle/pull/1206
|
|
|
|
for dest, src in {
|
|
|
|
"platform/BUILD": "//toolchain/platform:BUILD",
|
|
|
|
"toolchain/BUILD": "//toolchain/toolchain:BUILD",
|
|
|
|
"libc/BUILD": "//toolchain/libc:BUILD",
|
|
|
|
"libc_aware/platform/BUILD": "//toolchain/libc_aware/platform:BUILD",
|
|
|
|
"libc_aware/toolchain/BUILD": "//toolchain/libc_aware/toolchain:BUILD",
|
|
|
|
}.items():
|
|
|
|
repository_ctx.symlink(Label(src), dest)
|
|
|
|
|
|
|
|
for dest, src in {
|
|
|
|
"BUILD": "//toolchain:BUILD.sdk.bazel",
|
2022-09-21 13:14:29 +03:00
|
|
|
# "private/BUILD": "//toolchain/private:BUILD.sdk.bazel",
|
2022-09-15 21:20:21 +03:00
|
|
|
}.items():
|
|
|
|
repository_ctx.template(
|
|
|
|
dest,
|
|
|
|
Label(src),
|
|
|
|
executable = False,
|
|
|
|
substitutions = {
|
2022-09-27 15:37:28 +03:00
|
|
|
"{zig_sdk_path}": _quote("external/zig_sdk"),
|
2022-09-15 21:20:21 +03:00
|
|
|
"{os}": _quote(os),
|
|
|
|
},
|
|
|
|
)
|
|
|
|
|
2022-03-18 07:04:49 +02:00
|
|
|
urls = [uf.format(**format_vars) for uf in repository_ctx.attr.url_formats]
|
2021-04-10 01:05:01 +03:00
|
|
|
repository_ctx.download_and_extract(
|
2022-03-25 17:46:59 +02:00
|
|
|
auth = use_netrc(read_user_netrc(repository_ctx), urls, {}),
|
2022-03-18 07:04:49 +02:00
|
|
|
url = urls,
|
2021-04-10 01:05:01 +03:00
|
|
|
stripPrefix = "zig-{host_platform}-{version}/".format(**format_vars),
|
2021-04-10 03:49:14 +03:00
|
|
|
sha256 = zig_sha256,
|
2021-04-10 01:05:01 +03:00
|
|
|
)
|
|
|
|
|
2023-04-21 17:00:03 +03:00
|
|
|
cache_prefix = repository_ctx.os.environ.get("HERMETIC_CC_TOOLCHAIN_CACHE_PREFIX", "")
|
zig launcher: replace shell wrappers with a binary
Until now we needed to maintain two versions of the zig launcher: one
for Windows and one for everything else. This was problematic for two
reasons:
1. I do not know powershell and thus keep breaking the Windows wrapper
all the time (see git history of Fabian fixing stuff that I broke).
2. This makes bazel-zig-cc dependent on the system shell, making it not
really hermetic. So the recently added
`--experimental_use_hermetic_linux_sandbox` does not work with
bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`,
`/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`.
Switching to a Zig-based wrapper solves both issues, and we can do this:
bazel build "$@" \
--experimental_use_hermetic_linux_sandbox \
--sandbox_add_mount_pair=/proc \
<...>
Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to
keep that. I will look into reducing even that dependency separately.
Not all is nice and shiny though: this commit replaces ~80 LOC worth of
shell scripts wrappers with a singe ~300 LOC zig program, which is
arguably harder to understand. However, it is easier to change, at least
for me, because it's a single file with unit tests! Most importantly,
the gnarly code (which resolves paths and sets environment variables) is
cross-platform.
Thanks to Fabian Hahn for testing this on Windows and pointing out
errors.
2022-12-20 17:00:50 +02:00
|
|
|
if cache_prefix == "":
|
|
|
|
if os == "windows":
|
2023-04-21 17:00:03 +03:00
|
|
|
cache_prefix = "C:\\\\Temp\\\\hermetic_cc_toolchain"
|
zig launcher: replace shell wrappers with a binary
Until now we needed to maintain two versions of the zig launcher: one
for Windows and one for everything else. This was problematic for two
reasons:
1. I do not know powershell and thus keep breaking the Windows wrapper
all the time (see git history of Fabian fixing stuff that I broke).
2. This makes bazel-zig-cc dependent on the system shell, making it not
really hermetic. So the recently added
`--experimental_use_hermetic_linux_sandbox` does not work with
bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`,
`/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`.
Switching to a Zig-based wrapper solves both issues, and we can do this:
bazel build "$@" \
--experimental_use_hermetic_linux_sandbox \
--sandbox_add_mount_pair=/proc \
<...>
Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to
keep that. I will look into reducing even that dependency separately.
Not all is nice and shiny though: this commit replaces ~80 LOC worth of
shell scripts wrappers with a singe ~300 LOC zig program, which is
arguably harder to understand. However, it is easier to change, at least
for me, because it's a single file with unit tests! Most importantly,
the gnarly code (which resolves paths and sets environment variables) is
cross-platform.
Thanks to Fabian Hahn for testing this on Windows and pointing out
errors.
2022-12-20 17:00:50 +02:00
|
|
|
else:
|
2023-04-21 17:00:03 +03:00
|
|
|
cache_prefix = "/tmp/hermetic_cc_toolchain"
|
zig launcher: replace shell wrappers with a binary
Until now we needed to maintain two versions of the zig launcher: one
for Windows and one for everything else. This was problematic for two
reasons:
1. I do not know powershell and thus keep breaking the Windows wrapper
all the time (see git history of Fabian fixing stuff that I broke).
2. This makes bazel-zig-cc dependent on the system shell, making it not
really hermetic. So the recently added
`--experimental_use_hermetic_linux_sandbox` does not work with
bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`,
`/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`.
Switching to a Zig-based wrapper solves both issues, and we can do this:
bazel build "$@" \
--experimental_use_hermetic_linux_sandbox \
--sandbox_add_mount_pair=/proc \
<...>
Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to
keep that. I will look into reducing even that dependency separately.
Not all is nice and shiny though: this commit replaces ~80 LOC worth of
shell scripts wrappers with a singe ~300 LOC zig program, which is
arguably harder to understand. However, it is easier to change, at least
for me, because it's a single file with unit tests! Most importantly,
the gnarly code (which resolves paths and sets environment variables) is
cross-platform.
Thanks to Fabian Hahn for testing this on Windows and pointing out
errors.
2022-12-20 17:00:50 +02:00
|
|
|
|
|
|
|
repository_ctx.template(
|
|
|
|
"tools/launcher.zig",
|
|
|
|
Label("//toolchain:launcher.zig"),
|
|
|
|
executable = False,
|
|
|
|
substitutions = {
|
2023-04-21 17:00:03 +03:00
|
|
|
"{HERMETIC_CC_TOOLCHAIN_CACHE_PREFIX}": cache_prefix,
|
zig launcher: replace shell wrappers with a binary
Until now we needed to maintain two versions of the zig launcher: one
for Windows and one for everything else. This was problematic for two
reasons:
1. I do not know powershell and thus keep breaking the Windows wrapper
all the time (see git history of Fabian fixing stuff that I broke).
2. This makes bazel-zig-cc dependent on the system shell, making it not
really hermetic. So the recently added
`--experimental_use_hermetic_linux_sandbox` does not work with
bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`,
`/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`.
Switching to a Zig-based wrapper solves both issues, and we can do this:
bazel build "$@" \
--experimental_use_hermetic_linux_sandbox \
--sandbox_add_mount_pair=/proc \
<...>
Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to
keep that. I will look into reducing even that dependency separately.
Not all is nice and shiny though: this commit replaces ~80 LOC worth of
shell scripts wrappers with a singe ~300 LOC zig program, which is
arguably harder to understand. However, it is easier to change, at least
for me, because it's a single file with unit tests! Most importantly,
the gnarly code (which resolves paths and sets environment variables) is
cross-platform.
Thanks to Fabian Hahn for testing this on Windows and pointing out
errors.
2022-12-20 17:00:50 +02:00
|
|
|
},
|
|
|
|
)
|
|
|
|
|
2023-02-28 10:08:43 +02:00
|
|
|
compile_env = {
|
|
|
|
"ZIG_LOCAL_CACHE_DIR": cache_prefix,
|
|
|
|
"ZIG_GLOBAL_CACHE_DIR": cache_prefix,
|
|
|
|
}
|
|
|
|
compile_cmd = [
|
2023-04-17 12:37:03 +03:00
|
|
|
_paths_join("..", "zig"),
|
2023-02-28 10:08:43 +02:00
|
|
|
"build-exe",
|
2023-03-21 12:43:08 +02:00
|
|
|
"-mcpu={}".format(_MCPU[host_platform]),
|
2023-02-28 10:08:43 +02:00
|
|
|
"-OReleaseSafe",
|
|
|
|
"launcher.zig",
|
|
|
|
] + (["-static"] if os == "linux" else [])
|
|
|
|
|
2023-03-20 10:25:41 +02:00
|
|
|
# The elaborate code below is a workaround for ziglang/zig#14815:
|
|
|
|
# Sometimes, when Zig's cache is empty, compiling the launcher may fail
|
|
|
|
# with `error: FileNotFound`. The remedy is to clear the cache and try
|
|
|
|
# again. Until this change, we have been asking users to clear the Zig
|
|
|
|
# cache themselves and re-run the Bazel command.
|
|
|
|
#
|
|
|
|
# We can do better than that: if we detect the launcher failed, we can
|
|
|
|
# purge the zig cache and retry the compilation. It will be retried for up
|
|
|
|
# to two times.
|
|
|
|
launcher_success = True
|
|
|
|
launcher_err_msg = ""
|
|
|
|
for _ in range(3):
|
|
|
|
# Do not remove the cache_prefix itself, because it is not controlled
|
|
|
|
# by this script. Instead, clear the cache subdirs that we know Zig
|
|
|
|
# populates.
|
|
|
|
zig_cache_dirs = ["h", "o", "tmp", "z"]
|
|
|
|
if not launcher_success:
|
|
|
|
print("Launcher compilation failed. Clearing %s/{%s} and retrying" %
|
|
|
|
(cache_prefix, ",".join(zig_cache_dirs)))
|
|
|
|
for d in zig_cache_dirs:
|
2023-04-24 10:18:34 +03:00
|
|
|
repository_ctx.delete(_paths_join(cache_prefix, d))
|
2023-03-20 10:25:41 +02:00
|
|
|
|
|
|
|
ret = repository_ctx.execute(
|
|
|
|
compile_cmd,
|
|
|
|
working_directory = "tools",
|
|
|
|
environment = compile_env,
|
|
|
|
)
|
|
|
|
|
|
|
|
if ret.return_code == 0:
|
|
|
|
launcher_success = True
|
|
|
|
break
|
|
|
|
|
|
|
|
launcher_success = False
|
2023-02-28 10:08:43 +02:00
|
|
|
full_cmd = [k + "=" + v for k, v in compile_env.items()] + compile_cmd
|
2023-03-20 10:25:41 +02:00
|
|
|
launcher_err_msg = _compile_failed.format(
|
2023-02-28 10:08:43 +02:00
|
|
|
compile_cmd = " ".join(full_cmd),
|
|
|
|
return_code = ret.return_code,
|
|
|
|
stdout = ret.stdout,
|
|
|
|
stderr = ret.stderr,
|
|
|
|
cache_prefix = cache_prefix,
|
2023-03-20 10:25:41 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
if not launcher_success:
|
|
|
|
fail(launcher_err_msg)
|
zig launcher: replace shell wrappers with a binary
Until now we needed to maintain two versions of the zig launcher: one
for Windows and one for everything else. This was problematic for two
reasons:
1. I do not know powershell and thus keep breaking the Windows wrapper
all the time (see git history of Fabian fixing stuff that I broke).
2. This makes bazel-zig-cc dependent on the system shell, making it not
really hermetic. So the recently added
`--experimental_use_hermetic_linux_sandbox` does not work with
bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`,
`/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`.
Switching to a Zig-based wrapper solves both issues, and we can do this:
bazel build "$@" \
--experimental_use_hermetic_linux_sandbox \
--sandbox_add_mount_pair=/proc \
<...>
Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to
keep that. I will look into reducing even that dependency separately.
Not all is nice and shiny though: this commit replaces ~80 LOC worth of
shell scripts wrappers with a singe ~300 LOC zig program, which is
arguably harder to understand. However, it is easier to change, at least
for me, because it's a single file with unit tests! Most importantly,
the gnarly code (which resolves paths and sets environment variables) is
cross-platform.
Thanks to Fabian Hahn for testing this on Windows and pointing out
errors.
2022-12-20 17:00:50 +02:00
|
|
|
|
|
|
|
exe = ".exe" if os == "windows" else ""
|
2022-12-18 06:13:32 +02:00
|
|
|
for target_config in target_structs():
|
|
|
|
for zig_tool in _ZIG_TOOLS + target_config.tool_paths.values():
|
zig launcher: replace shell wrappers with a binary
Until now we needed to maintain two versions of the zig launcher: one
for Windows and one for everything else. This was problematic for two
reasons:
1. I do not know powershell and thus keep breaking the Windows wrapper
all the time (see git history of Fabian fixing stuff that I broke).
2. This makes bazel-zig-cc dependent on the system shell, making it not
really hermetic. So the recently added
`--experimental_use_hermetic_linux_sandbox` does not work with
bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`,
`/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`.
Switching to a Zig-based wrapper solves both issues, and we can do this:
bazel build "$@" \
--experimental_use_hermetic_linux_sandbox \
--sandbox_add_mount_pair=/proc \
<...>
Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to
keep that. I will look into reducing even that dependency separately.
Not all is nice and shiny though: this commit replaces ~80 LOC worth of
shell scripts wrappers with a singe ~300 LOC zig program, which is
arguably harder to understand. However, it is easier to change, at least
for me, because it's a single file with unit tests! Most importantly,
the gnarly code (which resolves paths and sets environment variables) is
cross-platform.
Thanks to Fabian Hahn for testing this on Windows and pointing out
errors.
2022-12-20 17:00:50 +02:00
|
|
|
tool_path = zig_tool_path(os).format(
|
|
|
|
zig_tool = zig_tool,
|
2022-10-01 14:26:45 +03:00
|
|
|
zigtarget = target_config.zigtarget,
|
|
|
|
)
|
zig launcher: replace shell wrappers with a binary
Until now we needed to maintain two versions of the zig launcher: one
for Windows and one for everything else. This was problematic for two
reasons:
1. I do not know powershell and thus keep breaking the Windows wrapper
all the time (see git history of Fabian fixing stuff that I broke).
2. This makes bazel-zig-cc dependent on the system shell, making it not
really hermetic. So the recently added
`--experimental_use_hermetic_linux_sandbox` does not work with
bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`,
`/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`.
Switching to a Zig-based wrapper solves both issues, and we can do this:
bazel build "$@" \
--experimental_use_hermetic_linux_sandbox \
--sandbox_add_mount_pair=/proc \
<...>
Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to
keep that. I will look into reducing even that dependency separately.
Not all is nice and shiny though: this commit replaces ~80 LOC worth of
shell scripts wrappers with a singe ~300 LOC zig program, which is
arguably harder to understand. However, it is easier to change, at least
for me, because it's a single file with unit tests! Most importantly,
the gnarly code (which resolves paths and sets environment variables) is
cross-platform.
Thanks to Fabian Hahn for testing this on Windows and pointing out
errors.
2022-12-20 17:00:50 +02:00
|
|
|
repository_ctx.symlink("tools/launcher{}".format(exe), tool_path)
|
2021-04-10 01:05:01 +03:00
|
|
|
|
|
|
|
zig_repository = repository_rule(
|
|
|
|
attrs = {
|
|
|
|
"version": attr.string(),
|
2021-04-10 02:58:05 +03:00
|
|
|
"host_platform_sha256": attr.string_dict(),
|
2022-03-18 06:44:22 +02:00
|
|
|
"url_formats": attr.string_list(allow_empty = False),
|
2022-05-29 19:35:16 +03:00
|
|
|
"host_platform_ext": attr.string_dict(),
|
2021-04-10 01:05:01 +03:00
|
|
|
},
|
2023-04-21 17:00:03 +03:00
|
|
|
environ = ["HERMETIC_CC_TOOLCHAIN_CACHE_PREFIX"],
|
2021-04-10 01:05:01 +03:00
|
|
|
implementation = _zig_repository_impl,
|
|
|
|
)
|
|
|
|
|
|
|
|
def filegroup(name, **kwargs):
|
|
|
|
native.filegroup(name = name, **kwargs)
|
|
|
|
return ":" + name
|
|
|
|
|
2022-12-07 12:17:44 +02:00
|
|
|
def declare_files(os):
|
2022-09-21 13:14:29 +03:00
|
|
|
filegroup(name = "all", srcs = native.glob(["**"]))
|
2021-06-16 12:44:16 +03:00
|
|
|
filegroup(name = "empty")
|
2022-05-29 19:35:16 +03:00
|
|
|
if os == "windows":
|
|
|
|
native.exports_files(["zig.exe"], visibility = ["//visibility:public"])
|
|
|
|
native.alias(name = "zig", actual = ":zig.exe")
|
|
|
|
else:
|
|
|
|
native.exports_files(["zig"], visibility = ["//visibility:public"])
|
2021-06-16 12:44:16 +03:00
|
|
|
filegroup(name = "lib/std", srcs = native.glob(["lib/std/**"]))
|
2021-04-10 01:05:01 +03:00
|
|
|
lazy_filegroups = {}
|
|
|
|
|
2022-04-06 23:10:45 +03:00
|
|
|
for target_config in target_structs():
|
2022-12-13 14:38:51 +02:00
|
|
|
all_includes = [native.glob(["lib/{}/**".format(i)]) for i in target_config.includes]
|
|
|
|
|
|
|
|
cxx_tool_label = ":" + zig_tool_path(os).format(
|
|
|
|
zig_tool = "c++",
|
|
|
|
zigtarget = target_config.zigtarget,
|
|
|
|
)
|
|
|
|
|
|
|
|
filegroup(
|
|
|
|
name = "{}_includes".format(target_config.zigtarget),
|
|
|
|
srcs = _flatten(all_includes),
|
|
|
|
)
|
|
|
|
|
|
|
|
filegroup(
|
|
|
|
name = "{}_compiler_files".format(target_config.zigtarget),
|
|
|
|
srcs = [
|
|
|
|
":zig",
|
|
|
|
":{}_includes".format(target_config.zigtarget),
|
|
|
|
cxx_tool_label,
|
|
|
|
],
|
|
|
|
)
|
|
|
|
|
|
|
|
filegroup(
|
|
|
|
name = "{}_linker_files".format(target_config.zigtarget),
|
|
|
|
srcs = [
|
|
|
|
":zig",
|
|
|
|
":{}_includes".format(target_config.zigtarget),
|
|
|
|
cxx_tool_label,
|
|
|
|
] + native.glob([
|
|
|
|
"lib/libc/{}/**".format(target_config.libc),
|
|
|
|
"lib/libcxx/**",
|
|
|
|
"lib/libcxxabi/**",
|
|
|
|
"lib/libunwind/**",
|
|
|
|
"lib/compiler_rt/**",
|
|
|
|
"lib/std/**",
|
|
|
|
"lib/*.zig",
|
|
|
|
"lib/*.h",
|
|
|
|
]),
|
|
|
|
)
|
|
|
|
|
2022-12-13 17:19:42 +02:00
|
|
|
filegroup(
|
|
|
|
name = "{}_ar_files".format(target_config.zigtarget),
|
|
|
|
srcs = [
|
|
|
|
":zig",
|
|
|
|
":" + zig_tool_path(os).format(
|
2022-12-13 18:26:56 +02:00
|
|
|
zig_tool = "ar",
|
|
|
|
zigtarget = target_config.zigtarget,
|
|
|
|
),
|
|
|
|
],
|
2022-12-13 17:19:42 +02:00
|
|
|
)
|
|
|
|
|
2022-12-13 14:38:51 +02:00
|
|
|
filegroup(
|
|
|
|
name = "{}_all_files".format(target_config.zigtarget),
|
|
|
|
srcs = [
|
|
|
|
":{}_linker_files".format(target_config.zigtarget),
|
|
|
|
":{}_compiler_files".format(target_config.zigtarget),
|
2022-12-13 17:19:42 +02:00
|
|
|
":{}_ar_files".format(target_config.zigtarget),
|
2022-12-13 14:38:51 +02:00
|
|
|
],
|
|
|
|
)
|
|
|
|
|
2022-09-26 10:14:08 +03:00
|
|
|
for d in _DEFAULT_INCLUDE_DIRECTORIES + target_config.includes:
|
2022-12-11 16:53:37 +02:00
|
|
|
d = "lib/" + d
|
2022-04-06 22:46:15 +03:00
|
|
|
if d not in lazy_filegroups:
|
|
|
|
lazy_filegroups[d] = filegroup(name = d, srcs = native.glob([d + "/**"]))
|
2022-12-13 14:38:51 +02:00
|
|
|
|
|
|
|
def _flatten(iterable):
|
|
|
|
result = []
|
|
|
|
for element in iterable:
|
|
|
|
result += element
|
|
|
|
return result
|
2023-04-17 12:37:03 +03:00
|
|
|
|
|
|
|
## Copied from https://github.com/bazelbuild/bazel-skylib/blob/1.4.1/lib/paths.bzl#L59-L98
|
|
|
|
def _paths_is_absolute(path):
|
|
|
|
return path.startswith("/") or (len(path) > 2 and path[1] == ":")
|
|
|
|
|
|
|
|
def _paths_join(path, *others):
|
|
|
|
result = path
|
|
|
|
for p in others:
|
|
|
|
if _paths_is_absolute(p):
|
|
|
|
result = p
|
|
|
|
elif not result or result.endswith("/"):
|
|
|
|
result += p
|
|
|
|
else:
|
|
|
|
result += "/" + p
|
|
|
|
return result
|