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

17 lines
300 B
Python
Raw Normal View History

Internal change PiperOrigin-RevId: 225221110
2018-12-12 19:24:00 +00:00
package(default_visibility = ["//visibility:public"])
licenses(["notice"])
exports_files(["LICENSE"])
Use rules_pkg for building releases This commit allows the creation of distributions, with 0.0.1 being the first version. See distro/README.md for details on how to build a release. This commit also uses a new version of the Bazel federation that contains rules_pkg 0.2.2 instead of 0.2.1. There are still some problems with the WORKSPACE stanza that is being printed by the release notes generation script, though: - It references a //cc:deps.bzl file, which doesn't exist. I have to modify the scripts in rules_pkg to support a flag like 'has_deps'. - It doesn't support the Bazel federation yet, since it always tells users to download code from the rules_cc repository.
2019-09-13 16:24:56 +00:00
filegroup(
name = "distribution",
Make Buildifier happy
2019-09-30 13:58:14 +00:00
srcs = [
rules_cc: Add top-level BUILD file to distribution. Before this commit Bazel could not use the distribution since it failed with "Every .bzl file must have a corresponding package, but '@rules_cc//:internal_deps.bzl' does not have one." https://buildkite.com/bazel/bazel-federation-distro-pre-release-testing/builds/20#29164fc9-b0bb-41aa-b62f-e2f3f20e9efc PiperOrigin-RevId: 275263945 Change-Id: I12216f2070ddc579f553a22975790bbc9a18f0f9
2019-10-17 15:30:31 +00:00
"BUILD",
Use rules_pkg for building releases This commit allows the creation of distributions, with 0.0.1 being the first version. See distro/README.md for details on how to build a release. This commit also uses a new version of the Bazel federation that contains rules_pkg 0.2.2 instead of 0.2.1. There are still some problems with the WORKSPACE stanza that is being printed by the release notes generation script, though: - It references a //cc:deps.bzl file, which doesn't exist. I have to modify the scripts in rules_pkg to support a flag like 'has_deps'. - It doesn't support the Bazel federation yet, since it always tells users to download code from the rules_cc repository.
2019-09-13 16:24:56 +00:00
"LICENSE",
Add missing bzl files to rules_cc distribution. PiperOrigin-RevId: 272505874 Change-Id: I68d1b43c859db54abf3da71ce1e11d5c15567257
2019-10-02 20:24:51 +00:00
"internal_deps.bzl",
"internal_setup.bzl",
Make Buildifier happy
2019-09-30 13:58:14 +00:00
],
Use rules_pkg for building releases This commit allows the creation of distributions, with 0.0.1 being the first version. See distro/README.md for details on how to build a release. This commit also uses a new version of the Bazel federation that contains rules_pkg 0.2.2 instead of 0.2.1. There are still some problems with the WORKSPACE stanza that is being printed by the release notes generation script, though: - It references a //cc:deps.bzl file, which doesn't exist. I have to modify the scripts in rules_pkg to support a flag like 'has_deps'. - It doesn't support the Bazel federation yet, since it always tells users to download code from the rules_cc repository.
2019-09-13 16:24:56 +00:00
visibility = ["@//distro:__pkg__"],
Merge pull request #35 from fweikert:distro PiperOrigin-RevId: 272444545 Change-Id: I8d582773c5ef124ecafe77a353434887f1abc1aa
2019-10-02 15:49:43 +00:00
)