diff options
Diffstat (limited to 'documentation/poky-ref-manual/development.xml')
-rw-r--r-- | documentation/poky-ref-manual/development.xml | 21 |
1 files changed, 11 insertions, 10 deletions
diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml index 58e725258e..76a0423f65 100644 --- a/documentation/poky-ref-manual/development.xml +++ b/documentation/poky-ref-manual/development.xml | |||
@@ -1,5 +1,6 @@ | |||
1 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | 1 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | 2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" |
3 | [<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] > | ||
3 | 4 | ||
4 | <chapter id="platdev"> | 5 | <chapter id="platdev"> |
5 | <title>Platform Development with the Yocto Project</title> | 6 | <title>Platform Development with the Yocto Project</title> |
@@ -231,7 +232,7 @@ | |||
231 | still defined so you can use commands such as <filename>configure</filename> and | 232 | still defined so you can use commands such as <filename>configure</filename> and |
232 | <filename>make</filename>. | 233 | <filename>make</filename>. |
233 | The commands execute just as if the Yocto Project build system were executing them. | 234 | The commands execute just as if the Yocto Project build system were executing them. |
234 | Consequently, workng this way can be helpful when debugging a build or preparing | 235 | Consequently, working this way can be helpful when debugging a build or preparing |
235 | software to be used with the Yocto Project build system. | 236 | software to be used with the Yocto Project build system. |
236 | </para> | 237 | </para> |
237 | 238 | ||
@@ -262,7 +263,7 @@ | |||
262 | or <filename>compile</filename> commands as if they were being run by | 263 | or <filename>compile</filename> commands as if they were being run by |
263 | the Yocto Project build system itself. | 264 | the Yocto Project build system itself. |
264 | As noted earlier, the working directory also automatically changes to the | 265 | As noted earlier, the working directory also automatically changes to the |
265 | source directory (<glossterm><link linkend='var-S'>S</link></glossterm>). | 266 | source directory (<filename><link linkend='var-S'>S</link></filename>). |
266 | </para> | 267 | </para> |
267 | 268 | ||
268 | <para> | 269 | <para> |
@@ -284,7 +285,7 @@ | |||
284 | 285 | ||
285 | <para> | 286 | <para> |
286 | Because an external shell is launched rather than opening directly into the | 287 | Because an external shell is launched rather than opening directly into the |
287 | original terminal window, it allows easier interaction with Bitbake's multiple | 288 | original terminal window, it allows easier interaction with BitBake's multiple |
288 | threads as well as accomodates a future client/server split. | 289 | threads as well as accomodates a future client/server split. |
289 | </para> | 290 | </para> |
290 | 291 | ||
@@ -294,7 +295,7 @@ | |||
294 | instead of just using <filename>gcc</filename>. | 295 | instead of just using <filename>gcc</filename>. |
295 | The same applies to other applications such as <filename>binutils</filename>, | 296 | The same applies to other applications such as <filename>binutils</filename>, |
296 | <filename>libtool</filename> and so forth. | 297 | <filename>libtool</filename> and so forth. |
297 | The Yocto Project has setup environment variables such as <filename>CC</filename> | 298 | BitBake sets up environment variables such as <filename>CC</filename> |
298 | to assist applications, such as <filename>make</filename> to find the correct tools.</para> | 299 | to assist applications, such as <filename>make</filename> to find the correct tools.</para> |
299 | <para>It is also worth noting that <filename>devshell</filename> still works over | 300 | <para>It is also worth noting that <filename>devshell</filename> still works over |
300 | X11 forwarding and similar situations</para> | 301 | X11 forwarding and similar situations</para> |
@@ -333,7 +334,7 @@ | |||
333 | It also allows you to perform post-mortem style analysis of program crashes. | 334 | It also allows you to perform post-mortem style analysis of program crashes. |
334 | GDB is available as a package within the Yocto Project and by default is | 335 | GDB is available as a package within the Yocto Project and by default is |
335 | installed in sdk images. | 336 | installed in sdk images. |
336 | See <xref linkend='ref-images'>Reference: Images</xref> for a description of these | 337 | See the "<link linkend='ref-images'>Reference: Images</link>" appendix for a description of these |
337 | images. | 338 | images. |
338 | You can find information on GDB at <ulink url="http://sourceware.org/gdb/"/>. | 339 | You can find information on GDB at <ulink url="http://sourceware.org/gdb/"/>. |
339 | </para> | 340 | </para> |
@@ -671,7 +672,7 @@ | |||
671 | <para> | 672 | <para> |
672 | A graphical user interface for OProfile is also available. | 673 | A graphical user interface for OProfile is also available. |
673 | You can download and build this interface from the Yocto Project at | 674 | You can download and build this interface from the Yocto Project at |
674 | <ulink url="http://git.yoctoproject.org/cgit.cgi/oprofileui/"></ulink>. | 675 | <ulink url="&YOCTO_GIT_URL;/cgit.cgi/oprofileui/"></ulink>. |
675 | If the "tools-profile" image feature is selected, all necessary binaries | 676 | If the "tools-profile" image feature is selected, all necessary binaries |
676 | are installed onto the target device for OProfileUI interaction. | 677 | are installed onto the target device for OProfileUI interaction. |
677 | </para> | 678 | </para> |
@@ -679,7 +680,7 @@ | |||
679 | <para> | 680 | <para> |
680 | Even though the Yocto Project usually includes all needed patches on the target device, you | 681 | Even though the Yocto Project usually includes all needed patches on the target device, you |
681 | might find you need other OProfile patches for recent OProfileUI features. | 682 | might find you need other OProfile patches for recent OProfileUI features. |
682 | If so, see the <ulink url='http://git.yoctoproject.org/cgit.cgi/oprofileui/tree/README'> | 683 | If so, see the <ulink url='&YOCTO_GIT_URL;/cgit.cgi/oprofileui/tree/README'> |
683 | OProfileUI README</ulink> for the most recent information. | 684 | OProfileUI README</ulink> for the most recent information. |
684 | </para> | 685 | </para> |
685 | 686 | ||
@@ -765,8 +766,8 @@ | |||
765 | is not always necessary to actually have them on the device for OProfile use. | 766 | is not always necessary to actually have them on the device for OProfile use. |
766 | All that is needed is a copy of the filesystem with the debug symbols present | 767 | All that is needed is a copy of the filesystem with the debug symbols present |
767 | on the viewer system. | 768 | on the viewer system. |
768 | The <link linkend='platdev-gdb-remotedebug-launch-gdb'>Launching GDB | 769 | The "<link linkend='platdev-gdb-remotedebug-launch-gdb'>Launching GDB on the Host Computer</link>" |
769 | on the Host Computer</link> section covers how to create such a directory with | 770 | section covers how to create such a directory with |
770 | the Yocto Project and how to use the OProfileUI Settings dialog to specify the location. | 771 | the Yocto Project and how to use the OProfileUI Settings dialog to specify the location. |
771 | If you specify the directory, it will be used when the file checksums | 772 | If you specify the directory, it will be used when the file checksums |
772 | match those on the system you are profiling. | 773 | match those on the system you are profiling. |