summaryrefslogtreecommitdiffstats
path: root/package/google-breakpad/Config.in
diff options
context:
space:
mode:
Diffstat (limited to 'package/google-breakpad/Config.in')
-rw-r--r--package/google-breakpad/Config.in34
1 files changed, 34 insertions, 0 deletions
diff --git a/package/google-breakpad/Config.in b/package/google-breakpad/Config.in
new file mode 100644
index 0000000000..0ef10c51c1
--- /dev/null
+++ b/package/google-breakpad/Config.in
@@ -0,0 +1,34 @@
+config BR2_PACKAGE_GOOGLE_BREAKPAD_ARCH_SUPPORTS
+ bool
+ default y if BR2_i386 || BR2_x86_64 || BR2_arm || BR2_aarch64 || \
+ BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el
+
+config BR2_PACKAGE_GOOGLE_BREAKPAD
+ bool "google-breakpad"
+ depends on BR2_INSTALL_LIBSTDCPP
+ depends on BR2_TOOLCHAIN_USES_GLIBC
+ depends on BR2_PACKAGE_GOOGLE_BREAKPAD_ARCH_SUPPORTS
+ help
+ Google-Breakpad is a library and tool suite that allows you
+ to distribute an application to users with compiler-provided
+ debugging information removed, record crashes in compact
+ "minidump" files, send them back to your server, and produce
+ C and C++ stack traces from these minidumps. Breakpad can
+ also write minidumps on request for programs that have not
+ crashed.
+
+ You may want to set BR2_ENABLE_DEBUG, in order to get useful
+ results.
+
+ This target package installs a static library named
+ libbreakpad_client.a which should be linked into programs
+ willing to use Google Breakpad. A host variant of this
+ package is also available, and provides the different tools
+ needed to extract the debugging symbols from target
+ binaries.
+
+ http://code.google.com/p/google-breakpad/
+
+comment "google-breakpad requires an (e)glibc toolchain w/ C++ enabled"
+ depends on BR2_PACKAGE_GOOGLE_BREAKPAD_ARCH_SUPPORTS
+ depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_USES_GLIBC
OpenPOWER on IntegriCloud