Building / Release ghostdocs for Android under Windows

Setup

• install doxygen (used to generate html documentation for external api)
  grab it from http://ftp.stack.nl/pub/users/dimitri/doxygen-1.8.6-setup.exe
  
  
• install graphviz (for the ‘dot’ binary, used to generate graphics for the documentation)
  grab it from http://www.graphviz.org/Download_windows.php
  
  
• install ADT Bundle (includes the Android SDK and NDK - the two can be installed independently if you prefer to avoid installing Eclipse)
  grab it from http://developer.android.com/sdk/index.html
  
  
• install unifdef
  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
  
  
• set ANDROID_HOME and ANDROID_SDK system variables
  set them to correspond with the ADT Bundle's install locations, e.g.:
  
  

  set ANDROID_HOME=C:\android-ndk-r8e
  set ANDROID_SDK=C:\Program Files (x86)\Android\android-sdk

Build Procedure

• get the release tracking sheet
  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
  
  
• add your entry to the end (probably based on an a previous release recorded in the tracking sheet)
  
  
• checkout epage
  git clone ghostscript.com:/home/git-private/sot.git, ensure you checkout the correct branch/tag
  
  
• run build command with extra flagsadd -vs2005 (the build line from the tracking sheet is likely for use under Linux)
  add --setvers, e.g.:
  
  

  --setvers "{customer:Vaultize i8089@issue:8089@version:2.1.28.1@sdate:15/03/2014}"

  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
    (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:
  ./scripts/showbuild.py

Paul Gardiner - 2014-04-16

Comments