[roll] Roll fuchsia [bazel] Add --config=no_sdk to .bazelrc file.
This CL introduces `--config=no_sdk` which can be used with
Bazel commands to use the workspace *without* IDK and SDK repositories.
This will be used in the future to allow certain bazel_build_action()
targets to run *before* the IDK is generated by Ninja, for example to
generate host binaries directly in Bazel.
This works by using `--override_repository` to point IDK/SDK related
repositories to empty/fake versions of them, that only contain the
minimum required to use the parts of @rules_fuchsia that are needed
to setup the project workspace.
For example, first setup the Bazel workspace (currently this still
rebuilds the IDK with Ninja, but this will change in the future):
```
fx build //:bazel_workspace
```
Then use `fx bazel` to invoke Bazel with the new config, e.g.:
```
fx bazel build --config=no_sdk //build/bazel/examples/hello_world
```
NOTE: This config forces the default platform to match the host
system. This restriction will be lifted in the future.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1165956
Original-Revision: 356531d80d3a67e3575b1cf248e0afddd2e3f98f
GitOrigin-RevId: ca71b8ae1c913fba99202e97b2f793910802151f
Change-Id: I457d825a2190d85b49dd1ac105387baea4f3af46
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 in one of the communication channels documented at get involved.
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.