summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-10-01 07:45:33 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-02 17:41:29 +0100
commit93e7454bd77fa917019103ca6d42811dda8f4c3b (patch)
tree62b717956b12db26e532cdb727b3339326a085bf
parent70c657200f63cd3f25889a4da449391210e6e68a (diff)
downloadpoky-93e7454bd77fa917019103ca6d42811dda8f4c3b.tar.gz
documentation: dev-manual - Created list of option.
Better display of the SELECTED_OPTIMIZATION variable options when they appear as a list. Also, some punctuation added. (From yocto-docs rev: 73777e545f13eacca9ee466ba852bccd84c17f6f) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml17
1 files changed, 11 insertions, 6 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1025b0056b..8d053b3f53 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1880,11 +1880,11 @@
1880 </para> 1880 </para>
1881 1881
1882 <para> 1882 <para>
1883 Perhaps the easiest way is to have an 'sdk' image that corresponds to the plain 1883 Perhaps the easiest way is to have an SDK image that corresponds to the plain
1884 image installed on the device. 1884 image installed on the device.
1885 In the case of <filename>core-image-sato</filename>, 1885 In the case of <filename>core-image-sato</filename>,
1886 <filename>core-image-sato-sdk</filename> would contain suitable symbols. 1886 <filename>core-image-sato-sdk</filename> would contain suitable symbols.
1887 Because the sdk images already have the debugging symbols installed, it is just a 1887 Because the SDK images already have the debugging symbols installed, it is just a
1888 question of expanding the archive to some location and then informing GDB. 1888 question of expanding the archive to some location and then informing GDB.
1889 </para> 1889 </para>
1890 1890
@@ -2015,13 +2015,18 @@
2015 <filename>-fno-omit-framepointer</filename> flag. 2015 <filename>-fno-omit-framepointer</filename> flag.
2016 You can achieve this by setting the 2016 You can achieve this by setting the
2017 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-SELECTED_OPTIMIZATION'>SELECTED_OPTIMIZATION</ulink></filename> 2017 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-SELECTED_OPTIMIZATION'>SELECTED_OPTIMIZATION</ulink></filename>
2018 variable to 2018 variable with the following options:
2019 <filename>-fexpensive-optimizations -fno-omit-framepointer -frename-registers -O2</filename>. 2019 <literallayout class='monospaced'>
2020 -fexpensive-optimizations
2021 -fno-omit-framepointer
2022 -frename-registers
2023 -O2
2024 </literallayout>
2020 You can also achieve it by setting the 2025 You can also achieve it by setting the
2021 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DEBUG_BUILD'>DEBUG_BUILD</ulink></filename> 2026 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DEBUG_BUILD'>DEBUG_BUILD</ulink></filename>
2022 variable to "1" in the <filename>local.conf</filename> configuration file. 2027 variable to "1" in the <filename>local.conf</filename> configuration file.
2023 If you use the <filename>DEBUG_BUILD</filename> variable you will also add extra debug information 2028 If you use the <filename>DEBUG_BUILD</filename> variable,
2024 that can make the debug packages large. 2029 you will also add extra debug information that can make the debug packages large.
2025 </para> 2030 </para>
2026 2031
2027 <section id="platdev-oprofile-target"> 2032 <section id="platdev-oprofile-target">