bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-30 22:41:22 +00:00
Code Issues Releases Activity
rules_cc/.bazelci/presubmit.yml

52 lines
1.4 KiB
YAML
Raw Normal View History

Add initial bazelci config for rules_cc RELNOTES: None. PiperOrigin-RevId: 228509583
2019-01-09 14:51:39 +00:00
---
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
x_defaults:
# YAML has a feature for "repeated nodes", BazelCI is fine with extra nodes
# it doesn't know about; so that is used to avoid repeating common subparts.
common: &common
# We have to list every package because even with exclusion notation -//foo
# Bazel will load the excluded package and it will be an error because at
# release Bazel the cc_libraries do not have all the attributes.
Add initial bazelci config for rules_cc RELNOTES: None. PiperOrigin-RevId: 228509583
2019-01-09 14:51:39 +00:00
build_targets:
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
- "//:all"
- "//cc:all"
- "//cc/private/rules_impl:all"
Automated rollback of commit 48881f1f453c963e49044210bb1d09b354c83f67. *** Reason for rollback *** Broke a test *** Original change description *** The auto-configured toolchains provided by Bazel itself have diverged heavily from the version maintained in this repo. There is no need to maintain this duplication until Starlarkification has progressed succiciently for rules_cc to be the source of truth for them. This is particularly relevant for Bzlmod, which currently uses the toolchains defined in rules_cc. As a result, Bazel C++ builds will use subtly different toolchains depending on whether --enable_bzlmod is used or not. This is fixed... *** PiperOrigin-RevId: 501228335 Change-Id: I858dc3ea44df7ae70b5603f6dc2e082b4540c42a
2023-01-11 10:47:44 +00:00
- "//cc/private/toolchain:all"
- "//cc/runfiles:all"
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
- "//examples:all"
- "//examples/my_c_archive:all"
- "//examples/my_c_compile:all"
- "//examples/write_cc_toolchain_cpu:all"
- "//tools/migration:all"
Add initial bazelci config for rules_cc RELNOTES: None. PiperOrigin-RevId: 228509583
2019-01-09 14:51:39 +00:00
test_flags:
Adds integration test for cc_shared_library. We use BUILD example added in previous CL and inspect the resulting *.so files with nm. Also fixes implementation of shared library to work with Bazel after having flipped the legacy whole archive flag. This caused exported libraries to be dropped by the linker unless they were alwayslink. Still more tests to come. RELNOTES:none PiperOrigin-RevId: 280640226 Change-Id: I34b48ce7379536352f87b703580083eb85ca67b3
2019-11-15 13:36:25 +00:00
- "--test_timeout=120"
Add initial bazelci config for rules_cc RELNOTES: None. PiperOrigin-RevId: 228509583
2019-01-09 14:51:39 +00:00
test_targets:
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
- "//:all"
- "//cc:all"
- "//cc/private/rules_impl:all"
Automated rollback of commit 48881f1f453c963e49044210bb1d09b354c83f67. *** Reason for rollback *** Broke a test *** Original change description *** The auto-configured toolchains provided by Bazel itself have diverged heavily from the version maintained in this repo. There is no need to maintain this duplication until Starlarkification has progressed succiciently for rules_cc to be the source of truth for them. This is particularly relevant for Bzlmod, which currently uses the toolchains defined in rules_cc. As a result, Bazel C++ builds will use subtly different toolchains depending on whether --enable_bzlmod is used or not. This is fixed... *** PiperOrigin-RevId: 501228335 Change-Id: I858dc3ea44df7ae70b5603f6dc2e082b4540c42a
2023-01-11 10:47:44 +00:00
- "//cc/private/toolchain:all"
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
- "//examples:all"
- "//examples/my_c_archive:all"
- "//examples/my_c_compile:all"
- "//examples/write_cc_toolchain_cpu:all"
- "//tools/migration:all"
buildifier:
version: latest
warnings: "all"
tasks:
Add initial bazelci config for rules_cc RELNOTES: None. PiperOrigin-RevId: 228509583
2019-01-09 14:51:39 +00:00
ubuntu1804:
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
<<: *common
Add initial bazelci config for rules_cc RELNOTES: None. PiperOrigin-RevId: 228509583
2019-01-09 14:51:39 +00:00
macos:
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
<<: *common
Add initial bazelci config for rules_cc RELNOTES: None. PiperOrigin-RevId: 228509583
2019-01-09 14:51:39 +00:00
windows:
Adds example usage of cc_shared_library This is only tested with Bazel at head. We modify the presubmits file so that we don't use release. The reason we don't use release is because we need very recent changes to Bazel to test cc_shared_library. In the future we will also test with release. Also in following CLs, we will inspect in integration test the *.so output from these example builds to make sure that the correct symbols are linked statically and are visible. After that we will add Starlark unit test to check error conditions. RELNOTES:none PiperOrigin-RevId: 280381939 Change-Id: I5de9b364a2a3db28d99558fbfca7bea8052e5114
2019-11-14 10:03:04 +00:00
<<: *common
Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/165 BEGIN_PUBLIC Copybara import of the project: -- 56e69b82484f1a9fb55d8173cc112f9f608f3581 by Fabian Meumertzheim <fabian@meumertzhe.im>: Simplify WORKSPACE setup and update ancient deps By removing a single unused `bzl_library` target, rules_cc no longer has any dependencies that would need to be loaded by a dependency macro. The existing macro is made a no-op. The few needed Bazel Federation dependencies are inlined and, in the case of bazel_skylib and abseil-py, updated to modern versions. Also reorders `WORKSPACE` to list direct dependencies first and keeps `MODULE.bazel` in sync with the dependency versions used in WORKSPACE. The `ubuntu1604` CI pipeline is removed as the version of Python used by it is no longer supported and the distribution is EOL. Instead, a new pipeline is added to check the Bzlmod build. END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/165 from fmeum:fix-workspace-module 56e69b82484f1a9fb55d8173cc112f9f608f3581 PiperOrigin-RevId: 501245864 Change-Id: Ib71ad910705807a00929a76774387a38d2da0f9f
2023-01-11 12:32:58 +00:00
ubuntu_bzlmod:
name: Bzlmod
platform: ubuntu1804
build_flags:
- "--enable_bzlmod"
- "--ignore_dev_dependency"
build_targets:
- "//cc/..."
Copy permalink