bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
rules_cc/WORKSPACE

77 lines
2.4 KiB
Python
Raw Permalink Normal View History

C++: Add defs.bzl to genproto.bzl RELNOTES: PiperOrigin-RevId: 258767676 Change-Id: I72c1a4b10daa62c996472b4ed03659bc2ae99d48
2019-07-18 14:40:33 +00:00
workspace(name = "rules_cc")
Add things needed for rules_cc to build & test in the open * Adding .gitignore * Referencing protobuf, absl, and six in the WORKSPACE * Adding six.BUILD RELNOTES: None PiperOrigin-RevId: 228309963
2019-01-08 12:51:36 +00:00
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
Stop depending on rules_pkg through the federation See discussion on https://github.com/bazelbuild/bazel-federation/issues/117
2020-07-28 12:15:43 +00:00
http_archive(
name = "rules_pkg",
urls = [
"https://github.com/bazelbuild/rules_pkg/releases/download/0.2.5/rules_pkg-0.2.5.tar.gz",
"https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.2.5/rules_pkg-0.2.5.tar.gz",
],
sha256 = "352c090cc3d3f9a6b4e676cf42a6047c16824959b438895a76c2989c6d7c246a",
)
load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
rules_pkg_dependencies()
Add things needed for rules_cc to build & test in the open * Adding .gitignore * Referencing protobuf, absl, and six in the WORKSPACE * Adding six.BUILD RELNOTES: None PiperOrigin-RevId: 228309963
2019-01-08 12:51:36 +00:00
http_archive(
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
name = "bazel_federation",
Use latest federation version This version includes rules_pkg 0.2.4, which contains the fix required to cut a first rules_cc release.
2019-09-30 13:10:00 +00:00
sha256 = "33222ab7bcc430f1ff1db8788c2e0118b749319dd572476c4fd02322d7d15792",
strip_prefix = "bazel-federation-f0e5eda7f0cbfe67f126ef4dacb18c89039b0506",
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
type = "zip",
Fix buildifier warnings in @rules_cc Fixes: * Enabled buildifier on the Bazel CI again * Added Skydocs where missing * Moved public files out of .../private/... (e.g. cc_toolchain_config_lib.bzl) * Reformatted * Removed unused loads * Using relative labels for cc_configure related files * Added development dependency on rules_proto * they're not in the federation yet, so hand rolling in rules_cc's WORKSPACE file * Added development dependency on rules_python (from federation) * Cleaned up copybara (notable change - not using @rules_cc in labels inside rules_cc repo) * Made cc_flags_supplier usable internally * Moved load statements to the top of the bzl file * Moved runfiles to the tools directory * Unified toolchain_utils.bzl and find_cc_toolchain.bzl RELNOTES: None. PiperOrigin-RevId: 276479521 Change-Id: I3196896061fa2ee61a3efb130c214d288782066a
2019-10-24 14:01:01 +00:00
url = "https://github.com/bazelbuild/bazel-federation/archive/f0e5eda7f0cbfe67f126ef4dacb18c89039b0506.zip", # 2019-09-30
Add things needed for rules_cc to build & test in the open * Adding .gitignore * Referencing protobuf, absl, and six in the WORKSPACE * Adding six.BUILD RELNOTES: None PiperOrigin-RevId: 228309963
2019-01-08 12:51:36 +00:00
)
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
load("@bazel_federation//:repositories.bzl", "rules_cc_deps")
Fix buildifier warnings in @rules_cc Fixes: * Enabled buildifier on the Bazel CI again * Added Skydocs where missing * Moved public files out of .../private/... (e.g. cc_toolchain_config_lib.bzl) * Reformatted * Removed unused loads * Using relative labels for cc_configure related files * Added development dependency on rules_proto * they're not in the federation yet, so hand rolling in rules_cc's WORKSPACE file * Added development dependency on rules_python (from federation) * Cleaned up copybara (notable change - not using @rules_cc in labels inside rules_cc repo) * Made cc_flags_supplier usable internally * Moved load statements to the top of the bzl file * Moved runfiles to the tools directory * Unified toolchain_utils.bzl and find_cc_toolchain.bzl RELNOTES: None. PiperOrigin-RevId: 276479521 Change-Id: I3196896061fa2ee61a3efb130c214d288782066a
2019-10-24 14:01:01 +00:00
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
rules_cc_deps()
Add things needed for rules_cc to build & test in the open * Adding .gitignore * Referencing protobuf, absl, and six in the WORKSPACE * Adding six.BUILD RELNOTES: None PiperOrigin-RevId: 228309963
2019-01-08 12:51:36 +00:00
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
load("@bazel_federation//setup:rules_cc.bzl", "rules_cc_setup")
Fix buildifier warnings in @rules_cc Fixes: * Enabled buildifier on the Bazel CI again * Added Skydocs where missing * Moved public files out of .../private/... (e.g. cc_toolchain_config_lib.bzl) * Reformatted * Removed unused loads * Using relative labels for cc_configure related files * Added development dependency on rules_proto * they're not in the federation yet, so hand rolling in rules_cc's WORKSPACE file * Added development dependency on rules_python (from federation) * Cleaned up copybara (notable change - not using @rules_cc in labels inside rules_cc repo) * Made cc_flags_supplier usable internally * Moved load statements to the top of the bzl file * Moved runfiles to the tools directory * Unified toolchain_utils.bzl and find_cc_toolchain.bzl RELNOTES: None. PiperOrigin-RevId: 276479521 Change-Id: I3196896061fa2ee61a3efb130c214d288782066a
2019-10-24 14:01:01 +00:00
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
rules_cc_setup()
Update rules_go to 0.18.1 [Copybara import of https://github.com/bazelbuild/rules_cc/pull/9] Merge 6181c870fcda4ba6bdc9618ee5fdf12c17c9d3e4 into 2312d7213425d868a54983f963c3e3d80b262558 PiperOrigin-RevId: 240145582
2019-03-25 15:38:55 +00:00
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
#
# Dependencies for development of rules_cc itself.
#
load("//:internal_deps.bzl", "rules_cc_internal_deps")
Fix buildifier warnings in @rules_cc Fixes: * Enabled buildifier on the Bazel CI again * Added Skydocs where missing * Moved public files out of .../private/... (e.g. cc_toolchain_config_lib.bzl) * Reformatted * Removed unused loads * Using relative labels for cc_configure related files * Added development dependency on rules_proto * they're not in the federation yet, so hand rolling in rules_cc's WORKSPACE file * Added development dependency on rules_python (from federation) * Cleaned up copybara (notable change - not using @rules_cc in labels inside rules_cc repo) * Made cc_flags_supplier usable internally * Moved load statements to the top of the bzl file * Moved runfiles to the tools directory * Unified toolchain_utils.bzl and find_cc_toolchain.bzl RELNOTES: None. PiperOrigin-RevId: 276479521 Change-Id: I3196896061fa2ee61a3efb130c214d288782066a
2019-10-24 14:01:01 +00:00
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
rules_cc_internal_deps()
Add skylib dependency [Copybara import of https://github.com/bazelbuild/rules_cc/pull/10] Skylib will be used to check minimum supported Bazel version. Merge 2e5b5eb2d04a7a87970f6441c5b782e0954bea14 into 3723b4c35f361ba5593d00c1f4183b387402fef5 PiperOrigin-RevId: 240725578
2019-03-28 07:52:04 +00:00
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
load("//:internal_setup.bzl", "rules_cc_internal_setup")
Fix buildifier warnings in @rules_cc Fixes: * Enabled buildifier on the Bazel CI again * Added Skydocs where missing * Moved public files out of .../private/... (e.g. cc_toolchain_config_lib.bzl) * Reformatted * Removed unused loads * Using relative labels for cc_configure related files * Added development dependency on rules_proto * they're not in the federation yet, so hand rolling in rules_cc's WORKSPACE file * Added development dependency on rules_python (from federation) * Cleaned up copybara (notable change - not using @rules_cc in labels inside rules_cc repo) * Made cc_flags_supplier usable internally * Moved load statements to the top of the bzl file * Moved runfiles to the tools directory * Unified toolchain_utils.bzl and find_cc_toolchain.bzl RELNOTES: None. PiperOrigin-RevId: 276479521 Change-Id: I3196896061fa2ee61a3efb130c214d288782066a
2019-10-24 14:01:01 +00:00
Fetch dependencies through the Bazel federation. As a result of this commit, rules_cc now contains the required bzl files to be tested as part of the Bazel federation.
2019-08-09 13:41:00 +00:00
rules_cc_internal_setup()
C++: Move tools/cpp from bazel_tools to rules_cc Here we are duplicating bazel_tools/tools/cpp. The goal is for the BUILD files in bazel_tools/tools/cpp to have an alias that point to rules_cc. Then later on with the incompatible flag these aliases will no longer be valid. Working towards #8743 RELNOTES:none PiperOrigin-RevId: 264604076 Change-Id: I389702793a1a95b0990dce93577de2b7182e2e6b
2019-08-21 14:29:46 +00:00
http_archive(
name = "com_google_googletest",
Actually, lets depend on the release archive, not the branch
2019-10-09 13:18:06 +00:00
sha256 = "9dc9157a9a1551ec7a7e43daea9a694a0bb5fb8bec81235d8a1e6ef64c716dcb",
strip_prefix = "googletest-release-1.10.0",
C++: Move tools/cpp from bazel_tools to rules_cc Here we are duplicating bazel_tools/tools/cpp. The goal is for the BUILD files in bazel_tools/tools/cpp to have an alias that point to rules_cc. Then later on with the incompatible flag these aliases will no longer be valid. Working towards #8743 RELNOTES:none PiperOrigin-RevId: 264604076 Change-Id: I389702793a1a95b0990dce93577de2b7182e2e6b
2019-08-21 14:29:46 +00:00
urls = [
Actually, lets depend on the release archive, not the branch
2019-10-09 13:18:06 +00:00
"https://mirror.bazel.build/github.com/google/googletest/archive/release-1.10.0.tar.gz",
"https://github.com/google/googletest/archive/release-1.10.0.tar.gz",
C++: Move tools/cpp from bazel_tools to rules_cc Here we are duplicating bazel_tools/tools/cpp. The goal is for the BUILD files in bazel_tools/tools/cpp to have an alias that point to rules_cc. Then later on with the incompatible flag these aliases will no longer be valid. Working towards #8743 RELNOTES:none PiperOrigin-RevId: 264604076 Change-Id: I389702793a1a95b0990dce93577de2b7182e2e6b
2019-08-21 14:29:46 +00:00
],
)
Fix buildifier warnings in @rules_cc Fixes: * Enabled buildifier on the Bazel CI again * Added Skydocs where missing * Moved public files out of .../private/... (e.g. cc_toolchain_config_lib.bzl) * Reformatted * Removed unused loads * Using relative labels for cc_configure related files * Added development dependency on rules_proto * they're not in the federation yet, so hand rolling in rules_cc's WORKSPACE file * Added development dependency on rules_python (from federation) * Cleaned up copybara (notable change - not using @rules_cc in labels inside rules_cc repo) * Made cc_flags_supplier usable internally * Moved load statements to the top of the bzl file * Moved runfiles to the tools directory * Unified toolchain_utils.bzl and find_cc_toolchain.bzl RELNOTES: None. PiperOrigin-RevId: 276479521 Change-Id: I3196896061fa2ee61a3efb130c214d288782066a
2019-10-24 14:01:01 +00:00
http_archive(
name = "rules_proto",
sha256 = "602e7161d9195e50246177e7c55b2f39950a9cf7366f74ed5f22fd45750cd208",
strip_prefix = "rules_proto-97d8af4dc474595af3900dd85cb3a29ad28cc313",
urls = [
"https://mirror.bazel.build/github.com/bazelbuild/rules_proto/archive/97d8af4dc474595af3900dd85cb3a29ad28cc313.tar.gz",
"https://github.com/bazelbuild/rules_proto/archive/97d8af4dc474595af3900dd85cb3a29ad28cc313.tar.gz",
],
)
load("@rules_proto//proto:repositories.bzl", "rules_proto_dependencies", "rules_proto_toolchains")
rules_proto_dependencies()
rules_proto_toolchains()
Add rules_cc_toolchains to repositories.bzl This is the new entry point for registering C++ toolchains (replacing implicit cc_configure()). While at it, fix one misnamed function.
2019-11-01 15:36:34 +00:00
load("//cc:repositories.bzl", "rules_cc_toolchains")
Remove need for exported_by or linked_statically_by For now we will restrict allowed exports to the same package. At the same time static_deps should be used to take into account what should be linked into a shared library. RELNOTES:none PiperOrigin-RevId: 294668451 Change-Id: Ia087519106983bfa9a980e471d3102ab391a53eb
2020-02-12 16:01:29 +00:00
Fix call in WORKSPACE
2019-11-01 15:39:47 +00:00
rules_cc_toolchains()
Remove need for exported_by or linked_statically_by For now we will restrict allowed exports to the same package. At the same time static_deps should be used to take into account what should be linked into a shared library. RELNOTES:none PiperOrigin-RevId: 294668451 Change-Id: Ia087519106983bfa9a980e471d3102ab391a53eb
2020-02-12 16:01:29 +00:00
local_repository(
name = "test_repo",
path = "examples/test_cc_shared_library2",
)