Changes between Version 21 and Version 22 of BuildingQtOnSymbian


Ignore:
Timestamp:
Feb 16, 2011 1:00:27 PM (12 years ago)
Author:
siddharth.mathur@nokia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildingQtOnSymbian

    v21 v22  
    5454== Using RVCT4.0 and 64-bit armlink.exe ==
    5555  * RVCT4.0 is know to work nicely with Webkit.org trunk, particularly with UDEB mode where 2.2 often segfaults.
    56   * First set up your RVCT4.0 installation by obtaining the binaries and setting up environment variables per ARM's instructions (Nokians may use SymSEE to activate it)
     56  * First set up your RVCT4.0 installation by obtaining the binaries and setting up '''environment variables''' per ARM's instructions (Nokians may use SymSEE to activate it)
    5757  * If using with Symbian3 SDKs, you may have to compile the '''compiler support libraries''' first (or you will see linker errors) : {{{sbs -b sf\os\kernelhwsrv\kernel\eka\compsupp\bld.inf -b sf\os\kernelhwsrv\kernel\eka\euser\bld.inf -c arm.v5.urel.rvct4_0 -c arm.v5.udeb.rvct4_0}}}
    58   * To explicitly as SBSv2/Raptor to use RVCT4.0 with Symbian3 SDKS, use {{{sbs -c arm.v5.urel.rvct4_0}}}. Symbian MCL supports RVCT4.0 out of the box, therefore
     58  * To explicitly as SBSv2/Raptor to use RVCT4.0 with Symbian3 SDKS, use {{{sbs -c arm.v5.urel.rvct4_0}}}. Symbian MCL supports RVCT4.0 out of the box, so the simpler invocation may be used.
    5959
    60   In case your link stages run into OOM even with the .py script or with --minimal, you need a 64-bit Windows OS and a 64-bit linker (armlink.exe)
     60  In case your link stages run into OOM even with --minimal, you need a 64-bit Windows OS and a 64-bit linker (armlink.exe)
    6161  * Back-up your armlink.exe from the 4.0 install
    62   * Obtain the RVCT4.1 toolchain from your organizations compiler tools team, or from ARM.com directly.
     62  * Obtain the RVCT4.1 toolchain from your organization's compiler tools team, or from ARM.com directly.
    6363  * Extract the 64-bit armlink.exe and drop it over your 4.0 installation's armlink.exe
    64   * {{{cd Source}}} and them compile as ARMV5 or ARMV6 {{{sbs -c arm.v6.udeb.rvct4_0}}}
     64  * {{{cd Source}}} and them compile as ARMV5 or ARMV6 {{{sbs -c arm.v5.udeb.rvct4_0}}}