Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | crashdump conditionals | ||
---|---|---|---|
Product: | Build Tools | Reporter: | mmeeks <mmeeks> |
Component: | code | Assignee: | Martin Hollmichel <nesshof> |
Status: | CLOSED FIXED | QA Contact: | issues@tools <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, khendricks, pavel, quetschke |
Version: | OOo 1.1 RC2 | ||
Target Milestone: | OOo 1.1 RC | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
mmeeks
2003-07-28 18:50:53 UTC
crash dump is a vq speciality. Well, up to now I didn't do anything with the installer. Martin or Kevin would be good to ask, but I'm sure ause can also approve in this area. Kevin ? I used something similar in the past because our build systems do not contain pkg-config thus crashrep can not be build. Currently even if you build without crashrep, your installation process wants to install its files and issues warning to user. This applies only to interactive installer. ./install --prefix=/tmp will fail. mh->is: please take a look on this. This is already fixed with bug #17635, which will be included in ooo11rc3. It was an error, that the crahsrep-files were still included into the files.scp. Instead I created before the new subdirectory scp/source/crashrep, where I defined the files crashrep_static.scp (with the crash_report_with_gtk.bin) and crashrep_dynamic.scp (with the other crashrep files from files.scp). files.scp will not contain any crashrep-files in the future. In scp/util/makefile.mk you can see, at which conditions the crashrep files are included in the OpenOffice.org product: .IF "$(ENABLE_CRASHDUMP)" != "" || "$(PRODUCT)" != "FULL" SCP1FILES += \ crashrep_dynamic.par .ENDIF .IF "$(GUI)"=="UNX" .IF "$(ENABLE_CRASHDUMP)" == "STATIC" || "$(PRODUCT)" != "FULL" SCP1FILES += \ crashrep_static.par .ENDIF .ENDIF Therefore this bug is obviously already fixed. If everything works fine now, you can close this bug. fixed in RC4; thanks. mark as verified. close issue. |