| commit | dd8317883cd9b329393a539be6b132ee3979687d | [log] [tgz] |
|---|---|---|
| author | PikachuHy <pikachuhy@linux.alibaba.com> | Fri Jun 14 03:59:43 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 14 04:00:58 2024 -0700 |
| tree | 7fe9f0284e1feca31a30954730571e86f413046b | |
| parent | 3aec1bcfc34850966fa9508b8dd046ed4e945eb0 [diff] |
[1/5] support C++20 Modules, add module_interfaces attr I split the XXL PR https://github.com/bazelbuild/bazel/pull/19940 into several small patches. This is the first patch of Support C++20 Modules, I add `module_interfaces` attr only example - foo.cppm ``` // foo.cppm export module foo; // ... ``` - BUILD.bazel ``` cc_library( name="foo", copts=["-std=c++20"], module_interfaces=["foo.cppm"], # features=["cpp20_module"] ) ``` build failed with the following message ``` ➜ bazel build :foo ERROR: bazel_demo/BUILD.bazel:1:11: in cc_library rule //:foo: Traceback (most recent call last): File "/virtual_builtins_bzl/common/cc/cc_library.bzl", line 40, column 42, in _cc_library_impl File "/virtual_builtins_bzl/common/cc/semantics.bzl", line 123, column 13, in _check_can_module_interfaces Error in fail: attribute module_interfaces: requires --experimental_cpp20_modules ERROR: bazel_demo/BUILD.bazel:1:11: Analysis of target '//:foo' failed ERROR: Analysis of target '//:foo' failed; build aborted INFO: Elapsed time: 0.106s, Critical Path: 0.00s INFO: 1 process: 1 internal. ERROR: Build did NOT complete successfully ``` To build with C++20 Modules, the flag `--experimental_cpp20_modules` must be added. ``` ➜ bazel build :foo --experimental_cpp20_modules ERROR: bazel_demo/BUILD.bazel:1:11: in cc_library rule //:foo: Traceback (most recent call last): File "/virtual_builtins_bzl/common/cc/cc_library.bzl", line 41, column 34, in _cc_library_impl File "/virtual_builtins_bzl/common/cc/cc_helper.bzl", line 1225, column 13, in _check_cpp20_modules Error in fail: to use C++20 Modules, the feature cpp20_modules must be enabled ERROR: bazel_demo/BUILD.bazel:1:11: Analysis of target '//:foo' failed ERROR: Analysis of target '//:foo' failed; build aborted INFO: Elapsed time: 0.091s, Critical Path: 0.00s INFO: 1 process: 1 internal. ERROR: Build did NOT complete successfully ``` To build with C++20 Modules, the feature `cpp20_modules` must be enabled. ``` bazel build :foo --experimental_cpp20_modules --features cpp20_modules ``` the flag `--experimental_cpp20_modules` works on global and the feature `cpp20_modules` work on each target but in this patch, do nothing with C++20 Module Interfaces. Closes #22425. PiperOrigin-RevId: 643303029 Change-Id: I08d8a1186d2ddd1c632f1e768442e504b87a0691
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
