commit | 3a06f4adf19fbba4b8990c6fc51191c9c99f0787 | [log] [tgz] |
---|---|---|
author | Leo Lung <leolung@google.com> | Tue Nov 06 13:50:34 2018 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Nov 06 22:36:05 2018 +0000 |
tree | 74dad93c25136bd1866dc4146ab2059c92e469d1 | |
parent | efd046914e770e8d8275082f87d4e9d1860e1827 [diff] |
[sdk][bazel] Fix broken flutter_app flutter_app build rule is broken when using fuchsia_package_name. Add a test for that too. Also demonstrates >1 flutter component per package. TESTED= name 'component_name' is not defined error when building with test added. went away when fix applied CF-170 #comment CF-129 #comment CF-80 #comment Change-Id: I6595f4d38ca40ef78e2f30de94901801262701de
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.