commit | d1314df52982ec94ad66f50ac9314f987898043d | [log] [tgz] |
---|---|---|
author | Adam Barth <abarth@google.com> | Tue Jul 03 19:38:00 2018 -0700 |
committer | Wez . <wez@google.com> | Fri Jul 13 23:09:40 2018 +0000 |
tree | e6f0c0401873e6223bffc97e2f46fe73202430d4 | |
parent | 0ac769bd33c76c4ec65e89bf605e044787d6a6e3 [diff] |
Reland "[sdk] Remove private headers from SDK" This is a reland of 37d8ac4810530285a8063e093f2ad37940e31a40 Original change's description: > [sdk] Remove private headers from SDK > > Consumers of the SDK should not be using these headers. We're going to > replace these ioctls with FIDL. > > Test: None. > Change-Id: I43681db00ec40f70efea8cbc50f3bae3e25f84a1 Test: Chromium successfully builds against resulting SDK (see https://fuchsia-sdk-chromium-roll.skia.org/). Change-Id: Ib20f928a36bb30e109e781191e4e1621f83f723f
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.