Skip to content

Remove all warnings features - #122

Open
nradakovic wants to merge 1 commit into
mainfrom
nira_migrate_warnigns
Open

Remove all warnings features#122
nradakovic wants to merge 1 commit into
mainfrom
nira_migrate_warnigns

Conversation

@nradakovic

Copy link
Copy Markdown
Member

All warnings features are now defined within score_cpp_policies so we have to remove them from here.

All warnings features are now defined within `score_cpp_policies`
so we have to remove them from here.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR removes the built-in warning-flag feature definitions from the Linux and QNX C/C++ toolchain templates, based on the assumption that warning features are now provided externally (e.g., via score_cpp_policies) rather than by this repository’s toolchain implementation.

Changes:

  • Removed warning flag groups (minimal/strict/all/-Werror) from Linux and QNX cc_toolchain_flags.bzl.template.
  • Removed corresponding warning features and flags.bzl loads from Linux and QNX cc_toolchain_config.bzl.template.
  • Removed the warning features from the toolchain features = [...] lists so they’re no longer registered by default.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
templates/qnx/cc_toolchain_flags.bzl.template Removes warning flag groups from the QNX flags template.
templates/qnx/cc_toolchain_config.bzl.template Stops loading/defining warning features in the QNX toolchain config template.
templates/linux/cc_toolchain_flags.bzl.template Removes warning flag groups from the Linux flags template.
templates/linux/cc_toolchain_config.bzl.template Stops loading/defining warning features in the Linux toolchain config template.
Suppressed comments (1)

templates/qnx/cc_toolchain_config.bzl.template:545

  • This removes the built-in warning features from the QNX toolchain (previously minimal_warnings was enabled by default). Any consumer using --features=minimal_warnings|strict_warnings|warnings_as_errors will now get an unknown-feature error unless those features are injected via extra_known_features/extra_enabled_features. The repo docs still describe these as toolchain-provided and note QNX defaults (docs/features.md:90-97; docs/migration_guide.md:98-113). Please update the docs/tests/examples to reflect the new injection requirement (e.g., via score_cpp_policies), or provide a compatibility shim that keeps these feature names registered.
    extra_compile_flags = %{extra_compile_flags}
    extra_compile_flags_feature = feature(
        name = "extra_compile_flags",
        enabled = %{extra_compile_flags_switch},

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines 285 to 287
extra_compile_flags = %{extra_compile_flags}
extra_compile_flags_feature = feature(
name = "extra_compile_flags",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants