build: switch to build settings for static build

This switches the way to select static linking for C builds from a
constraint_setting to a build_setting. The benefit of this is that the
transition to static linking no longer depends on the architecture,
because this setting is not part of the platform anymore.

The alternative would be to select the matching static platform based on
the architecture in the transition implementation. However, I did not
find a good way to obtain the architecture in a transition
implementation. You can access the platform through the settings
parameter, but it's not clear how to extract the architecture from that.
Something that would work is to define an attribute for the architecture
on the rule where the transition is used, and fill this attribute using
a select() at the point where the rule is instantiated. But this
requires changes to all rules which use the transition, which is ugly.

Change-Id: I8962e24b561b8d1724bac785cb3739cdc434d47e
Reviewed-on: https://review.monogon.dev/c/monogon/+/4172
Tested-by: Jenkins CI
Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
6 files changed
tree: bf5fffb68a6cccf4d47505173e036f047979614e
  1. .vscode/
  2. build/
  3. cloud/
  4. go/
  5. intellij/
  6. metropolis/
  7. osbase/
  8. third_party/
  9. tools/
  10. version/
  11. .bazelignore
  12. .bazelproject
  13. .bazelrc
  14. .bazelrc.ci
  15. .bazelrc.sandboxroot
  16. .bazelversion
  17. .git-ignore-revs
  18. .gitignore
  19. BUILD.bazel
  20. CODING_STANDARDS.md
  21. go.mod
  22. go.sum
  23. LICENSE
  24. MODULE.bazel
  25. MODULE.bazel.lock
  26. README.md
  27. SETUP.md
  28. shell.nix
  29. WORKSPACE
README.md

Monogon Monorepo

This is the main repository containing the source code for the Monogon Platform.

This is pre-release software - take a look, and check back later! In the meantime, join us on Matrix (#monogon-os-community:matrix.org) or Discord.

Environment

Our build environment is self-contained and requires only minimal host dependencies:

  • A Linux machine or VM.
  • Bazelisk >= v1.15.0 (or a working Nix environment).
  • A reasonably recent kernel with user namespaces enabled.
  • Working KVM with access to /dev/kvm (if you want to run tests).

Our docs assume that Bazelisk is available as bazel on your PATH.

Refer to SETUP.md for detailed instructions.

Monogon OS

The source code lives in //metropolis (Metropolis is the codename of Monogon OS).

See the //metropolis/README.md for a developer quick start guide, or see the Monogon OS Handbook for user documentation.