8646ab97dc
In OOo times, there'd originally been efforts to allow building on Windows with MinGW. Later, in LO times, this has been shifted to an attempt of cross- compiling for Windows on Linux. That attempt can be considered abandoned, and the relevant code rotting. Due to this heritage, there are now three kinds of MinGW-specific code in LO: * Code from the original OOo native Windows effort that is no longer relevant for the LO cross-compilation effort, but has never been removed properly. * Code from the original OOo native Windows effort that is re-purposed for the LO cross-compilation effort. * Code that has been added specifially for the LO cross-compilation effort. All three kinds of code are removed. (An unrelated, remaining use of MinGW is for --enable-build-unowinreg, utilizing --with-mingw-cross-compiler, MINGWCXX, and MINGWSTRIP.) Change-Id: I49daad8669b4cbe49fa923050c4a4a6ff7dda568 Reviewed-on: https://gerrit.libreoffice.org/34127 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Google breakpad crash-reporting library https://chromium.googlesource.com/breakpad/breakpad When this is enabled and soffice.bin crashes, a "mini-dump" file is written as "instdir/crash/*.dmp". There is an UI to upload the mini-dump to a TDF server but of course that only makes sense if the server has symbols available that match the build, which is not the case if you have built LO yourself. If you want to get the backtrace from local mini-dump files: * with Visual Studio: 1. open the *.dmp file from the Visual Studio IDE File->Open->File 2. then click "Debug Native Only" * otherwise: 1. run "make symbols" to extract the debuginfo from the binaries 2. run "workdir/UnpackedTarball/breakpad/src/processor/minidump_stackwalk foo.dmp workdir/symbols"