diff options
-rw-r--r-- | doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml | 27 |
1 files changed, 15 insertions, 12 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 7f4d817..26e37fb 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,7 +95,7 @@ | |||
95 | <listitem> | 95 | <listitem> |
96 | <para>Download the zip image from <ulink | 96 | <para>Download the zip image from <ulink |
97 | url="https://portal.enea.com/access/">portal.enea.com/access</ulink> | 97 | url="https://portal.enea.com/access/">portal.enea.com/access</ulink> |
98 | and unzip it on the host machine. </para> | 98 | and unzip it on the host machine.</para> |
99 | </listitem> | 99 | </listitem> |
100 | 100 | ||
101 | <listitem> | 101 | <listitem> |
@@ -124,9 +124,9 @@ | |||
124 | </listitem> | 124 | </listitem> |
125 | 125 | ||
126 | <listitem> | 126 | <listitem> |
127 | <para>Make sure you have <literal>libel-dev</literal> installed into | 127 | <para>Make sure you have <literal>libelf-dev</literal> installed |
128 | your host distribution. This is needed for working with the kernel | 128 | into your host distribution. This is needed for working with the |
129 | and building kernel modules.<programlisting>$ sudo apt-get install libelf-dev</programlisting></para> | 129 | kernel and building kernel modules.<programlisting>$ sudo apt-get install libelf-dev</programlisting></para> |
130 | </listitem> | 130 | </listitem> |
131 | </orderedlist> | 131 | </orderedlist> |
132 | </section> | 132 | </section> |
@@ -249,9 +249,9 @@ MODULE_LICENSE("GPL");</programlisting> | |||
249 | <section id="deploy-artifacts"> | 249 | <section id="deploy-artifacts"> |
250 | <title>Deploying your artifacts</title> | 250 | <title>Deploying your artifacts</title> |
251 | 251 | ||
252 | <para>You can use <literal>ssh</literal> to deploy your artifacts on the | 252 | <para>A network connection is needed to deploy the artifacts on the host |
253 | host target. For this you will need a network connection to the target, | 253 | target. Use <command>scp</command> to copy it to the desired |
254 | to use <literal>scp</literal> to copy to the desired location.</para> | 254 | location:</para> |
255 | 255 | ||
256 | <programlisting># scp helloworld root@[target_ip_address]:/tmp</programlisting> | 256 | <programlisting># scp helloworld root@[target_ip_address]:/tmp</programlisting> |
257 | </section> | 257 | </section> |
@@ -271,7 +271,7 @@ MODULE_LICENSE("GPL");</programlisting> | |||
271 | <para>To build the ODM target kit, access the location of the ODM SDK | 271 | <para>To build the ODM target kit, access the location of the ODM SDK |
272 | and run the <command>make</command> command:</para> | 272 | and run the <command>make</command> command:</para> |
273 | 273 | ||
274 | <programlisting>$ cd [sdkdir]/sysroots/corei7-64-enea-linux/usr/local/odm/odm-sdk-4.0.3-x86_64/ | 274 | <programlisting>$ cd [sdkdir]/sysroots/corei7-64-enea-linux/usr/local/odm/odm-sdk-4.0.3-x86_64/ |
275 | $ make</programlisting> | 275 | $ make</programlisting> |
276 | </section> | 276 | </section> |
277 | </section> | 277 | </section> |
@@ -368,8 +368,8 @@ $ make</programlisting> | |||
368 | <para>Or alternatively, you can download from an upstream git | 368 | <para>Or alternatively, you can download from an upstream git |
369 | repository:<programlisting>$ devtool add bbexample https://github.com/whbruce/bbexample.git</programlisting></para> | 369 | repository:<programlisting>$ devtool add bbexample https://github.com/whbruce/bbexample.git</programlisting></para> |
370 | 370 | ||
371 | <para><literal>devtool</literal> creates a Git repository locally | 371 | <para><literal><command>devtool</command></literal> creates a Git |
372 | during extraction at: | 372 | repository locally during extraction at: |
373 | <literal>sdkdir/workspace/source/bbexample</literal>, where the | 373 | <literal>sdkdir/workspace/source/bbexample</literal>, where the |
374 | recipe will be created automatically. E.g: | 374 | recipe will be created automatically. E.g: |
375 | <literal>sdkdir/workspace/recipes/bbexample/bbexample.bb</literal>.</para> | 375 | <literal>sdkdir/workspace/recipes/bbexample/bbexample.bb</literal>.</para> |
@@ -444,8 +444,10 @@ enabled in your configuration</programlisting>To rectify the dependency issue | |||
444 | application:</para> | 444 | application:</para> |
445 | 445 | ||
446 | <para><programlisting>$ devtool build bbexample</programlisting><note> | 446 | <para><programlisting>$ devtool build bbexample</programlisting><note> |
447 | <para>The image build result can be seen at: | 447 | <para>The image build result can be seen at |
448 | <literal>sdkdir/tmp/deploy/images/qemux86-64</literal>.</para> | 448 | <literal><sdkdir>/tmp/work/<arch>/<recipe></literal>. |
449 | E.g. | ||
450 | <literal>sdkdir/tmp/work/corei7-64-enea-linux/bbexample</literal>.</para> | ||
449 | </note></para> | 451 | </note></para> |
450 | </section> | 452 | </section> |
451 | </section> | 453 | </section> |
@@ -524,6 +526,7 @@ inherit core-image</programlisting> | |||
524 | 526 | ||
525 | <note> | 527 | <note> |
526 | <para>The image build result can be seen at: | 528 | <para>The image build result can be seen at: |
529 | <literal>sdkdir/tmp/deploy/images/<target></literal>. E.g.: | ||
527 | <literal>sdkdir/tmp/deploy/images/qemux86-64</literal></para> | 530 | <literal>sdkdir/tmp/deploy/images/qemux86-64</literal></para> |
528 | </note> | 531 | </note> |
529 | </listitem> | 532 | </listitem> |