commit | 2a70d8c5b49d571a1179fa8ef77d056417e5be4d | [log] [tgz] |
---|---|---|
author | James Tucker <raggi@google.com> | Mon Jan 28 12:21:27 2019 -0800 |
committer | James Tucker <raggi@google.com> | Mon Jan 28 12:24:06 2019 -0800 |
tree | a4d56173421ee4e9c4767a4ad8975326d5a1cac9 | |
parent | 7bbe17198c0dd4924b3035be0c991b48effd1980 [diff] |
[fx set] run in $FUCHSIA_DIR, new invariant There have been several bugs stemming from the fact that set was not changing it's directory. It produces GN arguments, many of which want to be relative to $FUCHSIA_DIR, rather than absolute. The build has similar invariants, with // being $FUCHSIA_DIR, and the build directory being the working directory during build execution. Test: fx set from sub-directory of root picks up a board file. Bug: BLD-352 #done Change-Id: If6a0e351ce4c5f52e1a6011387ce2fca27156934
This repository is for scripts useful when hacking on Fuchsia. This repository should contain scripts that perform tasks spanning multiple repositories. Scripts that only operate within a single repository should live in the relevant repository.
The push-package.py script pushes the files listed in the given manifests files. No checking is performed for incremental changes.
The sample command lines below can be used to build Modular and then push those files to the default device. This assumes you have already booted your device with a version of Fuchsia that contains the most recent version of all other packages. This command line uses the “system_manifest” file from each of the modular directories, such as modular, modular_dev, and modular_tests.
cd $FUCHSIA_DIR fx build peridot:modular_all scripts/push-package.py out/debug-x64/package/modular*/system_manifest
fx publish
will take a package from the build and create a Fuchsia package manager package from a build package. It will then add the package to a local update respository which, by default, is put at ${FUCHSIA_BUILD_DIR}/amber-files
. It will also add the package content files to the update repository and name these file after their Merkle Root. If a package name is supplied to fx publish
, only that package will be processed. If no name is supplied, all the packages made by the build will be included.