3 ms·
Whether you use Bazel or not, this is a well-known issue with an equally well-known solution. There’s no need for such a lengthy write-up: just use a consistent
by r2vcap 1y ago
Whether you use Bazel or not, this is a well-known issue with an equally well-known solution. There’s no need for such a lengthy write-up: just use a consistent sysroot across your entire build environment.
If you can’t create your own sysroot image, you can simply download Chromium’s prebuilt one and configure your C++ compile rules correctly. Problem solved.
- 01HNNWZ0MV43FF 1y agoSounds like a jerb for Docker
- rockwotj 1y agoYeah I built a custom sysroot for Redpanda (Bazel/C++/Distributed Kafka) using a really simple docker image: https://github.com/redpanda-data/redpanda/blob/dev/bazel/toolchain/Dockerfile.sysroot https://github.com/redpanda-data/redpanda/blob/dev/bazel/too... We also have an dockerfile for clang/LLVM in that repo so the whole thing is hermetic. It’s a bit of shame Bazel doesn’t come with stronger options/defaults here, because I feel like I want to reproduce this same toolchain on every C++ project with Bazel
- DriftRegion 1y agoThanks for sharing. As a non-google bazel user this is quite helpful.