Build Environment Effort/ToDo
From Apache OpenOffice Wiki
- create runnable instance of OOo in solver
- solver becomes incrementally filled office tree
- libraries can be executed from solver
- UNO services are registered from text files
- configurable place for solver
- build should not modify source tree
- configurable place for output directories
- split build, repositories and solver
- tools, URE, localization, help content, non-code parts, extensions (binfilter?)
- platform independent help content
- remove unnecessary dependencies (e.g. xmlhelp from svtools, linguistic from sfx2 etc.)
- evaluate integration of OOo SDK and OOo build environments
- find a way to move out localization completely (localize only strings, not resources)
- which resource types can be localized
- which of them do we localize
- find replacements for all non-string types
- evaluate po files for OOo
- get rid of common output trees: They cause way too much hassle with bots etc. and arent worth the trouble
- make pre-build parts of the solver available on a module-by-module basis