AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5a1368327d
skia2/WORKSPACE.bazel

16 lines
943 B
Plaintext
Raw Normal View History

[infra] Add hermetic toolchain for C/C++ using Clang+Musl This can successfully build a C library: bazel build --config=clang //third_party:libpng This can build and run a statically-linked executable: bazel test --config=clang //:bazel_test For more verbose compile and linking output, add the `--features diagnostic` flag to a Bazel command (see _make_diagnostic_flags() in toolchain/clang_toolchain_config.bzl. Similarly, a `--features print_search_dirs` can be used to show where clang is looking for libraries etc to link against. These features are made available for easier debugging. Suggested review order: - Read https://docs.bazel.build/versions/4.2.1/tutorial/cc-toolchain-config.html if unfamiliar with setting up C++ toolchains in Bazel - .bazelrc and WORKSPACE.bazel that configure use and download of the toolchain (Clang 13, musl 1.2.2) - toolchain/build_toolchain.bzl which downloads and assembles the toolchain (w/o installing anything on the host machine) - toolchain/BUILD.bazel and toolchain/*trampoline.sh to see the setup of the toolchain rules. - toolchain/clang_toolchain_config.bzl to see the configuration of the toolchain. Pay special attention to the various command line flags that are set. - See that tools/bazel_test.cc has made a new home in experimental/bazel_test/bazel_test.cpp, with a companion BUILD.bazel. Note the addition of some function calls that test use of the C++ standard library. The number being used to test the PNG library is the latest and greatest that verifies we are compiling the one brought in via DEPS (and not a local one). - third_party/* to see how png (and its dependent zlib) have been built. Pay special attention to the musl_compat hack to fix static linking (any idea what the real cause is?) - //BUILD.bazel to see definition of the bazel_test executable. Change-Id: I7b0922d0d45cb9be8df2fd5fa5a1f48492654d5f Bug: skia:12541 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/461178 Reviewed-by: Ben Wagner <bungeman@google.com> Reviewed-by: Leandro Lovisolo <lovisolo@google.com>
2021-10-20 20:20:42 +00:00
workspace(name = "skia")
bazel baby steps A few first steps toward a Bazel build. To try it out, I think just $ bazel test ... I added third_party to .bazelignore to prevent Bazel from looking there. It can handle external dependencies itself, so no need to poke into what we sync from DEPS. Some of those have Bazel configs and we don't want to be building them yet. I've started by with libpng using new_git_repository(), mostly because it's small, with a mildly complex build, and needs dependencies of its own, zlib. Mysteriously zlib is built-in to Bazel, so that was easy. Next up is probably a dependency that does support Bazel, using git_repository(). That should make sure we can handle the full mix. Change-Id: I5775a1b254d341b9a90630aa1cc433a24167f2fd Reviewed-on: https://skia-review.googlesource.com/c/skia/+/316636 Commit-Queue: Mike Klein <mtklein@google.com> Reviewed-by: Joe Gregorio <jcgregorio@google.com>
2020-09-11 16:11:33 +00:00
[infra] Add hermetic toolchain for C/C++ using Clang+Musl This can successfully build a C library: bazel build --config=clang //third_party:libpng This can build and run a statically-linked executable: bazel test --config=clang //:bazel_test For more verbose compile and linking output, add the `--features diagnostic` flag to a Bazel command (see _make_diagnostic_flags() in toolchain/clang_toolchain_config.bzl. Similarly, a `--features print_search_dirs` can be used to show where clang is looking for libraries etc to link against. These features are made available for easier debugging. Suggested review order: - Read https://docs.bazel.build/versions/4.2.1/tutorial/cc-toolchain-config.html if unfamiliar with setting up C++ toolchains in Bazel - .bazelrc and WORKSPACE.bazel that configure use and download of the toolchain (Clang 13, musl 1.2.2) - toolchain/build_toolchain.bzl which downloads and assembles the toolchain (w/o installing anything on the host machine) - toolchain/BUILD.bazel and toolchain/*trampoline.sh to see the setup of the toolchain rules. - toolchain/clang_toolchain_config.bzl to see the configuration of the toolchain. Pay special attention to the various command line flags that are set. - See that tools/bazel_test.cc has made a new home in experimental/bazel_test/bazel_test.cpp, with a companion BUILD.bazel. Note the addition of some function calls that test use of the C++ standard library. The number being used to test the PNG library is the latest and greatest that verifies we are compiling the one brought in via DEPS (and not a local one). - third_party/* to see how png (and its dependent zlib) have been built. Pay special attention to the musl_compat hack to fix static linking (any idea what the real cause is?) - //BUILD.bazel to see definition of the bazel_test executable. Change-Id: I7b0922d0d45cb9be8df2fd5fa5a1f48492654d5f Bug: skia:12541 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/461178 Reviewed-by: Ben Wagner <bungeman@google.com> Reviewed-by: Leandro Lovisolo <lovisolo@google.com>
2021-10-20 20:20:42 +00:00
load("//toolchain:build_toolchain.bzl", "build_cpp_toolchain")
build_cpp_toolchain(
# Meant to run on amd64 linux and compile for amd64 linux using musl as the c library.
name = "clang_linux_amd64_musl",
# From https://github.com/llvm/llvm-project/releases/download/llvmorg-13.0.0/clang+llvm-13.0.0-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256
clang_prefix = "clang+llvm-13.0.0-x86_64-linux-gnu-ubuntu-20.04/",
clang_sha256 = "2c2fb857af97f41a5032e9ecadf7f78d3eff389a5cd3c9ec620d24f134ceb3c8",
clang_url = "https://github.com/llvm/llvm-project/releases/download/llvmorg-13.0.0/clang+llvm-13.0.0-x86_64-linux-gnu-ubuntu-20.04.tar.xz",
# From https://packages.debian.org/bullseye/amd64/musl-dev/download
musl_dev_sha256 = "b017792ad6ba3650b4889238c73cd19c1d6b0e39ca8319cdd3ad9e16374e614e",
musl_dev_url = "http://ftp.debian.org/debian/pool/main/m/musl/musl-dev_1.2.2-1_amd64.deb",
bazel baby steps A few first steps toward a Bazel build. To try it out, I think just $ bazel test ... I added third_party to .bazelignore to prevent Bazel from looking there. It can handle external dependencies itself, so no need to poke into what we sync from DEPS. Some of those have Bazel configs and we don't want to be building them yet. I've started by with libpng using new_git_repository(), mostly because it's small, with a mildly complex build, and needs dependencies of its own, zlib. Mysteriously zlib is built-in to Bazel, so that was easy. Next up is probably a dependency that does support Bazel, using git_repository(). That should make sure we can handle the full mix. Change-Id: I5775a1b254d341b9a90630aa1cc433a24167f2fd Reviewed-on: https://skia-review.googlesource.com/c/skia/+/316636 Commit-Queue: Mike Klein <mtklein@google.com> Reviewed-by: Joe Gregorio <jcgregorio@google.com>
2020-09-11 16:11:33 +00:00
)
Reference in New Issue Copy Permalink