Changes between Version 21 and Version 22 of BuildingQtOnSymbian

Timestamp:

Feb 16, 2011 1:00:27 PM (13 years ago)

Author:

siddharth.mathur@nokia.com

Comment:

--

BuildingQtOnSymbian

@@ -54 +54 @@
 == Using RVCT4.0 and 64-bit armlink.exe ==
   * RVCT4.0 is know to work nicely with Webkit.org trunk, particularly with UDEB mode where 2.2 often segfaults. 
-  * 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) 
+  * 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) 
   * 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}}}
-  * 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 
+  * 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. 
 
-  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) 
+  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) 
   * Back-up your armlink.exe from the 4.0 install 
-  * Obtain the RVCT4.1 toolchain from your organizations compiler tools team, or from ARM.com directly. 
+  * Obtain the RVCT4.1 toolchain from your organization's compiler tools team, or from ARM.com directly. 
   * Extract the 64-bit armlink.exe and drop it over your 4.0 installation's armlink.exe
-  * {{{cd Source}}} and them compile as ARMV5 or ARMV6 {{{sbs -c arm.v6.udeb.rvct4_0}}}
+  * {{{cd Source}}} and them compile as ARMV5 or ARMV6 {{{sbs -c arm.v5.udeb.rvct4_0}}}