This creates a working sysroot that we can feed to Configure later. To your PATH, where $ANDROID_NDK is the location where you unpacked the NDK, and $TARGETARCH is your target's architecture. With those two in hand, you should add $ANDROID_NDK/toolchains/$TARGETARCH-4.8/prebuilt/`uname | tr '' ''`-x86_64/bin As of 2014, most Android devices run on ARM, so that is generally a safe bet. There's three possible options: arm-linux-androideabi for ARM, mipsel-linux-android for MIPS, and simply x86 for x86. # Determine the architecture you'll be cross-compiling for You'll want the normal, non-legacy version. # Get the Android Native Development Kit (NDK) On a similar vein, the examples below use the 4.8 toolchain if you want to use something older or newer (for example, the 4.4.3 toolchain included in the 8th revision of the NDK), just change those to the relevant version. If your host system's architecture is 32 bits, remember to change the x86_64's below to x86's. While Google also provides an NDK for Windows, these steps won't work native there, although it may be possible to cross-compile through different means. These instructions assume an Unixish build environment on your host system they've been tested on Linux and OS X, and may work on Cygwin and MSYS. This document describes how to set up your host environment when attempting to build Perl for Android. The latter portions describe how to build perl native using one of the toolchains available on the Play Store. The first portions of this document contains instructions to cross-compile Perl for Android 2.0 and later, using the binaries provided by Google. Perlandroid - Perl under Android #SYNOPSIS Determine the architecture you'll be cross-compiling for.Get the Android Native Development Kit (NDK).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |