BuildAndroid < Sandbox

Tags: view all tags
---+ Building / Release ghostdocs for Android under Windows

Setup
   * *install doxygen* (used to generate html documentation for external api)<br />grab it from http://ftp.stack.nl/pub/users/dimitri/doxygen-1.8.6-setup.exe<br /><br />
   * *install graphviz* (for the ‘dot’ binary, used to generate graphics for the documentation)<br />grab it from http://www.graphviz.org/Download_windows.php<br /><br />
   * *install ADT Bundle* (includes the Android SDK and NDK - the two can be installed independently if you prefer to avoid installing Eclipse)<br />grab it from http://developer.android.com/sdk/index.html<br /><br />
   * <b>install unifdef</b><br />grab source from http://dotat.at/prog/unifdef/unifdef-2.10.zip, build using the vcxproj in the win32 subdirectory, place unifdef.exe in a directory on your PATH<br /><br />
   * <b>set ANDROID_HOME and ANDROID_SDK system variables</b><br />set them to correspond with the ADT Bundle's install locations, e.g.:<br /><br /> <blockquote> <verbatim>set ANDROID_HOME=C:\android-ndk-r8e
set ANDROID_SDK=C:\Program Files (x86)\Android\android-sdk</verbatim> </blockquote>

Build Procedure
   * <b>get the release tracking sheet</b><br />currently held in cvs at /home/robin/PicselCVS checkout docs/releases/Release_Tracking_Sheet.xls, but likely soon to be subsumed by a twiki page<br /><br />
   * <b>add your entry to the end </b>(probably based on an a previous release recorded in the tracking sheet)<br /><br />
   * <b>checkout epage<br /></b>git clone ghostscript.com:/home/git-private/sot.git, ensure you checkout the correct branch/tag<br /><br />
   * <b>run build command with extra flags</b>add -vs2005 (the build line from the tracking sheet is likely for use under Linux)<br />add --setvers, e.g.:<br /><br /> <blockquote> <verbatim>--setvers "{customer:Vaultize i8089@issue:8089@version:2.1.28.1@sdate:15/03/2014}"</verbatim> </blockquote> Broken down:
      * customer: customer name; possibly may be displayed on splashscreen; at least for iOS builds we add the issue number too to ensure it's displayed on the splashscreen (I think)
      * issue: should match the issue number in the spreadsheet
      * version: should match spreadsheet
      * sdate: Start date for the build. UK format. Use today's date normally. It is not checked unless edate is set.
      * Optional: edate: If this is set, the end date - the build will refuse to start if started after this date, or before the sdate. Set only for evaluation builds<br />(Note how the issue number is put after the customer name, and that the date is in UK format)
   * *find the generated zip file* it’s probably on the first line of output from:<br />./scripts/showbuild.py
-- %USERSIG{PaulGardiner - 2014-04-16}%
---++ Comments

%COMMENT%
Topic revision: r2 - 2014-04-16 - PaulGardiner