Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Build support instructions. | ||
---|---|---|---|
Product: | Build Tools | Reporter: | issues@www <issues> |
Component: | code | Assignee: | Martin Hollmichel <nesshof> |
Status: | CLOSED FIXED | QA Contact: | issues@tools <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, issues, jens-heiner.rechtien |
Version: | 605 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
issues@www
2000-10-21 02:25:06 UTC
Yes, we are aware of this problem. We continue working on documentation. I have added a top-level summary of the full Linux build to the build documentation at http://www.openoffice.org/dev_docs/source/build.html (see Overview of Performing a Full Build). Does this resolve the issue? If not, please clarify the problem further. Eugene I think, it's still not simple enough, the goal should be to type configure and all other needed steps should be described by configure error messages. There are some items which still complicated: - search for the STL - Library - search for the JDK - search the Compiler (Windows) - simplify the bootstrap process we're working here in Hamburg for - move of binaries from solenv to some other place - introduce automake/autoconf process for dmake (makedepn, ...) - seperation of the UDK from the openoffice.org build -> reducing of prerequistes - implementation of deliver, mkout in perl changing QA contact from bugs@ to issues@ configure script and doucumentation have been updated. set up of the initial build environment is now easier. Verified - there are several build guides available and most obsure build problems are gone in 643+ builds. closing |