commit | 7ecf99da26c9dd3eb76ad887663b7258e3273169 | [log] [tgz] |
---|---|---|
author | Rob Tsuk <robtsuk@google.com> | Wed Oct 10 13:54:48 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Oct 10 23:03:42 2018 +0000 |
tree | 427e4a4e7426566195234e20ec8d8956b63ce490 | |
parent | 7e5fd6535310af80217eea9260dc184cb475c90e [diff] |
[rust] Make update-rustc-third-party work on Mac again Made sure to include the buildtools cmake in the path, since it isn’t always installed on Macs. Also set up CFLAGS and LDFLAGs to point to a homebrew installed openssl for the build script of the openssl crate. Also changed the run of cargo vendor so that it would put build results in the Fuchsia out directory instead of in the source tree. Testing: built on Mac Change-Id: Ic20d9729632d6f778849a8de8cbc0d1672fa5a54
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.