Difference between revisions of "BuildSpeedup"
From Apache OpenOffice Wiki
(→How to report build profile logs) |
(→How to report build profile logs) |
||
| Line 5: | Line 5: | ||
# Apply the latest patch from http://www.openoffice.org/issues/show_bug.cgi?id=60948 to your source tree | # Apply the latest patch from http://www.openoffice.org/issues/show_bug.cgi?id=60948 to your source tree | ||
# in the dmake directory type "make clean; make". In the root directory type "./bootstrap" | # in the dmake directory type "make clean; make". In the root directory type "./bootstrap" | ||
| − | # When building redirect stderr and stdout to the logfile. In tcsh "build --all |& tee >myconfigdesc_build.log" will do the trick. You can alternatively use cat instead of tee to speed up the build slightly | + | # When building redirect stderr and stdout to the logfile. In tcsh "build --all |& tee >myconfigdesc_build.log" will do the trick. You can alternatively use cat instead of tee to speed up the build slightly. You need to build in a single go. |
| + | # Check that the log contains markers like "s target 1234 foo.obj". If not, then report | ||
# Compress the log with zip/gz | # Compress the log with zip/gz | ||
# When you send in your log to mailto:kai@shorthike.com please provide a short description of the build type: | # When you send in your log to mailto:kai@shorthike.com please provide a short description of the build type: | ||
#* Important configure options (like --with-lang=?) | #* Important configure options (like --with-lang=?) | ||
#* OS/compiler/generic hardware description | #* OS/compiler/generic hardware description | ||
| − | #* | + | #* Processor/core count. -P options used for build (important!) |
| + | #* No-change, partial or full build (we are especially looking for full builds) | ||
#* External accelerators like ccache | #* External accelerators like ccache | ||
Revision as of 15:59, 25 January 2006
How to report build profile logs
Thank you for sending in a build profile log. The more logs we have, the easier it is to focus our effort correctly. Here are the steps to producing a build log:
- Apply the latest patch from http://www.openoffice.org/issues/show_bug.cgi?id=60948 to your source tree
- in the dmake directory type "make clean; make". In the root directory type "./bootstrap"
- When building redirect stderr and stdout to the logfile. In tcsh "build --all |& tee >myconfigdesc_build.log" will do the trick. You can alternatively use cat instead of tee to speed up the build slightly. You need to build in a single go.
- Check that the log contains markers like "s target 1234 foo.obj". If not, then report
- Compress the log with zip/gz
- When you send in your log to mailto:kai@shorthike.com please provide a short description of the build type:
- Important configure options (like --with-lang=?)
- OS/compiler/generic hardware description
- Processor/core count. -P options used for build (important!)
- No-change, partial or full build (we are especially looking for full builds)
- External accelerators like ccache
Thank you again for contributing! --KaiB 16:25, 25 January 2006 (CET)
Notes
This is a workarea for ideas and notes regarding the speeding up of the build process. --KaiB 12:50, 16 January 2006 (CET)
Notes:
- Newest dmake version: cws_src680_dmake43p01)
- solenv/inc define global targets
- potential modules: KaiB: transex3, tools, svx, binfilter - small to huge :)
- helpcontent2 --with-lang=ALL (there are open issues on this already)
- batched compiles
- Interix instead of cygwin
- dependency generation
transex3
Started by tackling this small module. Initial full compile time was 137 sec.
