Instead, have fixed code there that generates its targets based on
JSON emitted by the Zircon `gn gen`.

This eliminates the last vestiges of the old `export/*.pkg` system.

Bug: BLD-437 #done
Change-Id: I9717faf0fdd679c8ed0ca96c6c304920285b4c0c

Nothing uses the Zircon board lists via GN or .../zircon-boards.list
any more.

Bug: BLD-437 #comment Removed //zircon/public/config
Change-Id: Ic9f59756aa95cb43699f1ba926f674620eb34ff1

Follow the existing behavior of omitting the files from the image
when scripts/download-prebuilt sets internal_access=false.

Bug: BLD-325
Test: manual build with no CIPD auth
Change-Id: Ib776a97b8873f26074998ebc2705c57bf190f991

Change-Id: Ibe3194252284761fc7b496c4115463f5f486e66f

Change-Id: I50a54ccd8334b9934a77a98247922074367e3ed7

Change-Id: Ibab3dc4cd924e71c10f31c1f06d2986bcad3b9a6

Change-Id: I817c872084007e3bcd7752738d23a2281c2fd528

Test: None.
Change-Id: I185ef9e023173ee824027017a951ed6c1c5b9f91

Test: ./scripts/clang-fmt <some file> and ./scripts/clang-fmt --version
Change-Id: Ic8c8a830e3914dc0eba9b05abf4d9a8d5dac2e12

Test: N/A
Change-Id: Ife6524fc6306d129d97e76965feca77625794f4a

Fetch Linux sysroot that we use for all Linux targets.

TC-312

Change-Id: I5af3fa3e36f1703ee4f3f532f846487603ae1aa5

Tested: Manually verified.
Change-Id: I1c523c505372fe61ecbfe76b7f36ed536fa2ab36

Change-Id: I5ee9c6779337d2fa88ba13e59e752cedfdc53f78

(And a flaky test)

Test: Added a (deterministically) broken test and fixed it.

Change-Id: Ic16eb0baeb611cc6180e2ca3cc18611eceedfebb

This is the file generated by "fx compdb" and used by language servers.

Test: N/A
Change-Id: Ib083ad5cf25ca594332a605163f17afc6e8eb6d2

When updating the CIPD client to be identified by SHA256 hash, old clients (that
have no idea about SHA256) fail during 'selfupdate'.

We'll roll our SHA256 support in two stages:
  1. Deploy new client that understand SHA256 using its SHA1 name, so
     self-update from old clients works.
  2. Deploy same (or newer) client using its SHA256 name. This would work since
     the client doing the self-update already understands SHA256 at this point.

But we can't guarantee that ALL buildtools deployments will update through
stages (1) and (2) sequentially. Some of them may skip (1) and end-up directly
in (2), failing on 'selfupdate'.

This CL makes sure they can recover from this state by rebootstraping the client
from scratch (this works with SHA256 hashes).

Similar CL in Chromium's depot_tools:
https://chromium-review.googlesource.com/1149454

Change-Id: I6bb6cb9980ad536008260af74ddec90ded51dd22

More-local .gitignore of firmware/ subdirectory to match pattern used
for other firmware/ directories.

Tested: Checked git status, and firmware/ still ignored.
Change-Id: I149c56edf68580aa9861da3b15a0d8ee5f7dde10

The time stamp of the last `jiri update` is visible in the
`//.jiri_root/update/update_history/` directory.  So rather than
touching the source tree in a hook that runs at the end of `jiri
update`, just generate the timestamp file in the GN build as a
function of the files `jiri update` writes.

Bug: BLD-200 #comment Stop writing //garnet/last-update file in jiri hook
Test: CQ
Change-Id: I41c1448b0fed8d0cb3985ee032d1b7d4c6209a36

This ignores the amlogic-video firmware directory so that git status
won't be noisy.  This change assumes that we'll keep cipd content in a
firmware/ directory to itself (ignores the dir, not the two files
separately).

Tested: ran "git status" after adding the line to .gitignore
Change-Id: Id970838cc2e1c2233b8dccd5c8fe5597dc893c3a

This program will do more than turn the screen Fuchsia once the requirements
for recovery UI are more clear.

Change-Id: I56fcf9a2e841545d4b72dc80b38521067361addb

When the user doesn't have premissions to download the internal CIPD
packages, just skip those rather than failing.

Change-Id: I448e1ea8e04d59198f452168581f12e02a3234f8

This allows us to have a unified source for vendored crates as well
as a unified target directory for all fargo build.

This CL also adds Cargo.toml files to the .gitignore since we no
longer check them in as part of the build system.

Change-Id: I1d19404f6b1760c2a5931fd9984e6093e195816a

It will soon host generated GN rules for FIDL libraries.

BLD-16

Change-Id: I32887ae0a2bdca9580cb9d2b5f4628fb525fdb06

This is now used to hold third party vendored go repo repositories.

Change-Id: I03739d31228f321bb030d932abc5d7011f93f194

Change-Id: Ia7036de3c94a44fa9ef505094666fafc3b308eb2

Sublime text users might have these in the repo.

Change-Id: I5afde56c5df49c5c3c7c025db53c942fbf42ce86

IDEA CE works pretty well with Rust

Change-Id: I86dfaa37036ffa5a2a4eee3a4fc568ed99a421fb

Change-Id: I3aa6fb443a77562f59aa055898bb40ec2c9e34e8

Set up a garnet-wide cipd.ensure and script in tools/.
Use it for for wlan and bluetooth firmware.
Delete the download-firmware.sh scripts.
Set up a jiri hook to run cipd.

The vulkan sdk and fonts scripts are a little more involved, and can be
ported to cipd at a later time.

Change-Id: I1a853c9ff07ecbae33f18db6353cb107962d73ed

Change-Id: I04a68ad9c265af7b2519e4b5b33d31d8d9140df8

Change-Id: I8da227d3e18eeadd417a4bd99d176e36cd871923

Sublime text users might have these in the repo.

Change-Id: I86e6993a2baeed856a0ff419925f7c0f5a86d28e

TO-733

Change-Id: I5b61eb3fd01335441c376c191ab90c4a176a1963

TO-562

Change-Id: I159ee8ae73d05bbf42c3e64238b16ab82e2e634f

Change lists in this topic change the build strategy from rewriting
Cargo.toml files to using a workspace and patch sections. The result is
the same but it is easier to maintain.

Change-Id: I79c12e8a9491e3a4c0fdbf95d01b43941a8d66bb