commit | e7a2298b469d3dee7f10fe9edc1ee272c6ed3dee | [log] [tgz] |
---|---|---|
author | Jake Ehrlich <jakehehrlich@google.com> | Wed Dec 05 18:51:11 2018 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Dec 15 02:41:29 2018 +0000 |
tree | fbad541de308f55b48022874c09aca61a69db6c9 | |
parent | 467829d94d0a73c1177727a0ef7b848828307eed [diff] |
[scripts] Add script to convert between ids.txt and .build-id Test: 1) Convert //zircon rel to absolute 2) Convert absolute to //zircon rel 3) Convert implicit ids.txt rel to absolute 4) Convert explicit ids.txt rel to //zircon rel 5) Convert absolute ids.txt to .build-id 6) Convert //zircon rel ids.txt to .build-id 7) Convert ids.txt rel to .build-id 8) Convert .build-id to //zircon rel ids.txt 9) Convert .build-id to absolute ids.txt Bug: TC-303 #comment Script to help with testing and conversion. Change-Id: I9a22b547db786f2f43ad5371db61bf0c0058ce35
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.