Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Open sidebar
halo
ndk
Commits
6ab129be
Commit
6ab129be
authored
9 years ago
by
Dan Albert
Browse files
Options
Download
Email Patches
Plain Diff
Add testing instructions to the README.
Change-Id: I34e566b0095ee4c0f574b03d6dd1eb3f9dd77ee9
parent
797ec6dc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
9 deletions
+14
-9
README.md
README.md
+14
-9
No files found.
README.md
View file @
6ab129be
...
...
@@ -122,12 +122,17 @@ 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
-------------------------------------
*
Do not run
`build/tools/dev-cleanup.sh`
which erases all prebuilts.
*
Remove the individual prebuilt directory if new build deletes files. This is
rare.
*
Package NDK from prebuilt tarballs in
`$PREBUILT_PATH`
. It runs
`build/tools/build-docs.sh`
which produces no tarball in
`$PREBUILT_PATH`
.
*
Unpack and compare against the previous package.
Testing
-------
Running the NDK tests requires a complete NDK package (see previous steps). The
full test suite includes tests which run on a device or emulator, so you'll need
to have adb in your path and
`ANDROID_SERIAL`
set if more than one
device/emulator is connected. With that package:
```
bash
$
tar
xf android-ndk-
$BUILD_NUM
-
$HOST_TAG
.tar.bz2
$
cd
android-ndk-
$BUILD_NUM
$
export
NDK
=
`
pwd
`
$
python tests/run-all.py
--abi
$ABI_TO_TEST
```
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment