bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-27 20:43:26 +00:00
Code Issues Releases Activity
rules_cc/.bazelci/presubmit.yml

67 lines
1.9 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"
- "//cc/private/toolchain:all"
- "//distro:all"
- "//examples:all"
- "//examples/my_c_archive:all"
- "//examples/my_c_compile:all"
- "//examples/write_cc_toolchain_cpu:all"
- "//tools/migration:all"
- "//tools/runfiles: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"
- "//cc/private/toolchain:all"
- "//distro:all"
- "//examples:all"
- "//examples/my_c_archive:all"
- "//examples/my_c_compile:all"
- "//examples/write_cc_toolchain_cpu:all"
- "//tools/migration:all"
- "//tools/runfiles:all"
buildifier:
version: latest
warnings: "all"
tasks:
ubuntu1604:
<<: *common
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
examples:
platform: ubuntu1804
use green instead of downstream green
2021-02-18 16:50:36 +00:00
bazel: last_green
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
- "//examples/test_cc_shared_library/..."
works better?
2021-02-17 15:04:47 +00:00
- "//examples/test_cc_shared_library/diamond_inheritance/..."
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
build_flags:
- "--experimental_cc_shared_library"
Add flags to cc_shared_library for easier debugging --//examples:incompatible_link_once=False[default = False] When True, it will be an error to link the same library more than once unless it has the tag LINKABLE_MORE_THAN_ONCE --//examples:experimental_debug=True[default = False] When True, it will generate files listing the exports of each cc_shared_library and which libraries are linked to it statically. RELNOTES:none PiperOrigin-RevId: 311323625 Change-Id: I340cc71965650f7c9dd7ef7fb9656da362021527
2020-05-13 14:23:47 +00:00
- "--//examples:incompatible_link_once=True"
C++: Make permissions check optional in cc_shared_library The cc_shared_library_permissions mechanism was introduced to add control over which cc_shared_libraries can export a given cc_library. If the repo is big enough, the owner of a cc_library might want to prevent someone else in a different package making their library part of the ABI of a public shared library because that makes it harder to change the cc_library. This does not apply accross repositories because a dependant repository can overwrite anything from a repository dependency anyway. However, it is becoming more apparent than even though this mechanism should exist, it should not be enabled by default since most people don't need it. To enable it pass the flag --//examples:enable_permissions_check=True. RELNOTES:none PiperOrigin-RevId: 363171677 Change-Id: I8afb3294806bb3053ee1279c6e9c5355089bccbb
2021-03-16 13:44:51 +00:00
- "--//examples:enable_permissions_check=True"
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_flags:
- "--test_timeout=120"
- "--experimental_cc_shared_library"
Add flags to cc_shared_library for easier debugging --//examples:incompatible_link_once=False[default = False] When True, it will be an error to link the same library more than once unless it has the tag LINKABLE_MORE_THAN_ONCE --//examples:experimental_debug=True[default = False] When True, it will generate files listing the exports of each cc_shared_library and which libraries are linked to it statically. RELNOTES:none PiperOrigin-RevId: 311323625 Change-Id: I340cc71965650f7c9dd7ef7fb9656da362021527
2020-05-13 14:23:47 +00:00
- "--//examples:incompatible_link_once=True"
C++: Make permissions check optional in cc_shared_library The cc_shared_library_permissions mechanism was introduced to add control over which cc_shared_libraries can export a given cc_library. If the repo is big enough, the owner of a cc_library might want to prevent someone else in a different package making their library part of the ABI of a public shared library because that makes it harder to change the cc_library. This does not apply accross repositories because a dependant repository can overwrite anything from a repository dependency anyway. However, it is becoming more apparent than even though this mechanism should exist, it should not be enabled by default since most people don't need it. To enable it pass the flag --//examples:enable_permissions_check=True. RELNOTES:none PiperOrigin-RevId: 363171677 Change-Id: I8afb3294806bb3053ee1279c6e9c5355089bccbb
2021-03-16 13:44:51 +00:00
- "--//examples:enable_permissions_check=True"
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_targets:
- "//examples/test_cc_shared_library/..."
works better?
2021-02-17 15:04:47 +00:00
- "//examples/test_cc_shared_library/diamond_inheritance/..."
Copy permalink