overview-manual: Converted paragraph on figure to note

The paragraph at the end of the section about the file
hierarchies is better cast as a note.

(From yocto-docs rev: 4e8a33be61ea1ea5db12fc5fc97832393213fb5d)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-05-02 10:26:00 -07:00
committed by Richard Purdie
parent 02aa4d3ec4
commit 992c7e5634

View File

@@ -1215,15 +1215,17 @@
</itemizedlist>
</para></listitem>
</itemizedlist>
In the previous figure, notice that two sample
hierarchies exist: one based on package architecture (i.e.
<filename>PACKAGE_ARCH</filename>) and one based on a
machine (i.e. <filename>MACHINE</filename>).
The underlying structures are identical.
The differentiator being what the OpenEmbedded build
system is using as a build target (e.g. general
architecture, a build host, an SDK, or a specific
machine).
<note>
In the previous figure, notice that two sample
hierarchies exist: one based on package architecture (i.e.
<filename>PACKAGE_ARCH</filename>) and one based on a
machine (i.e. <filename>MACHINE</filename>).
The underlying structures are identical.
The differentiator being what the OpenEmbedded build
system is using as a build target (e.g. general
architecture, a build host, an SDK, or a specific
machine).
</note>
</para>
</section>