The cirros image was rebuilt against the 3.13.0-83 kernel, drivers e1000e, igbvf...
[packages/trusty/cirros-testvm.git] / cirros-testvm / src-cirros / buildroot-2015.05 / package / google-breakpad / Config.in
diff --git a/cirros-testvm/src-cirros/buildroot-2015.05/package/google-breakpad/Config.in b/cirros-testvm/src-cirros/buildroot-2015.05/package/google-breakpad/Config.in
new file mode 100644 (file)
index 0000000..a95bf63
--- /dev/null
@@ -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
+
+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