|author||Luboš Luňák <email@example.com>||2019-04-17 19:13:30 +0200|
|committer||Jan Holesovsky <firstname.lastname@example.org>||2019-06-05 22:19:35 +0200|
update references about selective debuginfo in android/README
The second case is very likely mistaken though. Change-Id: I6bfc55800a6b26ce0ae6d3645e4179dc5f683205
1 files changed, 7 insertions, 3 deletions
diff --git a/android/README b/android/README
index 21ede90e94e4..4ebfab6594ff 100644
@@ -200,8 +200,8 @@ Debugging
First of all, you need to configure the build with --enable-debug or
---enable-dbgutil. You may want to provide --enable-selective-debuginfo too,
-like --enable-selective-debuginfo="sw/" or so, in order to fit into the memory
+--enable-dbgutil. You may want to provide --enable-symbols to limit debuginfo,
+like --enable-symbols="sw/" or so, in order to fit into the memory
Building with all symbols is also possible but the linking is currently
@@ -291,7 +291,11 @@ SAL_INFO from cppuhelper/source/shlib.cxx in logcat and therefore identify
what services are missing. To do so, you may want add the following
when configuring the build.
- --enable-selective-debuginfo="cppuhelper/ sal/"
+ --enable-symbols="cppuhelper/ sal/"
+[TODO: This is nonsense. --enable-symbols enables the -g option, not SAL_INFO.
+Perhaps this was a misunderstanding of meaning of --enable-selective-debuginfo,
+the old name for the option.]
Which services are combined in the android lib is determined by