[FE training-materials-updates] yocto: labs: split write and debug section

[Antoine Ténart]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=f878ecc3e5196331c779358b7144f90e24f21358

>---------------------------------------------------------------

commit f878ecc3e5196331c779358b7144f90e24f21358
Author: Antoine Tenart <antoine.tenart at free-electrons.com>
Date:   Fri Nov 7 14:41:04 2014 +0100

    yocto: labs: split write and debug section
    
    Signed-off-by: Antoine Tenart <antoine.tenart at free-electrons.com>


>---------------------------------------------------------------

f878ecc3e5196331c779358b7144f90e24f21358
 labs/yocto-add-application/yocto-add-application.tex | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/labs/yocto-add-application/yocto-add-application.tex b/labs/yocto-add-application/yocto-add-application.tex
index 81dea3d..7f4ea81 100644
--- a/labs/yocto-add-application/yocto-add-application.tex
+++ b/labs/yocto-add-application/yocto-add-application.tex
@@ -31,7 +31,14 @@ family. In order to deal with the text based user interface, nInvaders uses the
 ncurses library.
 
 First try to find the project homepage, download the sources and have a first
-look: license, Makefile, requirements \dots
+look: license, Makefile, requirements\dots
+
+\section{Write the common recipe}
+
+Create an appropriate common file, ending in \code{.inc}
+
+In this file add the common configuration variables: source URI, package
+description\dots
 
 \section{Write the version specific recipe}
 
@@ -39,14 +46,9 @@ Create a file that respects the Yocto nomenclature: \code{${PN}_${PV}.bb}
 %stopzone
 
 Add the required common configuration variables: archive checksum, license file
-checksum, package revision \dots
+checksum, package revision\dots
 
-\section{Write the common recipe}
-
-Create an appropriate common file, ending in \code{.inc}
-
-In this file add the common configuration variables: source URI, package
-description \dots
+\section{Testing and troubleshooting}
 
 You can check the whole packaging process is working fine by explicitly running
 the build task on the \code{nInvaders} recipe: