Skip to content

bazel: make environment compatible with more operating systems. #7086

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maliberty merged 1 commit into from
Apr 10, 2025
Merged

bazel: make environment compatible with more operating systems. #7086

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .bazelrc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ test --test_timeout=300,1800,1800,9600
common --incompatible_disallow_empty_glob

build --cxxopt "-std=c++17" --host_cxxopt "-std=c++17"
build --cxxopt "-xc++" --host_cxxopt "-xc++"
build --cxxopt "-ffp-contract=off" --host_cxxopt "-ffp-contract=off"

# allow exceptions.
Expand Down
11 changes: 11 additions & 0 deletions MODULE.bazel
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,17 @@ bazel_dep(name = "platforms", version = "0.0.11")
bazel_dep(name = "bazel_skylib", version = "1.7.1")
bazel_dep(name = "rules_flex", version = "0.3.1")
bazel_dep(name = "rules_bison", version = "0.3.1")

# The current rules_cc 0.1.1 hardcodes script locations to `#!/bin/bash`
# instead of using `#!/usr/bin/env bash`.
# This is fixed by https://github.com/bazelbuild/rules_cc/pull/306 but
Copy link
Member

@maliberty maliberty Apr 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is closed as of three weeks ago. Is it going to be released?

Copy link
Collaborator Author

@hzeller hzeller Apr 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is in the repo, but they have not cut a release yet.

Copy link
Member

@maliberty maliberty Apr 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird - it says closed not merged.

# is not released yet. Use rules_cc from that commit.
bazel_dep(name = "rules_cc", version = "0.1.1")
git_override(
module_name = "rules_cc",
commit = "d74915024017250e46d95e91a3defc34174effe0",
remote = "https://github.com/bazelbuild/rules_cc",
)

# Not all boost libs are available at the latest version yet, so use a
# slightly older one that has all we need.
Expand Down Expand Up @@ -64,4 +74,5 @@ llvm.toolchain(
use_repo(llvm, "llvm_toolchain")
# use_repo(llvm, "llvm_toolchain_llvm") # if you depend on specific tools in scripts

# FYI: Comment out on NixOS where you'd like to use the local clang toolchain.
register_toolchains("@llvm_toolchain//:all")
18 changes: 0 additions & 18 deletions MODULE.bazel.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.