Toolchain configuration shall not be done per module

[LittleHuba]

We need one toolchain that is similar for all modules. This includes compiler and linker flags. Only that way, we can ensure interoperability between modules.

Therefore the manual configuration of the toolchain per module should not be required (gcc.extra_features(), gcc.warning_flags()).

Instead, the toolchain should come with a finished and complete configuration.

Still, a module should have the capability to disable certain compiler or linker flags via bazle features like treat_warnings_as_errors to work around limitations such as third_party libraries, bugs without clear fix,...

[nradakovic]

I don't fully agree with this approach. The toolchain may need to support different operation modes (e.g., build, run, test), so allowing additional features should remain possible. However, overriding mandatory features shouldn't be allowed.

To support this, the architecture group should define and provide a list of core flags/features required for each module.

[walid-salhi]

Hi @AlexanderLanin
This is an important decision on how to proceed with the setting of the toolchain configuration which involves the Compiler Flags Setting 731
The ticket seems to be forgotten given that there is no updates since 07.07.2025 and no attribute is set since its creation.
Could you please bring it back to discussion as we need it for the issues related to the Compiler Flags Setting.