Lines Matching +full:build +full:- +full:and +full:- +full:test

11 First, make sure you have all the usual tools and libraries needed to build
19 * Create a directory `android-sdk/cmdline-tools`, and unzip the command line
21 * Rename `android-sdk/cmdline-tools/cmdline-tools` to
22   `android-sdk/cmdline-tools/latest`.
23 * `export ANDROID_HOME=/path/to/android-sdk`
37 cross-build where you use a "build" Python (for your development machine) to
40 The easiest way to do a build is to use the `android.py` script. You can either
41 have it perform the entire build process from start to finish in one step, or
42 you can do it in discrete steps that mirror running `configure` and `make` for
48 ./android.py configure-build
49 ./android.py make-build
50 ./android.py configure-host HOST
51 ./android.py make-host HOST
54 `HOST` identifies which architecture to build. To see the possible values, run
55 `./android.py configure-host --help`.
60 ./android.py build HOST
63 In the end you should have a build Python in `cross-build/build`, and an Android
64 build in `cross-build/HOST`.
66 You can use `--` as a separator for any of the `configure`-related commands –
67 including `build` itself – to pass arguments to the underlying `configure`
68 call. For example, if you want a pydebug build that also caches the results from
72 ./android.py build HOST -- -C --with-pydebug
78 The test suite can be run on Linux, macOS, or Windows:
80 * On Linux, the emulator needs access to the KVM virtualization interface, and
82 * On Windows, you won't be able to do the build on the same machine, so you'll
83   have to copy the `cross-build/HOST` directory from somewhere else.
85 The test suite can usually be run on a device with 2 GB of RAM, but this is
89 and find `hw.ramSize` in both config.ini and hardware-qemu.ini. Either set these
93 Before running the test suite, follow the instructions in the previous section
94 to build the architecture you want to test. Then run the test script in one of
97 * In `--connected` mode, it runs on a device or emulator you have already
98   connected to the build machine. List the available devices with
99   `$ANDROID_HOME/platform-tools/adb devices -l`, then pass a device ID to the
103   ./android.py test --connected emulator-5554
106 * In `--managed` mode, it uses a temporary headless emulator defined in the
107   `managedDevices` section of testbed/app/build.gradle.kts. This mode is slower,
110   We currently define two devices: `minVersion` and `maxVersion`, corresponding
111   to our minimum and maximum supported Android versions. For example:
114   ./android.py test --managed maxVersion
117 By default, the only messages the script will show are Python's own stdout and
118 stderr. Add the `-v` option to also show Gradle output, and non-Python logcat
121 Any other arguments on the `android.py test` command line will be passed through
122 to `python -m test` – use `--` to separate them from android.py's own options.
124 Guide](https://devguide.python.org/testing/run-write-tests/) for common options
126 such as `-j`.
128 Every time you run `android.py test`, changes in pure-Python files in the
130 and architecture-specific files such as sysconfigdata, will not take effect
131 until you re-run `android.py make-host` or `build`.