176
edits
Mobile/debug on maemo: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 13: | Line 13: | ||
First thing we need to do before debugging some app under maemo is choosing our preferred maemo distribution and SDK. Normally, one should always choose the latest stable distribution, but sometimes, various tools may be unavailable or in an unstable state. That was the case when first writing this document : the various profiling tools provided with the diablo distribution (e.g. oprofile) were very unstable and and not-so-compatible with the associated binutils tools from the associated scratchbox SDK. that's why the whole step-by-step process is presented for maemo 4.0 chinook and maemo 4.1.X diablo. | First thing we need to do before debugging some app under maemo is choosing our preferred maemo distribution and SDK. Normally, one should always choose the latest stable distribution, but sometimes, various tools may be unavailable or in an unstable state. That was the case when first writing this document : the various profiling tools provided with the diablo distribution (e.g. oprofile) were very unstable and and not-so-compatible with the associated binutils tools from the associated scratchbox SDK. that's why the whole step-by-step process is presented for maemo 4.0 chinook and maemo 4.1.X diablo. | ||
= | =INSTALL AND SETUP= | ||
The various steps presented hereafter are based upon the assumption that you have installed the maemo 4.0.1 scratchbox SDK with an additional target using the arm2007q3 toolchain, as described [[Mobile/Build/cs2007q3]] | |||
==diablo distribution== | ==diablo distribution== | ||
=DEBUG AND PROFILE= | =DEBUG AND PROFILE= | ||