| commit | a5a79a411a2fb4f8c25427736cb27b36e56ae732 | [log] [tgz] |
|---|---|---|
| author | Keith Smiley <keithbsmiley@gmail.com> | Fri Aug 11 17:46:09 2023 -0700 |
| committer | GitHub <noreply@github.com> | Fri Aug 11 17:46:09 2023 -0700 |
| tree | d389f7f419450880bf04e54f15738ff6b209a289 | |
| parent | 40e2489b7470a8efb5098d02486dbf3b1d94211f [diff] |
Remove apple_common transitions (#242) This was removed upstream but we still need the smallest possible transition for testing, this copies the one from rules_apple and removes a bunch of the features. If this ends up being too much of a pain to update we'll have to find a different solution.
This repository contains the Apple CC toolchain, Apple related platforms and constraints definitions, and small helper functions for rules authors targeting Apple platforms.
If you want to build iOS, tvOS, watchOS, or macOS apps, use rules_apple.
If you want to build Swift use rules_swift.
See the documentation for the helper rules provided by this repository.
Copy the MODULE.bazel or WORKSPACE snippets from the releases page into your project.
The Apple CC toolchain in by this repository provides toolchains for building for Apple platforms besides macOS. Since Bazel 7 this toolchain is required when targeting those platforms but the toolchain also supports Bazel 6.
To use the Apple CC toolchain, pull this repository into your build and add this to your .bazelrc:
build --enable_platform_specific_config build:macos --apple_crosstool_top=@local_config_apple_cc//:toolchain build:macos --crosstool_top=@local_config_apple_cc//:toolchain build:macos --host_crosstool_top=@local_config_apple_cc//:toolchain
This ensures that all rules provided by rules_apple, as well as other rules like cc_binary, all use the toolchain provided by this repository when building on macOS.
NOTE: This toolchain requires a full Xcode installation, not just the Xcode Command Line Tools. If you only need to build for macOS and don't want to require a full Xcode installation in your build, use the builtin Unix toolchain provided by Bazel.
If you're using bzlmod with the --crosstool_top configurations you must expose the local_config_apple_cc repository to your project by putting this in your MODULE.bazel:
apple_cc_configure = use_extension("@build_bazel_apple_support//crosstool:setup.bzl", "apple_cc_configure_extension") use_repo(apple_cc_configure, "local_config_apple_cc")
Bazel is currently working on migrating C++ toolchain configuration to a new discovery method that no longer uses the --*crosstool_top flags. If you would like to test this upcoming feature, or need to use this in your build for other reasons, you can use this toolchain with --incompatible_enable_cc_toolchain_resolution as long as you provide a platform_mappings file. Please file any issues you find as you test this work in progress configuration.
There are many different flags you can flip to configure how the toolchain works. Here are some of the more commonly useful ones:
DEVELOPER_DIR in the environment. This is recommended so that the toolchain can be invalidated when the DEVELOPER_DIR changes, which ensures that toolchain binaries will be rebuilt with the new version of Xcode so that caches are correctly shared across machines.BAZEL_ALLOW_NON_APPLICATIONS_XCODE=1 in the environment (or using --repo_env) allows the toolchain to discover Xcode versions outside of the /Applications directory to avoid header inclusion errors from bazel. This is not enabled by default because /Applications is the standard directory, and this improves toolchain setup performance.