Motiejus Jakštys e319ac4635 zig cache dir: move to /tmp/zig-cache (#52) ...

This cache directory can be re-used by everything and everyone. There is
nothing bazel or hermetic_cc_toolchain specific there. So let's make it
clear.

Also, if there are any more zig-based toolchains on top of Bazel or
other build systems where they cannot rely on $HOME, but need an
absolute path, this feels like a reasonable choice.

2023-04-28 09:05:34 -07:00

..

libc

Rename bazel-zig-cc to hermetic_cc_toolchain (#36)

2023-04-21 10:00:03 -04:00

libc_aware

Rename bazel-zig-cc to hermetic_cc_toolchain (#36)

2023-04-21 10:00:03 -04:00

platform

Rename bazel-zig-cc to hermetic_cc_toolchain (#36)

2023-04-21 10:00:03 -04:00

private

Re-add linkopts and set -Wl,-headerpad_max_install_names on macos

2023-04-24 09:48:27 -07:00

toolchain

Rename bazel-zig-cc to hermetic_cc_toolchain (#36)

2023-04-21 10:00:03 -04:00

BUILD

add .build.yml

2021-06-08 06:28:15 +03:00

BUILD.sdk.bazel

remove glibc hacks and update Zig SDK

2023-04-24 12:09:35 +03:00

defs.bzl

zig cache dir: move to /tmp/zig-cache (#52)

2023-04-28 09:05:34 -07:00

launcher.zig

bump zig sdk to 0.11.0-dev.2619+bd3e248c7

2023-04-24 15:48:07 +03:00

zig_toolchain.bzl

buildifier

2023-04-26 07:32:43 +03:00