bazelbuild/rules_swift
bazelbuild/rules_swift has 355 GitHub stars and 183 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-17 03:35 UTC. Last push 2026-11-17.
Measured star growth
- in 24h
- 0
- in 7 days
- Update delayed
- in 15 days
- Update delayed
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Bazel rules to build Swift on Apple and Linux platforms
Developer ToolsREADME.md
OriginalSwift Rules for Bazel
This repository contains rules for Bazel that can be used to build Swift libraries, tests, and executables for macOS and Linux.
To build applications for all of Apple's platforms (macOS, iOS, tvOS, visionOS, and watchOS), they can be combined with the Apple Rules.
If you run into any problems with these rules, please file an issue!
Basic Examples
Create a simple CLI that can run on macOS, Linux, or Windows:
load("@rules_swift//swift:swift_binary.bzl", "swift_binary")
swift_binary(
name = "cli",
srcs = ["CLI.swift"],
)
Create a single library target that can be used by other targets in your build:
load("@rules_swift//swift:swift_library.bzl", "swift_library")
swift_library(
name = "MyLibrary",
srcs = ["MyLibrary.swift"],
tags = ["manual"],
)
Reference Documentation
Click here for the reference documentation for the rules and other definitions in this repository.
Quick Setup
1. Install Swift
Before getting started, make sure that you have a Swift toolchain installed.
Apple users: Install Xcode. If this is your first time installing it, make sure to open it once after installing so that the command line tools are correctly configured.
Linux users: Follow the instructions on the Swift download page to download and install the appropriate Swift toolchain for your platform. Take care to ensure that you have all of Swift's dependencies installed (such as ICU, Clang, and so forth), and also ensure that the Swift compiler is available on your system path.
2. Configure your workspace
Copy the MODULE.bazel snippet from the releases page.
3. Additional configuration (Linux only)
The swift_binary and swift_test rules expect to use clang as the driver
for linking, and they query the Bazel C++ API and CROSSTOOL to determine which
arguments should be passed to the linker. By default, the C++ toolchain used by
Bazel is gcc, so Swift users on Linux need to override this by setting the
environment variable CC=clang when invoking Bazel.
This step is not necessary for macOS users because the Xcode toolchain always
uses clang.
Building with a Standalone Swift Toolchain
As an alternative to the host's Swift install, rules_swift can download
and register a hermetic Swift toolchain from swift.org. See
doc/standalone_toolchain.md for setup
instructions.
Building with Custom Toolchains
macOS hosts: You can build with a custom Swift toolchain (downloaded from https://swift.org/download) instead of Xcode's default. To do so, pass the following flag to Bazel:
--action_env=TOOLCHAINS=toolchain.id
Where toolchain.id is the value of the CFBundleIdentifier key in the
toolchain's Info.plist file.
To list the available toolchains and their bundle identifiers, you can run:
bazel run @rules_swift//tools/dump_toolchains
Linux hosts: At this time, Bazel uses whichever swift executable is
encountered first on your PATH.
Supporting debugging
To make cacheable builds work correctly with debugging see this doc.
For explicit module builds, see debugging with explicit modules.
Swift Package Manager Support
To download, build, and reference external Swift packages as Bazel targets, check out rules_swift_package_manager.
Supported Xcode versions
rules_swift is heavily tied to the Swift compiler's current feature
set. We have the ability to add / remove flags based on the current
Xcode / Swift version, but overtime we like to reduce the maintenance
cost of this type of branch and remove support for older versions. We
attempt to do this conservatively and are open to supporting more
versions if there is a need.
| Xcode release | Minimum supported rules version | Final supported rules version |
|---|---|---|
| 27.x | unknown | current |
| 26.x | unknown | current |
| 16.x | unknown | current |
Supported bazel versions
rules_apple and rules_swift are often affected by changes in bazel itself. This means you generally need to update these rules as you update bazel.
You can also see the supported bazel versions in the notes for each release on the releases page.
Besides these constraint this repo follows semver as best as we can since the 1.0.0 release.
| Bazel release | Minimum supported rules version | Final supported rules version |
|---|---|---|
| 10.x (most recent rolling) | 3.5.0 | current |
| 9.x | 3.5.0 | current |
| 8.x | 1.14.0 | current |
| 7.x | 1.8.0 | 3.6.1 |
| 6.x | 0.27.0 | 2.8.2 |
| 5.x | 0.25.0 | 1.14.0 |
| 4.x | 0.19.0 | 0.24.0 |
| 3.x | 0.14.0 | 0.18.0 |