[roll] Roll fuchsia [bazel_sdk] Add @fuchsia_sdk//fuchsia/workspace/sdk_export:idk_to_bazel_sdk Add a new py_binary() target that can be used to convert an IDK export directory directly into a Fuchsia Bazel SDK. This will be used in the future at build time to generate the final SDK directories to be uploaded to cloud storage, and verified with the Bazel SDK test suite. This works by creating a symlink file (generate_sdk_build_rules.py) that points to .../workspace/sdk_templates/generate_sdk_build_rules.bzl, which is written in a way to allow execution both in Bazel (when invoked from a repository rule) or in Python (when invoked from the script). `idk_to_bazel_sdk.py` contains special classes that implement the special `runtime` value described in the technical note at the start of `generate_sdk_build_rules.bzl`, and translates its function calls to proper Python operations when needed. See the new .../sdk_export/BUILD.bazel file for a comment that explains how to use this new target with `fx bazel run ...`. A future CL will add some targets to the platform build to generate the final SDK at build time. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1062855 Original-Revision: e895547e88613d9aa19b917cebfcb16deba56abc GitOrigin-RevId: 4d980638323d53e99c068e191a80078b808db092 Change-Id: Id07acc849136b68911bc118775e054125ce04200
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.