Difference: BuildAndroid (1 vs. 2)

Revision 22014-04-16 - PaulGardiner

Line: 1 to 1
 

Building / Release ghostdocs for Android under Windows

Deleted:
<
<

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 ]
port install graphviz

install Xcode version 4.6.3, and use xcode-select to ensure that is the active version for command line builds - and also make sure it’s called /Applications/Xcode.App as that path is hardcoded in some places

ensure cvs uses ssh; add this to your .bashrc or equivalent:
export CVS_RSH=ssh

Build Procedure

Get the release tracking sheet:

cvs -d :ext:ghostscript.com:/home/robin/PicselCVS checkout docs/releases/Release_Tracking_Sheet.xls

Add your entry to the end

Commit spreadsheet to cvs

Checkout epage:
git clone ghostscript.com:/home/git-private/sot.git

checkout correct tag etc

get release command from spreadsheet

add setvers onto end of build command, eg:

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

[Note how the issue number is put after the customer name, and that the date is in UK format.]

Broken down:

  1. 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)
  2. issue: should match the issue number in the spreadsheet
  3. version: should match spreadsheet
  4. sdate: Start date for the build. UK format. Use today's date normally. It is not checked unless edate is set.
  5. 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.

run release command… wait…

find the generated zip file; it’s probably on the first line of output from:
./scripts/showbuild.py

Testflight builds

Setup as per above.

Install the artifex iOS distribution private key (~joseph on casper); ask Joseph for password.

Fetch the latest provisioning profile from the artifex iOS develop account (ie. add the account under xcode preferences if necessary, and then hit 'refresh').

Run:

./scripts/release.py appstore-ios-so

Run ./scripts/showbuild.py to find the the ipa file, and drag it onto the testflight app.

-- Joseph Heenan - 2014-03-27

 
Added:
>
>
Setup

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

<--/commentPlugin-->

Revision 12014-04-15 - PaulGardiner

Line: 1 to 1
Added:
>
>

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 ]
port install graphviz

install Xcode version 4.6.3, and use xcode-select to ensure that is the active version for command line builds - and also make sure it’s called /Applications/Xcode.App as that path is hardcoded in some places

ensure cvs uses ssh; add this to your .bashrc or equivalent:
export CVS_RSH=ssh

Build Procedure

Get the release tracking sheet:

cvs -d :ext:ghostscript.com:/home/robin/PicselCVS checkout docs/releases/Release_Tracking_Sheet.xls

Add your entry to the end

Commit spreadsheet to cvs

Checkout epage:
git clone ghostscript.com:/home/git-private/sot.git

checkout correct tag etc

get release command from spreadsheet

add setvers onto end of build command, eg:

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

[Note how the issue number is put after the customer name, and that the date is in UK format.]

Broken down:

  1. 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)
  2. issue: should match the issue number in the spreadsheet
  3. version: should match spreadsheet
  4. sdate: Start date for the build. UK format. Use today's date normally. It is not checked unless edate is set.
  5. 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.

run release command… wait…

find the generated zip file; it’s probably on the first line of output from:
./scripts/showbuild.py

Testflight builds

Setup as per above.

Install the artifex iOS distribution private key (~joseph on casper); ask Joseph for password.

Fetch the latest provisioning profile from the artifex iOS develop account (ie. add the account under xcode preferences if necessary, and then hit 'refresh').

Run:

./scripts/release.py appstore-ios-so

Run ./scripts/showbuild.py to find the the ipa file, and drag it onto the testflight app.

-- Joseph Heenan - 2014-03-27

Comments

<--/commentPlugin-->
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2014 Artifex Software Inc