Lines Matching refs:to
7 Beside basic tools like perl and make, you'll need to download the Android
9 version was actually tested. There is no reason to believe that macOS
12 role, the goal is to support a range of most recent versions.
18 to find out the configuration target for you. You have to name your
25 you still need to know the prefix to extend your PATH, in order to
29 Apart from `PATH` adjustment, you need to set `ANDROID_NDK_ROOT` environment
30 to point at the `NDK` directory. If you're using a side-by-side NDK the path
35 `android-21`, etc. By default, latest API level is chosen. If you need to target
36 an older platform pass the argument `-D__ANDROID_API__=N` to `Configure`,
38 to compile for Android 10 arm64 with a side-by-side NDK r20.0.5594570
46 directory, so the bin path will be slightly different. EG: to compile
55 variable set to `$ANDROID_NDK_ROOT/platforms/android-<api>/arch-<arch>` to
57 to facilitate migration from older projects. However, since API level
59 conflict, and mixing the two is therefore not supported. Migration to
62 One can engage clang by adjusting PATH to cover the same NDK's clang. Just
63 keep in mind that if you miss it, Configure will try to use gcc...
64 Also, PATH would need even further adjustment to cover unprefixed, yet
65 target-specific, ar and ranlib. It's possible that you don't need to
68 Another option is to create so called "standalone toolchain" tailored
70 location to `ANDROID_NDK_ROOT`. In such case, you have to pass matching
71 target name to Configure and shouldn't use `-D__ANDROID_API__=N`. `PATH`
79 Even though build output targets alien system, it's possible to execute
81 linking. Pass -static to Configure, then edit generated Makefile and
82 remove occurrences of -ldl and -pie flags. You would also need to pick
83 API version that comes with usable static libraries, 42/2=21 used to
84 work. Once built, you should be able to
88 If you need to pass additional flag to qemu, quotes are your friend, e.g.
