From b590fab4a1e483657815f31ede17d09fea483b14 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 6 Apr 2016 10:31:54 -0700 Subject: dev-manual, ref-manual, sdk-manual: Removing oprofile references. Fixes [YOCTO #9264] I handled the occurrences of "oprofile" and "tools-profile" throughout as I could. They are not all done yet. These in this commit have been removed. (From yocto-docs rev: d76e264ea210846ad8080134bacd56462ba69d24) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 13 +++++------ documentation/ref-manual/ref-variables.xml | 3 --- documentation/sdk-manual/sdk-intro.xml | 11 +-------- documentation/sdk-manual/sdk-using.xml | 26 ---------------------- 4 files changed, 7 insertions(+), 46 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 5e6dafd5b6..372d7b788f 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -8179,21 +8179,20 @@ This line pulls in the listed include file that contains numerous lines of exactly that form: + #SRCREV_pn-opkg-native ?= "${AUTOREV}" + #SRCREV_pn-opkg-sdk ?= "${AUTOREV}" + #SRCREV_pn-opkg ?= "${AUTOREV}" + #SRCREV_pn-opkg-utils-naitve ?= "${AUTOREV}" + #SRCREV_pn-opkg-utils ?= "${AUTOREV}" SRCREV_pn-gconf-dbus ?= "${AUTOREV}" SRCREV_pn-matchbox-common ?= "${AUTOREV}" SRCREV_pn-matchbox-config-gtk ?= "${AUTOREV}" SRCREV_pn-matchbox-desktop ?= "${AUTOREV}" SRCREV_pn-matchbox-keyboard ?= "${AUTOREV}" - SRCREV_pn-matchbox-panel ?= "${AUTOREV}" SRCREV_pn-matchbox-panel-2 ?= "${AUTOREV}" SRCREV_pn-matchbox-themes-extra ?= "${AUTOREV}" SRCREV_pn-matchbox-terminal ?= "${AUTOREV}" - SRCREV_pn-matchbox-wm ?= "${AUTOREV}" - SRCREV_pn-matchbox-wm-2 ?= "${AUTOREV}" - SRCREV_pn-settings-daemon ?= "${AUTOREV}" - SRCREV_pn-screenshot ?= "${AUTOREV}" - SRCREV_pn-libfakekey ?= "${AUTOREV}" - SRCREV_pn-oprofileui ?= "${AUTOREV}" + SRCREV_pn-matchbox-wm ?= "${AUTOREV}" . . . . diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index fd15dff9a1..b26f6f73f7 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -3819,9 +3819,6 @@ "tools-debug" - Adds debugging tools such as gdb and strace. -"tools-profile" - Adds profiling tools such as oprofile, - exmap, lttng and valgrind (x86 only). - "tools-sdk" - Adds development tools such as gcc, make, pkgconfig and so forth. diff --git a/documentation/sdk-manual/sdk-intro.xml b/documentation/sdk-manual/sdk-intro.xml index ae27562037..88ae77831c 100644 --- a/documentation/sdk-manual/sdk-intro.xml +++ b/documentation/sdk-manual/sdk-intro.xml @@ -203,7 +203,7 @@ User-space tools are available as part of the SDK development process and can be helpful. - The tools include LatencyTOP, PowerTOP, OProfile, Perf, SystemTap, + The tools include LatencyTOP, PowerTOP, Perf, SystemTap, and Lttng-ust. These tools are common development tools for the Linux platform. @@ -216,15 +216,6 @@ determine what software is using the most power. You can find out more about PowerTOP at . - OProfile: A system-wide - profiler for Linux systems that is capable of profiling all - running code at low overhead. - You can find out more about OProfile at - . - For examples on how to setup and use this tool, see the - "OProfile" - section in the Yocto Project Profiling and Tracing Manual. - Perf: Performance counters for Linux used to keep track of certain types of hardware and software events. diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index 9a942d1c1c..618e57030f 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml @@ -1341,32 +1341,6 @@ Here are some specifics about the remote tools: - OProfile: - Selecting this tool causes the - oprofile-server on the remote - target to launch on the local host machine. - The oprofile-viewer must be - installed on the local host machine and the - oprofile-server must be installed - on the remote target, respectively, in order to use. - You must compile and install the - oprofile-viewer from the source - code on your local host machine. - Furthermore, in order to convert the target's sample - format data into a form that the host can use, you must - have OProfile version 0.9.4 or greater installed on the - host. - You can locate both the viewer and server from - . - You can also find more information on setting up and - using this tool in the - "oprofile" - section of the Yocto Project Profiling and Tracing - Manual. - The oprofile-server is - installed by default on the - core-image-sato-sdk image. - Lttng2.0 trace import: Selecting this tool transfers the remote target's Lttng tracing data back to the -- cgit v1.2.3-54-g00ecf