BuildingForAndroid.wiki
changeset 296 545c549e454c
child 297 7bfe4334f7dd
equal deleted inserted replaced
295:bcd606524d19 296:545c549e454c
       
     1 #summary Instructions for building Hedgewars for Android
       
     2 #labels Phase-Implementation,Phase-Design,Phase-Support
       
     3 = Hedgewars for Android =
       
     4 == Introduction ==
       
     5 
       
     6 This guide will take you through the steps needed to succesfully compile Hedgewars for Android
       
     7 
       
     8 ==Download==
       
     9 
       
    10 We need to download these packages:
       
    11 
       
    12 * [http://code.google.com/p/hedgewars/ Hedgewars Source]<br>
       
    13 * [http://developer.android.com/sdk/index.html Android SDK] (Latest version will do)<br>
       
    14 * [http://developer.android.com/sdk/ndk/index.html Android NDK] (current version is r5b but anything up will probably work)<br>
       
    15 * ~~[http://freepascal.org/down/source/sources.var FreePascal] (Latest (stable) version will do)~~<br>
       
    16 * [http://sourceforge.net/projects/p-tools/ p-tools] (Fixed freepascal compiler, read below which to download)<br>
       
    17 * [http://ant.apache.org/ Ant] (Linux distro should just use their package manager to get it, version isn't really important)<br>
       
    18 * Java compiler, make sure you get JDK (not JRE) version 6 and up
       
    19 * [http://www.cmake.org/ Cmake]
       
    20 * You will also need qt4 although this is not strictly required for the android build it is needed for the desktop frontend
       
    21 
       
    22 ==Hedgewars Source==
       
    23 
       
    24 Using mercurial you can pull the hedgeroid branch using
       
    25 {{{
       
    26 hg clone https://hedgewars.googlecode.com/hg/ hedgewars
       
    27 }}}
       
    28 
       
    29 ==Android SDK==
       
    30 
       
    31 Download the latest version using the link above. And unzip it at a place you can remember, I’ll refer to the location with `<`SDK`>`. Once you’ve unzipped/extracted the tar navigate to `<`SDK`>`/tools and execute ‘android’. This should bring up a GUI select ‘Available packages’, then ‘Android Repository’ and check atleast SDK Platform Android 1.6 / 2.2 / 4.0. I would recommend checking all of them, but it’s up to you. Next select ‘Install Selected’ press ‘Next’ a couple of times and you should have the SDK installed.
       
    32 
       
    33 Optionally you could permanently add `<`SDK`>`/platform-tools to your $PATH, this makes it easier to use ‘adb’. Adb is the main program to communicate with Android, think logging/pushing and pulling files/shell.
       
    34 
       
    35 If you do not have a real android device you can create an emulator if you do I’d skip this and continue at Android NDK
       
    36 
       
    37 You can use either the GUI, run android and follow the signs or from cli
       
    38 
       
    39 {{{
       
    40 android create avd -n <name> -t 4
       
    41 }}}
       
    42 -n is a name of your choice -t stands for the target ID
       
    43 
       
    44 See this for more information
       
    45 
       
    46 To run the emulator navigate to `<`SDK`>`/tools and run
       
    47 
       
    48 {{{emulator -avd <name>}}}
       
    49 where `<`name`>` is the same name as when you created it with the line above.
       
    50 
       
    51 Note when using ant:
       
    52 Ant needs a JDK, but tries to use a JRE sometimes (there is usually a separate JRE installation outside the JDK). If you get an error about missing tools.jar, make sure Ant is actually attempting to use the JDK. You can coax it to cooperate by setting the JAVA_HOME environment variable to point to the JDK directory.
       
    53 
       
    54 ==Android NDK==
       
    55 
       
    56 Download and untar it, ill refer to the ndk as `<`NDK`>`. That’s it :)
       
    57 
       
    58 ==!FreePascal ==
       
    59 
       
    60 We need to download the sources from the Freepascal website and compile the crosscompiler. ~~I have grabbed the latest stable release 2.4.4 , though any version will work.~~ _Because of a bug in the latest fpc sources I recommend you download the p-tools repository/tar. Follow this link http://sourceforge.net/projects/p-tools/ and find the directory fpc4android in their source repository. Download a tarball and extract it to a new directory, which will be called '<'fpc'>' from now on._ Once downloaded, extract the  tar/zip and place the files in a known directory. I will refer to the directory  with `<`fpc`>` from now on. Next navigate to the `<`fpc`>` directory and compile it, for this various tools are needed, ‘make’ for instance. But also a fpc compiler for your system. Some apt-get/aptitude magic will solve these problems, make a comment if you run in to problems. Use this to compile the crosscompiler:
       
    61 
       
    62 {{{
       
    63 make crossinstall CPU_TARGET=arm OS_TARGET=linux CROSSBINDIR=<ndk>/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin OPT=-dFPC_ARMEL BINUTILSPREFIX=arm-linux-androideabi- INSTALL_PREFIX=<fpc>/fpc_install
       
    64 }}}
       
    65 
       
    66 Note: The flag CROSSBINDDIR points to the ndk/toolchain/../prebuilt/linux-x86/bin dir, change linux-x86 to your host machine, so for windows it would be 'windows' instead of linux-x86
       
    67 
       
    68 Note2: On windows use forward slashes so '/' not '\'
       
    69 ==Final==
       
    70 
       
    71 We will generate the Makefile.android, which is needed to compile hedgewars, download SDL and you’ll need to make sure cmake knows where all the compilers are
       
    72 
       
    73 1.<br>
       
    74 Add `<`NDK`>`:`<`SDK`>`/platform-tools:`<`FPC`>`/compiler to your path, on debian based system I would do it as follows:
       
    75 
       
    76 {{{
       
    77 export PATH=$PATH:/home/xeli/SoftDev/android/ndk
       
    78 export PATH=$PATH:/home/xeli/SoftDev/android/sdk/platform-tools
       
    79 export PATH=$PATH:/home/xeli/SoftDev/android/fpc-2.4.4/compiler
       
    80 }}}
       
    81 
       
    82 (Check google on how to do it for your specific OS if you don't know how)
       
    83 
       
    84 for windows the PATH var should include this, mind the order:
       
    85 {{{
       
    86     - %WINDIR%\System32 (for Java)<br>
       
    87     - <CMake>\bin<br>
       
    88     - <QtSDK>\mingw\bin<br>
       
    89     - <QtSDK>\Desktop\Qt\4.8.0\mingw\bin<br>
       
    90     - <fpc-win>\bin\i386-win32<br>
       
    91     - <fpc-android>\compiler<br>
       
    92     - <ndk><br>
       
    93     - <sdk>\platform-tools<br>
       
    94     - <ant>\bin<br>
       
    95     - <mercurial> (directory containing hg.exe, TortoiseHg dir in my case)<br>
       
    96 }}}
       
    97 
       
    98 
       
    99 2.<br>
       
   100 Now we're gonna download sdl and a couple of its libraries, if you're on linux there's a script you can use
       
   101 {{{
       
   102 cd <hedgewars-root>/project_files/Android-build
       
   103 chmod +x download_libs.sh (might not be needed)
       
   104 ./download_libs.sh
       
   105 }}}
       
   106 This will download and unzip sdl to the expected folders
       
   107 
       
   108 On windows the script should work fine with Git Bash.
       
   109 
       
   110 
       
   111 3.<br>
       
   112 Finally you can use cmake to create the scripts
       
   113 
       
   114 {{{
       
   115 cd <hedgewars-root>
       
   116 cmake . -DANDROID=1
       
   117 }}}
       
   118 
       
   119 on windows you will need some extra arguments:
       
   120 {{{
       
   121 cmake -G "MinGW Makefiles" -DCMAKE_INCLUDE_PATH="%CD%/misc/winutils/include" -DCMAKE_LIBRARY_PATH="%CD%/misc/winutils/lib" -DANDROID=1 .
       
   122 }}}
       
   123 
       
   124 And that’s it. To compile:
       
   125 
       
   126 {{{
       
   127 cd <hedgewars-root>/project_files/Android-build/
       
   128 make -f Makefile.android
       
   129 }}}
       
   130 and it should be installed on your emulator/device if it was connected.
       
   131 
       
   132 On the device/emulator you can start the application up :)
       
   133 
       
   134 
       
   135 
       
   136 
       
   137 TODO verify that it works on OS X, is the depencency list complete now?