diff options
-rw-r--r-- | .bazelci/presubmit.yml | 46 | ||||
-rw-r--r-- | AUTHORS | 15 | ||||
-rw-r--r-- | BUILD | 43 | ||||
-rw-r--r-- | CODEOWNERS | 1 | ||||
-rw-r--r-- | CONTRIBUTING.md | 24 | ||||
-rw-r--r-- | LICENSE | 201 | ||||
-rw-r--r-- | METADATA | 13 | ||||
-rw-r--r-- | MODULE.bazel | 7 | ||||
-rw-r--r-- | MODULE_LICENSE_APACHE2 | 0 | ||||
-rw-r--r-- | OWNERS | 1 | ||||
-rw-r--r-- | README.md | 84 | ||||
-rw-r--r-- | WORKSPACE | 12 | ||||
-rw-r--r-- | WORKSPACE.bzlmod | 4 | ||||
-rw-r--r-- | cpu/BUILD | 190 | ||||
-rw-r--r-- | distro/README.md | 47 | ||||
-rwxr-xr-x | distro/makerel.sh | 67 | ||||
-rw-r--r-- | os/BUILD | 124 | ||||
-rw-r--r-- | tests/BUILD | 21 | ||||
-rw-r--r-- | version.bzl | 16 |
19 files changed, 916 insertions, 0 deletions
diff --git a/.bazelci/presubmit.yml b/.bazelci/presubmit.yml new file mode 100644 index 0000000..b24af0f --- /dev/null +++ b/.bazelci/presubmit.yml @@ -0,0 +1,46 @@ +--- +# +# Bazel releases +# +lts: <s + bazel: latest + +rolling: &rolling + bazel: rolling + + +targets: &targets + build_targets: + - "//..." + + +tasks: + ubuntu_lts: + name: ubuntu_lts + platform: ubuntu2004 + <<: *lts + <<: *targets + ubuntu_rolling: + name: ubuntu_rolling + platform: ubuntu2004 + <<: *rolling + <<: *targets + macos_lts: + name: macos_lts + platform: macos + <<: *lts + <<: *targets + windows_lts: + name: windows_lts + platform: windows + <<: *lts + <<: *targets + check_bzlmod: + name: check_bzlmod + # No need to check bzlmod on every platform. This repository only holds + # constants and has no per-platform behavior. + platform: ubuntu2004 + <<: *rolling + <<: *targets + build_flags: + - "--enable_bzlmod" @@ -0,0 +1,15 @@ +# This is the list of bazelbuild/platforms' significant contributors. +# +# This does not necessarily list everyone who has contributed code, +# especially since many employees of one corporation may be contributing. +# To see the full list of contributors, see the revision history in +# source control. + +# Names should be added to this file as: +# Name or Organization <email address> +# The email address is not required for organizations. + +Google Inc. +Austin Schuh <austin.linux@gmail.com> +Lizan Zhou <lizan@tetrate.io> +Mathieu Boespflug <m@tweag.io> @@ -0,0 +1,43 @@ +load("@rules_license//rules:license.bzl", "license") + +package( + default_applicable_licenses = [":license"], + default_visibility = ["//visibility:public"], +) + +license( + name = "license", + license_kinds = [ + "@rules_license//licenses/spdx:Apache-2.0", + ], + license_text = "LICENSE", +) + +exports_files([ + "LICENSE", + "MODULE.bazel", +]) + +filegroup( + name = "srcs", + srcs = [ + "BUILD", + "WORKSPACE", + "//cpu:srcs", + "//os:srcs", + ], +) + +# For use in Incompatible Target Skipping: +# https://docs.bazel.build/versions/main/platforms.html#skipping-incompatible-targets +# +# Specifically this lets targets declare incompatibility with some set of +# platforms. See +# https://docs.bazel.build/versions/main/platforms.html#more-expressive-constraints +# for some more details. +constraint_setting(name = "incompatible_setting") + +constraint_value( + name = "incompatible", + constraint_setting = ":incompatible_setting", +) diff --git a/CODEOWNERS b/CODEOWNERS new file mode 100644 index 0000000..a7a3ff8 --- /dev/null +++ b/CODEOWNERS @@ -0,0 +1 @@ +@aiuto @aragos @gregestren @katre diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..81b7da6 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,24 @@ +# Contributing to Bazel + +## Contributor License Agreement + +Contributions to this project must be accompanied by a Contributor License +Agreement. You (or your employer) retain the copyright to your contribution, +this simply gives us permission to use and redistribute your contributions as +part of the project. Head over to <https://cla.developers.google.com/> to see +your current agreements on file or to sign a new one. + +You generally only need to submit a CLA once, so if you've already submitted one +(even if it was for a different project), you probably don't need to do it +again. + +## Patch Acceptance Process + +The process is described in the [README for this repository](README.md). For +background, you should also understand how to +[contribute to Bazel](https://bazel.build/contributing.html). + +## Setting up your development environment + +Read how to +[set up your development environment](https://bazel.build/contributing.html). @@ -0,0 +1,201 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/METADATA b/METADATA new file mode 100644 index 0000000..481a433 --- /dev/null +++ b/METADATA @@ -0,0 +1,13 @@ +name: "platforms" +description: + "" + +third_party { + identifier { + type: "Git" + value: "https://github.com/bazelbuild/platforms" + } + version: "0.0.1" + last_upgrade_date { year: 2024 month: 1 day: 16 } + license_type: NOTICE +} diff --git a/MODULE.bazel b/MODULE.bazel new file mode 100644 index 0000000..617a84a --- /dev/null +++ b/MODULE.bazel @@ -0,0 +1,7 @@ +module( + name = "platforms", + version = "0.0.8", # keep in sync with version.bzl + compatibility_level = 1, +) + +bazel_dep(name = "rules_license", version = "0.0.7") diff --git a/MODULE_LICENSE_APACHE2 b/MODULE_LICENSE_APACHE2 new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/MODULE_LICENSE_APACHE2 @@ -0,0 +1 @@ +include kernel/build:/OWNERS diff --git a/README.md b/README.md new file mode 100644 index 0000000..99fc7a9 --- /dev/null +++ b/README.md @@ -0,0 +1,84 @@ +# [Bazel Platforms](https://bazel.build) + +This repository houses all canonical +[constraint_setting()](https://bazel.build/reference/be/platforms-and-toolchains#constraint_setting)s, +[constraint_value()](https://bazel.build/reference/be/platforms-and-toolchains#constraint_value)s +and +[platform()](https://bazel.build/reference/be/platforms-and-toolchains#platform)s +that are universally useful across languages and Bazel projects. + +For questions or concerns please email +[bazel-discuss@googlegroups.com](mailto://bazel-discuss@googlegroups.com). + +# Motivation + +Constraints must be carefully organized to avoid fragmentation. If two different +declarations for, say, cpu=x86_64 were to exist at the same time then select() +statements and toolchain selection would stop working across languages and +projects. + +# Process + +This repository only includes truly ubiquitous constraints. + +Most common constraints -- that is settings and values that can be used across +projects - fall into specific areas like "Apple" or "Java". These are declared +in those areas' respective repositories. + +A very few constraints (such as OS and cpu) are relevant for essentially all +projects across all areas. These are what this repository is for. + +# Adding a canonical constraint value + +To add a new canonical constraint value, prepare a PR adding it to that the +appropriate BUILD file. + +Note that even global constraint values are typically area values. For example, +ios is an area value for the global setting os but belongs in the apple area. +For the PR's reviewer(s) choose an owner of this repository plus an owner of the +area repository this references.. + +A constraint value should be: + +- semantically clear, particularly in its distinctions from other values of + the same setting + +- well-named: consistent with existing values of the same setting and easy to + understand at usage sites + +- well-documented + +Remember that this value will apply for the entire Bazel community and its +semantics will be difficult to impossible to change once it starts being used. + +# Adding a canonical constraint setting + +New canonical constraint settings should be rare and well-justified. + +To add a new setting, prepare a design document according to Bazel's design +review process. This document should explain the need for a new setting and why +it belongs here vs. area-specific repositories. It should clearly explain +semantics, initial values, and criteria for adding new values. + +Once the design is approved prepare a PR for the actual change. If any values +are area-specific, include the area repositories' owners as reviewers. + +# Private changes to global constraints + +If you'd like to experiment with changes to global settings or values, you can +fork this repo for experimental purposes. But in the interest of community +health and interoperability please don't share your changes with anyone not +involved with the experiment. For wider distribution, submit a proper change +here. + +Note that you can declare constraint_values in your own repo that are members of +the global constraint_settings. This lets you "extend" global settings within +the confines of your own project. But don't do this if you expect other projects +to use these changes - this can easily lead to fragmentation conflicts. + +If you need custom constaint_settings, just declare them in your own repo. They +are, by definition, not global. + +If you really need a permanent global change and it isn't design-approved for +this repo, start a thread on +[GitHub](https://github.com/bazelbuild/bazel/discussions) to discuss options. diff --git a/WORKSPACE b/WORKSPACE new file mode 100644 index 0000000..172bccc --- /dev/null +++ b/WORKSPACE @@ -0,0 +1,12 @@ +workspace(name = "platforms") + +load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") + +http_archive( + name = "rules_license", + urls = [ + "https://mirror.bazel.build/github.com/bazelbuild/rules_license/releases/download/0.0.7/rules_license-0.0.7.tar.gz", + "https://github.com/bazelbuild/rules_license/releases/download/0.0.7/rules_license-0.0.7.tar.gz", + ], + sha256 = "4531deccb913639c30e5c7512a054d5d875698daeb75d8cf90f284375fe7c360", +) diff --git a/WORKSPACE.bzlmod b/WORKSPACE.bzlmod new file mode 100644 index 0000000..59c0af4 --- /dev/null +++ b/WORKSPACE.bzlmod @@ -0,0 +1,4 @@ +# Include dependencies which are only needed for development here. +# +# Even if this is empty, you need it with bzlmod enable to prevent +# bzlmod from bringing in WORKSPACE too. diff --git a/cpu/BUILD b/cpu/BUILD new file mode 100644 index 0000000..6497452 --- /dev/null +++ b/cpu/BUILD @@ -0,0 +1,190 @@ +# Standard cpu name constraint_setting and constraint_values +licenses(["notice"]) + +package( + default_visibility = ["//visibility:public"], +) + +filegroup( + name = "srcs", + srcs = glob(["**"]), +) + +# To add a new constraint_value see https://github.com/bazelbuild/platforms. +constraint_setting(name = "cpu") + +# New cpu values should refer to specific, highly available CPU implementations, +# not broad architectures. It should be possible to select the right compiler +# options by just by knowing the cpu. This can be a difficult evaluation for +# ARM variations, where there are many possibilities for customization within +# an architecture. +# +# 1. No private names are be allowed. If you build your own custom ARM chips, +# then define them locally within your organization. +# 2. All CPU values must be clear that they are for a 32 or a 64 bit +# implementation. For example, cortex-r52 is a 32 bit processor, and +# cortex-r82 is a 64 bit processor, but both are armv8-r architecture. +# We use the specific processor names because armv8-r is insufficient to +# select proper compiler options. +# +# Many of the name here are legacy values and probably violate these conditions. +# We'll try to clean those up over time. + +# Special case: Architecture-independent outputs only +# +# Some builds are expected to only produce architecture-independent data files, +# such as configuration files, database seed data, composited images, or even +# some kinds of interpreted scripts (Shell, Python, Perl, etc). +# +# When such a build is being performed, this constraint value may be used to +# ensure that architecture-dependent builds cannot be performed (except by way +# of another transition). +# +# As a final example, consider building a package of NIC firmware images for +# many different NIC models. The package overall is architecture-independent, +# and should be built with `//cpu:all`, then each individual image rule has a +# transition to the suitable architecture for that specific NIC model. +constraint_value( + name = "all", + constraint_setting = ":cpu", +) + +constraint_value( + name = "aarch32", + constraint_setting = ":cpu", +) + +constraint_value( + name = "aarch64", + constraint_setting = ":cpu", +) + +alias( + name = "arm", + actual = ":aarch32", +) + +# Cortex-M0, Cortex-M0+, Cortex-M1 +constraint_value( + name = "armv6-m", # Commonly known as thumbv6 + constraint_setting = ":cpu", +) + +# Cortex-M3 +constraint_value( + name = "armv7-m", + constraint_setting = ":cpu", +) + +# Cortex-M4, Cortex-M7 +constraint_value( + name = "armv7e-m", + constraint_setting = ":cpu", +) + +# Cortex-M4, Cortex-M7 with fpu +constraint_value( + name = "armv7e-mf", # armv7e-m with fpu + constraint_setting = ":cpu", +) + +# Cortex-M23, Cortex-M33, Cortex-M35P +constraint_value( + name = "armv8-m", + constraint_setting = ":cpu", +) + +alias( + name = "arm64", + actual = ":aarch64", +) + +constraint_value( + name = "arm64_32", + constraint_setting = ":cpu", +) + +constraint_value( + name = "arm64e", + constraint_setting = ":cpu", +) + +constraint_value( + name = "armv7", + constraint_setting = ":cpu", +) + +constraint_value( + name = "armv7k", + constraint_setting = ":cpu", +) + +constraint_value( + name = "cortex-r52", + constraint_setting = ":cpu", +) + +constraint_value( + name = "cortex-r82", + constraint_setting = ":cpu", +) + +constraint_value( + name = "i386", + constraint_setting = ":cpu", +) + +constraint_value( + name = "ppc", + constraint_setting = ":cpu", +) + +constraint_value( + name = "ppc32", + constraint_setting = ":cpu", +) + +constraint_value( + name = "ppc64le", + constraint_setting = ":cpu", +) + +constraint_value( + name = "s390x", + constraint_setting = ":cpu", +) + +constraint_value( + name = "x86_32", + constraint_setting = ":cpu", +) + +constraint_value( + name = "x86_64", + constraint_setting = ":cpu", +) + +constraint_value( + name = "wasm32", + constraint_setting = ":cpu", +) + +constraint_value( + name = "wasm64", + constraint_setting = ":cpu", +) + +constraint_value( + name = "mips64", + constraint_setting = ":cpu", +) + +constraint_value( + name = "riscv32", + constraint_setting = ":cpu", +) + +constraint_value( + name = "riscv64", + constraint_setting = ":cpu", +) diff --git a/distro/README.md b/distro/README.md new file mode 100644 index 0000000..77fffd6 --- /dev/null +++ b/distro/README.md @@ -0,0 +1,47 @@ +# Updating bazelbuild/platforms + +WARNING: These are what worked last time. Reality might be different. + +## Step 1: Make the release + +- Pick a new version number +- Update version.bzl +- Run distro/makerel.sh +- Go to the [Releases](https://github.com/bazelbuild/platforms/releases) page +- Draft a new release + - Name the release with a version number + - Use the version number as the title + - Copy the description that makerel.sh produced to the description field. + - upload the generated tar file + +- use https://github.com/bazelbuild/continuous-integration/blob/HEAD/mirror/mirror.sh to mirror the file + +## Step 2: Update Bazel + +- Edit `distdir_deps.bzl` +- Merge the PR + +Sample diff: + +``` +diff --git a/distdir_deps.bzl b/distdir_deps.bzl +index ed49a563bc..1739a25c2a 100644 +--- a/distdir_deps.bzl ++++ b/distdir_deps.bzl +@@ -20,11 +20,11 @@ DIST_DEPS = { + # + ######################################## + "platforms": { +- "archive": "platforms-0.0.2.tar.gz", +- "sha256": "48a2d8d343863989c232843e01afc8a986eb8738766bfd8611420a7db8f6f0c3", ++ "archive": "platforms-0.0.3.tar.gz", ++ "sha256": "460caee0fa583b908c622913334ec3c1b842572b9c23cf0d3da0c2543a1a157d", + "urls": [ +- "https://mirror.bazel.build/github.com/bazelbuild/platforms/releases/download/0.0.2/platforms-0.0.2.tar.gz", +- "https://github.com/bazelbuild/platforms/releases/download/0.0.2/platforms-0.0.2.tar.gz", ++ "https://mirror.bazel.build/github.com/bazelbuild/platforms/releases/download/0.0.3/platforms-0.0.3.tar.gz", ++ "https://github.com/bazelbuild/platforms/releases/download/0.0.3/platforms-0.0.3.tar.gz", + ], + "used_in": [ + "additional_distfiles", +``` diff --git a/distro/makerel.sh b/distro/makerel.sh new file mode 100755 index 0000000..20c2f0b --- /dev/null +++ b/distro/makerel.sh @@ -0,0 +1,67 @@ +#!/bin/bash + +if [[ ! -f WORKSPACE ]] ; then + echo 'You must run this command from the top of the workspace.' + exit 1 +fi + +if [[ ! -f version.bzl ]] ; then + version.bzl is missing. + exit 1 +fi +version=$(sed -n -e 's/^version *= *"\(.*\)".*$/\1/p' version.bzl) + +# tar on macos builds a file with different checksums each time. +if [[ $(uname) != 'Linux' ]] ; then + echo 'You must run this command from a linux machine.' + exit 1 +fi + + +dist_file="/tmp/platforms-${version}.tar.gz" +tar czf "$dist_file" BUILD LICENSE MODULE.bazel WORKSPACE WORKSPACE.bzlmod version.bzl cpu os +sha256=$(shasum -a256 "$dist_file" | cut -d' ' -f1) + +path="github.com/bazelbuild/platforms/releases/download/$version/platforms-$version.tar.gz" +cat <<INP + + +1. Create a new release using the tag $version +2. Copy/paste the text below into the release description field. +3. Upload $dist_file as an artifact. +4. Copy $dist_file to the mirror site. +5. Create the release. +6. Update Bazel distdir_deps.bzl to point to this new release. See the readme. + +=============== CUT HERE =============== +**WORKSPACE setup** + +\`\`\` +load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") +http_archive( + name = "platforms", + urls = [ + "https://mirror.bazel.build/${path}", + "https://${path}", + ], + sha256 = "$sha256", +) +\`\`\` +=============== CUT HERE =============== + +Use this to update Bazel's distdir_deps.bzl + + + "archive": "platforms-$version.tar.gz", + "sha256": "$sha256", + "urls": [ + "https://mirror.bazel.build/${path}", + "https://${path}", + ], + +Copy/paste this to mirror the file. + + gsutil cp /tmp/platforms-$version.tar.gz "gs://bazel-mirror/${path}" + gsutil setmeta -h "Cache-Control: public, max-age=31536000" "gs://bazel-mirror/${path}" + +INP diff --git a/os/BUILD b/os/BUILD new file mode 100644 index 0000000..ae6e8b0 --- /dev/null +++ b/os/BUILD @@ -0,0 +1,124 @@ +# Standard constraint_setting and constraint_values to be used in platforms. +licenses(["notice"]) + +package( + default_visibility = ["//visibility:public"], +) + +filegroup( + name = "srcs", + srcs = glob(["**"]), +) + +# To add a new constraint_value see https://github.com/bazelbuild/platforms. +constraint_setting(name = "os") + +constraint_value( + name = "freebsd", + constraint_setting = ":os", +) + +constraint_value( + name = "netbsd", + constraint_setting = ":os", +) + +constraint_value( + name = "openbsd", + constraint_setting = ":os", +) + +constraint_value( + name = "haiku", + constraint_setting = ":os", +) + +constraint_value( + name = "android", + constraint_setting = ":os", +) + +constraint_value( + name = "linux", + constraint_setting = ":os", +) + +constraint_value( + name = "windows", + constraint_setting = ":os", +) + +# For the VXworks OS, usefull for embedded systems +constraint_value( + name = "vxworks", + constraint_setting = ":os", +) + +# For platforms with no OS, like microcontrollers. +constraint_value( + name = "none", + constraint_setting = ":os", +) + +### Apple OS Values + +constraint_value( + name = "ios", + constraint_setting = ":os", +) + +# TODO(b/138656886): Rename this to macos instead of osx. +constraint_value( + name = "osx", + constraint_setting = ":os", +) + +alias( + name = "macos", + actual = ":osx", +) + +constraint_value( + name = "tvos", + constraint_setting = ":os", +) + +constraint_value( + name = "watchos", + constraint_setting = ":os", +) + +constraint_value( + name = "visionos", + constraint_setting = ":os", +) + +constraint_value( + name = "qnx", + constraint_setting = ":os", +) + +# NixOS uses the Linux kernel, but is not ABI-compatible with any +# other Linux distribution. This is because the dynamic linker is in +# a non-standard (and undefined) location on the filesystem. +constraint_value( + name = "nixos", + constraint_setting = ":os", +) + +# WASI (WebAssembly System Interface) +# https://github.com/bytecodealliance/wasmtime/blob/main/docs/WASI-overview.md +constraint_value( + name = "wasi", + constraint_setting = ":os", +) + +constraint_value( + name = "fuchsia", + constraint_setting = ":os", +) + +constraint_value( + name = "chromiumos", + constraint_setting = ":os", +) diff --git a/tests/BUILD b/tests/BUILD new file mode 100644 index 0000000..e0c7526 --- /dev/null +++ b/tests/BUILD @@ -0,0 +1,21 @@ +load("//:version.bzl", "version") + +package(default_visibility = ["//visibility:private"]) + +# This is a quick hack to make sure that version.bzl agrees with MODULE.bazel +# It only works from Linux, but that is sufficient, becuase we do a presubmit +# run linux, so we will still catch a mismatch. +genrule( + name = "versions_match", + outs = ["found_it"], + cmd = ";\n".join([ + """echo version: %s""" % version, + """grep 'version = "%s",' $(location //:MODULE.bazel) >$(location :found_it)""" % version, + ]), + target_compatible_with = [ + "//os:linux", + ], + tools = [ + "//:MODULE.bazel", + ], +) diff --git a/version.bzl b/version.bzl new file mode 100644 index 0000000..2068e00 --- /dev/null +++ b/version.bzl @@ -0,0 +1,16 @@ +# Copyright 2022 The Bazel Authors. All rights reserved. +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +"""The version of bazelbuild/platforms.""" + +version = "0.0.8" |