From c8221d41c83631f1fdb67f1568e0cd3a2ef0c633 Mon Sep 17 00:00:00 2001 From: Sona Sarmadi Date: Wed, 4 Jul 2018 14:40:51 +0200 Subject: Fixed some review comments on SDK chapter - Added path to SDK installers: Enea_NFV_Access_2.0/x86_64/install/esdk Enea_NFV_Access_2.0/x86_64/install/sdk - To avoid confusion, use only [sdkdir] please. Signed-off-by: Sona Sarmadi --- .../doc/using_nfv_access_sdks.xml | 61 ++++++++++++---------- 1 file changed, 34 insertions(+), 27 deletions(-) diff --git a/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml b/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml index 26e37fb..6280338 100644 --- a/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml +++ b/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml @@ -95,20 +95,24 @@ Download the zip image from portal.enea.com/access - and unzip it on the host machine. + and unzip it on the host machine e.g. in the + Enea_NFV_Access_2.0 directory. - $ ./install-sdk.shAfter - running this script, when prompted, select to install the toolchain - in a desired directory, referred to henceforth as - sdkdir. + Run the install script located at + Enea_NFV_Access_2.0/x86_64/install/sdk directory, + when prompted, select to install the toolchain in a desired + directory, referred to henceforth as + [sdkdir]. + + $ ./install-sdk.sh A default path where the toolchain will be installed will be shown in the prompt. The installer will unpack the environment-setup script in - sdkdir and the toolchain under - sdkdir/sysroots. + [sdkdir] and the toolchain under + [sdkdir]/sysroots. Choose a unique directory for each toolchain. Installing a @@ -176,7 +180,7 @@ hello world Before cross-compiling kernel modules, inside the kernel source tree in the installed SDK, available at - sdkdir/sysroots/targetarch-enea-linux/usr/src/kernel, + [sdkdir]/sysroots/targetarch-enea-linux/usr/src/kernel, run the following command: make scripts prepare @@ -310,20 +314,21 @@ $ make Installing the Extensible SDK To install the Extensible SDK on your host development machine, - run the installation script provided in the /esdk + run the installation script provided in the + Enea_NFV_Access_2.0/x86_64/install/esdk folder: $ ./install-sdk.shWhen prompted, select to install the toolchain in a desired directory, - referred to henceforth as sdkdir. + referred to henceforth as [sdkdir]. A default path where the toolchain will be installed will be shown in the prompt. The installer unpacks the environment-setup script in - sdkdir and the toolchain under - sdkdir/sysroots. + [sdkdir] and the toolchain under + [sdkdir]/sysroots. Choose a unique directory for each toolchain. Installing a @@ -370,9 +375,9 @@ $ make devtool creates a Git repository locally during extraction at: - sdkdir/workspace/source/bbexample, where the + [sdkdir]/workspace/source/bbexample, where the recipe will be created automatically. E.g: - sdkdir/workspace/recipes/bbexample/bbexample.bb. + [sdkdir]/workspace/recipes/bbexample/bbexample.bb. @@ -380,7 +385,7 @@ $ make layer Use devtool modify [recipe] on any recipe - from sdkdir/layers/poky/meta*, example: + from [sdkdir]/layers/poky/meta*, example: $ devtool modify curl @@ -395,8 +400,9 @@ $ make Clone a recipe from the upstream Yocto project, e.g. meta-security: - $ pushd sdkdir/layers/poky -$ git clone -b rocko git://git.yoctoproject.org/meta-security + $ pushd [sdkdir]/layers/poky +$ git clone -b rocko git://git.yoctoproject.org/meta-security +$ popd @@ -411,13 +417,13 @@ enabled in your configurationTo rectify the dependency issue exemplified above, clone meta-perl from openembedded and run add-layers again:$ layers/poky/bitbake/bin/bitbake-layers add-layer layers/poky/meta-securityNow - sdkdir/layers/poky/meta-security is created + [sdkdir]/layers/poky/meta-security is created and the layer has been added to - sdkdir/conf/bblayers.conf:${SDKBASEMETAPATH}/layers/poky/meta-security + [sdkdir]/conf/bblayers.conf: The image build result can be seen at: - sdkdir/tmp/deploy/images/qemux86-64 + [sdkdir]/tmp/deploy/images/qemux86-64 @@ -429,8 +435,8 @@ enabled in your configurationTo rectify the dependency issue $ devtool modify isic The following directories and files will be created: - sdkdir/workspace/appends/isic_0.07.bbappend - and sdkdir/workspace/sources/isic. + [sdkdir]/workspace/appends/isic_0.07.bbappend + and [sdkdir]/workspace/sources/isic. @@ -445,9 +451,9 @@ enabled in your configurationTo rectify the dependency issue $ devtool build bbexample The image build result can be seen at - <sdkdir>/tmp/work/<arch>/<recipe>. + <[sdkdir]>/tmp/work/<arch>/<recipe>. E.g. - sdkdir/tmp/work/corei7-64-enea-linux/bbexample. + [sdkdir]/tmp/work/corei7-64-enea-linux/bbexample. @@ -526,8 +532,9 @@ inherit core-image The image build result can be seen at: - sdkdir/tmp/deploy/images/<target>. E.g.: - sdkdir/tmp/deploy/images/qemux86-64 + [sdkdir]/tmp/deploy/images/<target>. + E.g.: + [sdkdir]/tmp/deploy/images/qemux86-64 @@ -539,4 +546,4 @@ inherit core-image - \ No newline at end of file + -- cgit v1.2.3-54-g00ecf