| commit | 6f94a4caf72f64449c82b778324b94b8020d43c8 | [log] [tgz] |
|---|---|---|
| author | Rob Tsuk <robtsuk@google.com> | Fri Oct 13 09:18:22 2017 -0700 |
| committer | Rob Tsuk <robtsuk@google.com> | Fri Oct 13 09:18:57 2017 -0700 |
| tree | b10588e0d3693b0d9a4d041619c6f19371afa761 | |
| parent | b15bc75c26e69bbe41af97f1e2e0736807b9b47d [diff] |
Remove Rust spinning square example It needs to be updated for both the new FIDL bindings and Mozart 2 so it is not a good example right now. I will bring it back when it makes sense to have a Rust example of a Mozart client module in Topaz. Change-Id: I7a4cd201895b92dae57173392cb4afbdc97e7fa2
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 all of the files in a particular package. No checking is performed for incremental changes.
The sample command lines below can be used to build the “modular” package and then push it 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.
fbuild apps/modular scripts/push-package.py -o $FUCHSIA_BUILD_DIR packages/gn/modular
fpublish from env.sh 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 fpublish, only that package will be processed. If no name is supplied, all the packages made by the build will be included.