rules_cc
rules_apple
Our great sponsors
| rules_cc | rules_apple | |
|---|---|---|
| 2 | 1 | |
| 161 | 474 | |
| 1.9% | 2.5% | |
| 6.1 | 9.5 | |
| 7 days ago | 7 days ago | |
| Starlark | Starlark | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rules_cc
-
What's New in Bazel 6.0
Not that I'd recommend it, but if you symlink your system library into the bazel build area, as long as your sandboxing setup don't hose you (or you just turn it off), bazel will track system tools/library in the same way as everything else.
Bazel's rules_cc even has a system_library.bzl you can import a `system_library` from that automates this for you. https://github.com/bazelbuild/rules_cc/blob/main/cc/system_l...
I'd still recommend building everything from scratch (and understanding the relationships and graph of your dependencies), but if your build isn't that complicated and you want to role the dice on UB, this isn't that hard.
As an aside, the most galling part of bazel's cache key calculations has to be that it's up to the individual rules to implement this how they see fit. The rules native to bazel written in java vary wildly compared to starlark-written rules. On thing you (or someone in your org) end up becoming pretty comfortable with while using bazel in anger is RTFC.
-
[Windows] Resource .rc file compilation?
I found several associated issues and a closed PR that supposedly solved this issue. However, it seems that cc_rules has undergone several changes and this PR likely wouldn't function.
rules_apple
-
A Comprehensive guide to build a cross-platform application by Bazel
git_repository( name = "build_bazel_rules_apple", remote = "https://github.com/bazelbuild/rules_apple.git", tag = "1.1.3", ) git_repository( name = "build_bazel_rules_swift", remote = "https://github.com/bazelbuild/rules_swift.git", tag = "1.2.0", ) load("@build_bazel_rules_swift//swift:repositories.bzl", "swift_rules_dependencies") swift_rules_dependencies()
What are some alternatives?
rules_scala - Scala rules for Bazel
sml_rules - Bazel SML rules provide the necessary rules to build and test SML (Standard ML) applications using Bazel.
rules_nodejs - NodeJS toolchain for Bazel.
platforms - Constraint values for specifying platforms and toolchains
bazel_static_dynamic_c_demo - Internet Points
rules_android - Android rules for Bazel
rules_docker - Rules for building and handling Docker images with Bazel
rules_apko - Bazel rules for apko
Bazel - a fast, scalable, multi-language and extensible build system
rules_graalvm - Build GraalVM native binaries with Bazel
bazel-central-registry - The central registry of Bazel modules for the Bzlmod external dependency system.
rules_r - R rules for Bazel