Merge tag '0.0.1' into tmp_auto_upgrade am: 86fe3085e4

Original change: https://android-review.googlesource.com/c/platform/external/bazelbuild-platforms/+/2913502

Change-Id: If33c3523f926332eb8e17834a93e8e536efea627
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>

10 files changed, 533 insertions, 0 deletions

diff --git a/.bazelci/presubmit.yml b/.bazelci/presubmit.yml
new file mode 100644
index 0000000..d529df1
--- /dev/null
+++ b/.bazelci/presubmit.yml
@@ -0,0 +1,19 @@
+---
+tasks:
+  ubuntu1604:
+    build_targets:
+    - "..."
+  ubuntu1804:
+    build_targets:
+    - "..."
+  ubuntu1804_nojava:
+    build_flags:
+    - "--javabase=@openjdk11_linux_archive//:runtime"
+    build_targets:
+    - "..."
+  macos:
+    build_targets:
+    - "..."
+  windows:
+    build_targets:
+    - "..."
diff --git a/AUTHORS b/AUTHORS
new file mode 100644
index 0000000..0a41ced
--- /dev/null
+++ b/AUTHORS
@@ -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>
diff --git a/BUILD b/BUILD
new file mode 100644
index 0000000..d73ff92
--- /dev/null
+++ b/BUILD
@@ -0,0 +1,15 @@
+package(default_visibility = ["//visibility:public"])
+
+licenses(["notice"])
+
+exports_files(["LICENSE"])
+
+filegroup(
+    name = "srcs",
+    srcs = [
+        "BUILD",
+        "WORKSPACE",
+        "//cpu:srcs",
+        "//os:srcs",
+    ],
+)
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).
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..261eeb9
--- /dev/null
+++ b/LICENSE
@@ -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/README.md b/README.md
new file mode 100644
index 0000000..a2c00d3
--- /dev/null
+++ b/README.md
@@ -0,0 +1,85 @@
+# [Bazel Platforms](https://bazel.build)
+
+This repository houses all canonical
+[constraint_setting()](https://docs.bazel.build/versions/master/be/platform.html#constraint_setting)s,
+[constraint_value()](https://docs.bazel.build/versions/master/be/platform.html#constraint_value)s
+and
+[platform()](https://docs.bazel.build/versions/master/be/platform.html#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, contact
+[bazel-dev@googlegroups.com](mailto://bazel-dev@googlegroups.com) to discuss
+options.
diff --git a/WORKSPACE b/WORKSPACE
new file mode 100644
index 0000000..f1874ea
--- /dev/null
+++ b/WORKSPACE
@@ -0,0 +1 @@
+workspace(name = "platforms")
diff --git a/cpu/BUILD b/cpu/BUILD
new file mode 100644
index 0000000..e06de69
--- /dev/null
+++ b/cpu/BUILD
@@ -0,0 +1,86 @@
+# 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")
+
+# TODO(b/136237408): Remove this generic CPU name and replace with a specific one.
+constraint_value(
+    name = "aarch64",
+    constraint_setting = ":cpu",
+)
+
+# TODO(b/136237408): Remove this generic CPU name and replace with a specific one.
+constraint_value(
+    name = "arm",
+    constraint_setting = ":cpu",
+)
+
+constraint_value(
+    name = "arm64_32",
+    constraint_setting = ":cpu",
+)
+
+constraint_value(
+    name = "arm64",
+    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 = "i386",
+    constraint_setting = ":cpu",
+)
+
+constraint_value(
+    name = "ppc",
+    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",
+)
diff --git a/os/BUILD b/os/BUILD
new file mode 100644
index 0000000..16525d3
--- /dev/null
+++ b/os/BUILD
@@ -0,0 +1,86 @@
+# 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 = "openbsd",
+    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 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 = "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",
+)