diff options
author | Dan Albert <danalbert@google.com> | 2015-07-10 14:58:29 -0700 |
---|---|---|
committer | Dan Albert <danalbert@google.com> | 2015-07-10 16:16:52 -0700 |
commit | b82a69d778acbdabe9bb75310e23167fd2ebb476 (patch) | |
tree | da2f9d0d833fc6584cbd09597c04ea928c6dc847 /README.md | |
parent | e62491b29add9a410aeda5bdefa8b7d03b055cd6 (diff) | |
download | ndk-b82a69d778acbdabe9bb75310e23167fd2ebb476.tar.gz |
Add packaging support to checkbuild.py.
The --package flag will cause the NDK to be packaged once the build is
complete. Note that this flag is on by default until the build server
configuration is updated; use --no-package to skip this step for local
builds.
Bug: http://b/22404289
Change-Id: Idea82eb8c1bc005dafb3acbfe9fe827772bb817e
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 14 |
1 files changed, 7 insertions, 7 deletions
@@ -104,7 +104,7 @@ Host/Target prebuilts ### For Linux or Darwin: ```bash -$ python checkbuild.py +$ python checkbuild.py --no-package ``` ### For Windows, from Linux: @@ -116,13 +116,13 @@ $ python checkbuild.py --system windows Packaging --------- -Once all prebuilt tarballs are at `$PREBUILT_PATH`, run the following to package -the NDK: +The simplest way to package an NDK on Linux is to just omit the `--no-package` +flag when running `checkbuild.py`. This will take a little longer though, so it +may not be desired for day to day development. -```bash -$ build/tools/package-release.sh --prebuilt-dir=/s/prebuilt --separate-64 \ - --release=r9x -``` +To package the NDK for Windows or Darwin (or if more control over the packaging +process is needed), invoke `build/tools/package-release.sh` directly. This +process will be improved in a future commit. Best Practices for Incremental Builds ------------------------------------- |