Update cross-building.md to apply recent changes

We changed name of ARM with softfp ABI from arm-softfp to armel.

Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>

1 files changed, 7 insertions, 6 deletions

diff --git a/Documentation/building/cross-building.md b/Documentation/building/cross-building.md
index 7431c26a62..cc35b1b6aa 100644
--- a/Documentation/building/cross-building.md
+++ b/Documentation/building/cross-building.md
@@ -1,7 +1,7 @@
 Cross Compilation for ARM on Linux
 ==================================
 
-It is possible to build CoreFx on Linux for arm, arm-softft, or arm64 by cross compiling.
+It is possible to build CoreFx on Linux for arm, armel, or arm64 by cross compiling.
 It is very similar to the cross compilation procedure of CoreCLR.
 
 Requirements
@@ -15,7 +15,7 @@ In addition, to cross compile CoreFX, the binutils for the target are required.
 
     lgs@ubuntu ~/git/corefx/ $ sudo apt-get install binutils-arm-linux-gnueabihf
 
-for arm-softfp:
+for armel:
 
     lgs@ubuntu ~/git/corefx/ $ sudo apt-get install binutils-arm-linux-gnueabi
 
@@ -28,8 +28,9 @@ Generating the rootfs
 ---------------------
 The `cross\build-rootfs.sh` script can be used to download the files needed for cross compilation. It will generate an Ubuntu 14.04 rootfs as this is what CoreFX targets.
 
-    Usage: build-rootfs.sh [BuildArch]
-    BuildArch can be: arm, arm-softfp, arm64
+    Usage: ./cross/build-rootfs.sh [BuildArch] [UbuntuCodeName]
+    BuildArch can be: arm, armel, arm64, x86
+    UbuntuCodeName - optional, Code name for Ubuntu, can be: trusty(default), vivid, wily, xenial. If BuildArch is armel, jessie(default) or tizen.
 
 The `build-rootfs.sh` script must be run as root, as it has to make some symlinks to the system. It will, by default, generate the rootfs in `cross\rootfs\<BuildArch>` however this can be changed by setting the `ROOTFS_DIR` environment variable.
 
@@ -73,7 +74,7 @@ As usual the generated binaries will be found in `bin/BuildOS.BuildArch.BuildTyp
 
 Compiling for managed CoreFX
 ============================
-The managed components of CoreFX are architecture-independent and thus do not require a special build for arm, arm-softfp or arm64.
+The managed components of CoreFX are architecture-independent and thus do not require a special build for arm, armel or arm64.
 
 Many of the managed binaries are also OS-independent, e.g. System.Linq.dll, while some are OS-specific, e.g. System.IO.FileSystem.dll, with different builds for Windows and Linux.
 
@@ -101,4 +102,4 @@ prajwal@ubuntu ~/corefx $ ./scripts/arm32_ci_script.sh \
     --buildConfig=Release
 ```
 
-The Linux ARM Emulator is based on the soft floating point and thus the native binaries are generated for the arm-softfp architecture. The corefx binaries generated by the above command can be found at `~/corefx/bin/Linux.arm-softfp.Release`, `~/corefx/bin/Linux.AnyCPU.Release`, `~/corefx/bin/Unix.AnyCPU.Release`, and `~/corefx/bin/AnyOS.AnyCPU.Release`.
+The Linux ARM Emulator is based on the soft floating point and thus the native binaries are generated for the armel architecture. The corefx binaries generated by the above command can be found at `~/corefx/bin/Linux.armel.Release`, `~/corefx/bin/Linux.AnyCPU.Release`, `~/corefx/bin/Unix.AnyCPU.Release`, and `~/corefx/bin/AnyOS.AnyCPU.Release`.