Lines Matching refs:package

63 ### 1. From a previous NDK release package:
105 --mingw option, which requires that you have the "mingw32" package
116 ### 3. Download, rebuild, package, install in separate steps:
122     package the result in a simple tarball.
134 Use the following command to download, patch and package the
137         $NDK/build/tools/download-toolchain-sources.sh --package
146 Note that if you don't use the --package option, you will need to
156 tarball that was created in the previous section with the --package
161 Where <file> points to the package generated by the
184 package on your system, then use the --mingw option, as in:
207 an archive. To do that, use the --package option, as in:
209         $NDK/build/tools/rebuild-all-prebuilt.sh --package
211 This will generate a package file containing all the prebuilts, that
212 can be unpacked directly into your $NDK directory. The package name is
222 The generated package can easily be shared with other people.
225 IV. Generate new package releases:
247 ### 2. Using a previous NDK release package:
249 This is the second simplest way to generate a new package, and it will
251 from the previous package.
256         build/tools/package-release.sh --prebuilt-ndk=<file>
258 Where <file> points to a previous NDK package (i.e. archive file).
260 NOTE: This method can only be used to generate a single release package
274         build/tools/package-release.sh --prebuilt-dir=<path>
276 The generated NDK package release will have a name that looks like:
284 The script 'package-release.sh' provides a few additional options:
288         --systems=<list>       Change the list of host systems to package for
290         --platforms=<list>     List of API levels to package in the NDK