README: Document dependencies for backtrace generation
libcamera now has the ability to use libdw and libunwind to generate backtraces, in addition to the glibc backtrace() function. libdw provides the most detailed output and is highly recommended, but is limited to parsing backtraces, it doesn't support capturing them. libunwind and backtrace() provide both features. If backtrace() is available, libunwind will not bring any improvement. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Paul Elder <paul.elder@ideasonboard.com> Reviewed-by: Umang Jain <umang.jain@ideasonboard.com>
This commit is contained in:
parent
5b39dc6d9b
commit
78e94065fc
1 changed files with 8 additions and 0 deletions
|
@ -63,6 +63,14 @@ for the libcamera core: [required]
|
|||
for IPA module signing: [required]
|
||||
libgnutls28-dev openssl
|
||||
|
||||
for improved debugging: [optional]
|
||||
libdw-dev libunwind-dev
|
||||
|
||||
libdw and libunwind provide backtraces to help debugging assertion
|
||||
failures. Their functions overlap, libdw provides the most detailed
|
||||
information, and libunwind is not needed if both libdw and the glibc
|
||||
backtrace() function are available.
|
||||
|
||||
for the Raspberry Pi IPA: [optional]
|
||||
libboost-dev
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue