This is a quick fix. We need to work on the bug and come up with a
better gn fix.

BLD-354 #comment

TEST=build on my local and CQ

Change-Id: I59ec2b4c0deb312f74dafa1a0f1d332abe4f82fd

Test: verified that a local instance was correctly included in SDK archives.
Bug: DX-209
Change-Id: I97ae4ec3a93f7d93ce0a401945e525cf8a1b8268

host_tests.json may be used to find test specs printed to the root out
dir of //build/toolchain:host_${host_cpu}. Have write_runtime_deps write
to the same root out dir, so that these files may be discovered
alongside each other.

Change-Id: Ib460cd5a4aaf2018e0de61dd7b071fa7b2f21a21

My opinion:
-Better to proliferate these variables throughout the tree than
complicated, space-hungry scopes (which developers will invariably groan
about having to type out). Moreover, these are more easily grep-able.
-If we introduce a second nuc, then we can always rename nuc_env to
dawson_canyon_env; same for vim2 or any other environment.

Bug: IN-497

Change-Id: I54acaa2cee62318be6b7b2bd9ae1a4d33d97d834

We've been assuming make is in the user's path for generated Zircon
build rules. This assumption is false for Chromium bots, which are not
provisioned with build-essential and thus this is blocking Tricium
rollout, since that runs on Chromium bots.

Change-Id: I16cc31a282c4973c52012a1200976af3fe1d904a

TESTED=built all

Change-Id: If22320474beb012ecd5150bd58f0ee832f4b5f28

When the netboot.sh script was introduced as a build contract, the optional
building of netboot images regressed. It now returns.

Change-Id: I52208a0de7c8aba199420eeb63a7ceb26c55709a

copytree was only used to produce the blob output directory. The blob output
directory is content addressed, as such repeating writes to target locations
is not useful work. The code for copytree is used to produce a copy-only-once
behavior that significantly reduces total number and cost of io operations
for incremental builds.

Change-Id: Idc4b14b88326f93cfe2ff5c43e01a6628f7b2bec

Enforces manifest has a .cmx or .cml: Component
//garnet/examples/components/v2:hello_world_component(//build/toolchain/fuchsia:x64)'s
manifest /[redacted]/garnet/examples/components/v2/meta/hello_world.cmhi
should have extension .cmx or .cml

Enforces matching manifest-manifest_dest of cmx-cmx, cml-cm:
Component
//garnet/examples/components/v2:hello_world_component(//build/toolchain/fuchsia:x64)'s
manifest_dest meta/hello_world.cml should have extension .cm

TESTED=built

Change-Id: Ie23841eeebe039412ac047290b8368ae2ffe820c

The `license` section in the cargo manifest references a SPDX
license expression, which does not fully support our BSD-3-Clause
with the Patent grant. So instead, use a license file until
that support is added.

Change-Id: Icbd5a91a464b82be99fdf285f99329c7d8f38697

This passes the --sizes flag to the blobfs tool, which asks it record
information about the size used by each blob to a file. This data can
be picked up by 'fx blobstats' and similar tools for image size
analysis.

Test: CQ
ZX-3303 #comment build rules for --sizes flag

Change-Id: I7b2119594a25f5ad8205c33d3b49bb82983bbf4f

Needed so that callers of dart_fuchsia_test can specify environments.
See bug for context.

Bug: IN-927 #comment
Test: CQ
Change-Id: Ia54f22073c923b124eeccb8463e5710ce3dead87

Invoking go vet appears to contribute a very significant portion of Go binary
build time, including a significant portion of overall build time, as it
repeats significant volumes of work vetting shared dependencies and so on.

Users can instead invoke `fx go --package <package-name> vet`, or specify
`go_vet_enabled=true` in their build arguments to get the information for
their own purposes.

Change-Id: I49dfa062b7bcf3738ea842a96bc497db8de46c95

Change-Id: Iafd2bd62068f616f0639c532157afadb5328db24

Change-Id: I7dac9443f5c9e2d721f22aca6bdf94a1f2ce50ce

This adds a build step that generates a file containing a maximum
allowable FVM size limit. The limit can be configured from product
configurations and/or specified as a GN argument.

Test: build with this configuration
INTK-773 #comment add build infrastructure

Change-Id: I9c52975d7660df154924c813ba7587b96aa2f27d

CF-278 #done

TESTED=
Edited garnet/examples/components/v2/meta/hello_world.cml
fx build
Observed ninja did things

Change-Id: I3a48ed714d116381a6e1d7e52ba5e177a5fc895e

Some host targets like Escher depend on libgl and libx11, rollback
to the older sysroot which still contains those until we produce
new sysroot which also contains those libraries.

TC-301 #done

Change-Id: I4a65d350936949798133eeb34a59e7056bc818dc

Remove cmx tool from //build, as it was recently migrated to
//garnet/bin/cmc.

TEST: fx set && fx build succeeds
Change-Id: I883d728ebfd2dc32ebd900cf0cf8d11383f899fc

TESTED=built all, and built
https://fuchsia-review.googlesource.com/c/garnet/+/243993

CF-278

Change-Id: I4c9efc383d6018cc8323dc31271355a82e3dd9ba

Host-only deps can be in this state.

Testing: built
Change-Id: I1f70815d017f37d9382d1d956bfbe3be14449d8b

GOCACHE allows for caching build artifacts and test results across
builds. As of Go 1.12, GOCACHE is required to be set if a user cache
directory cannot be determined (which is done using $HOME or
$XDG_CACHE_HOME). Neither of these environment variables are set during
our builds (and if they are, it's not necessarily likely that we would
like to use them), so we must set GOCACHE to build Go 1.12.

This change introduces a declared_arg to set the go cache directory,
which defaults to the root build directory joined with ".gocache". If
overridden, this argument must be a full path.

Change-Id: I0e509e498cb60772cbd94456afac6e1fe757e953

This means you can define a test_package("tests") without forcing the
package to be named "tests".

TEST=fx build

Change-Id: I781e7d869261a025e975a44a50600b2cbd1ffe9f

This is technically a kind of security regression, as any infrastructure
should instead be managing it's own key material, but as we're using these
keys everywhere presently, this helps with the nascent infra scripts. This
should be undone along with other actions in IN-915.

Bug: INTK-781 #comment added insecure dev keys to package-archive.tgz, to be undone later.
Bug: IN-915 #comment added insecure dev keys to package-archive.tgz, to be undone later.
Change-Id: I3c75331ef6d96d2f08a38a93b73837ffaf568c61

This enables soft transitions when the artifacts and sources change locations
within //garnet.

Change-Id: I95529f5bc582114633e9185ee5746621bd7a4177

Now that "pm expand" can generate the blobs.json file, use its output
instead of generating our own so this template/script doesn't need to
parse the meta/contents to generate a correct package path for all the
blobs in the package.

Test: build
Change-Id: I32039acfd257f358e90fb105d9ccab7a73c40063

This cuts off the leading //.

Moreover, we fix a bug in test.gni in which the location was being
recorded with the target_name of the spec instead of that of the test
template.

Change-Id: I691134596f27d38a36dc355c8fa0ee5519ac68d2

Change-Id: Id55243bb7f55e42e6a0227dc41ea5d82a45bc0f6

Although we wish to minimize the usage of mexec (ZX-2069), the infrastructure
currently requires it for vim2 lifecycle management. (`fastboot continue`
does not continue back to fuchsia after paving and rebooting in the case we
do not mexec a kernel.)

Test: mexec-ing zircon.zbi works for zircon on a vim2.
Bug: IN-892
Change-Id: Ifb2f62ef858535e1f06a50d118b56c37d8394f9e

Test: ran locally and verified packages.tar.gz contents.
Bug: IN-881

Change-Id: If12dcd6f880c1ada76b4e9cda8e536d74afdf8d4

Test: successfully created a sdk tarball locally and compared contents
at HEAD.
Bug: IN-881

Change-Id: If47f91b2ee633bbdbd62ad55dba2c2a480b3c243

This is needed since ld64 which is the default linker doesn't support
linking ELF binaries.

Change-Id: If8e06cb42c5ea61c24613e0f3f51267ab89d6fd0

Modify rust build rules to support producing SDK atoms, and use the
added functionality to produce an SDK atom for the cmx tool.

Change-Id: I3e8e686e01f7dbc52fc21d3fc34e2bffd6f23554

Just as we did in the "link" tool we now add modules to .build-id in "solink"
and "solink_module" to make sure shared_library and loadable_module binaries
are included in .build-id.

Bug: TC-303
Test: Run a build, find driver_module and shared_library targets in ids.txt,
look for those in .build-id, if present it works.

Change-Id: I165f5de09496d0a715254e744f23fc733ae1ad76

This change adds JSON schemas for CML, the "component manifest
language", and CM, the "binary" component manifest format. CM and CML
are complementary languages to express v2 component manifests. CML is
what humans use to read and write component manifests, while CM is the
format to store a component manifest at rest and is what gets shipped
with a package. CM has a direct one-to-to mapping onto the FIDL
representation.

This change also updates the cmx validator to work with CM and CMl
files. We don't support any post-validation yet, only validation through
the schema.

CF-154 #comment component manifest schemas

TESTED=validate.rs unit tests

Change-Id: Ic22ae05ef0b5c0fbedbbcae8c069b0f6aad458f0

Test: built
Change-Id: I0fd2704ca78f93463e91792e0635597bb5529fcc

This template was moved to //topaz/runtime/dart/dart_test.gni

Change-Id: I50e39167c7d8e6fdf013f7463924dc0ce789065f

This change adds a means to record test metadata for testing instruction when
building for linux or mac, to be collected at test time.

Bug: IN-823
Change-Id: Ib66864f5f43f944473d5cfe59d6555486eba45f5

Bug: IN-824
Change-Id: I1dc4b8c81a06a3b5daacc69d13cd021ad897bea9