dev-manual: Updated "Requirements" section for creating partitioned images

Wic is not using parted and other runtime dependencies from host
system anymore.  It uses native tools instead.  Removed host parted
from the list of requirements.  Added instructions to build native
tools.

(From yocto-docs rev: 6c84e9d4f969952240a869ec83ea149a75c17978)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 6 insertions, 6 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index c856775303..0ea494052e 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3788,12 +3788,6 @@
                         development host system.
                         </para></listitem>
                     <listitem><para>
-                        The
-                        <ulink url='http://www.gnu.org/software/parted/'>GNU Parted</ulink>
-                        package must be installed on your development host
-                        system.
-                        </para></listitem>
-                    <listitem><para>
                         You need to have the build artifacts already
                         available, which typically means that you must
                         have already created an image using the
@@ -3806,6 +3800,12 @@
                         in the form generated by the build system.
                         </para></listitem>
                     <listitem><para>
+                        You must build several native tools:
+                        <literallayout class='monospaced'>
+     $ bitbake parted-native dosfstools-native mtools-native
+                        </literallayout>
+                        </para></listitem>
+                    <listitem><para>
                         You must have sourced one of the build environment
                         setup scripts (i.e.
                         <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>