Project tools

Project home

Membership

Announcements

Mailing lists

Documents & files

Source Code (svn)

Crossreference

Issue tracker

Tools (with Pages)

dmake

Tinderbox...

BuildBot results

Tinderbox

Search

This project All projects

Advanced search

Google search

How do I...

• Sitemap
• FAQ
• Get help?

start:

Tools Project

Build Environment

Using CVS to get the source

• Overview of OpenOffice.org codelines
• Descriptions of current CVS branches and their status
• Downloading the source from the Subversion repository (for current development heading 3.1 release)
  
• Downloading the source from CVS for releases until OOo 3.0
  
• CVS Modules or top level directories (in Subversion) available from OpenOffice.org.

Building the source

• Background Information for building OpenOffice.org
• Description of the Build Process The build requirements and instructions changed between OpenOffice.org 1.1.x, the recent OpenOffice.org versions and again for the current development versions:
  • Instructions for current OpenOffice.org development versions These build instructions are currently migrated to the OpenOffice.org wiki and are not finished yet. Please help improving them.
    Use the build instructions for the OpenOffice.org 2.x version from below as an additional reference.
  • Instructions for OpenOffice.org 2.0.x and 3.0.x
    
    • Linux
    • Solaris
    • Mac OS X (X11) or Mac OS X (Aqua)
    • Windows with Microsoft Visual C++ .NET2003 Compiler
      with Cygwin tools
      
    • Windows with Microsoft Visual C++ 2005 Express Compiler click here
• Build Environment description ( for OpenOffice 2.x/3.x series )
• Diagram of inter-project dependencies by C.P. Hennessy
• Tips for Troubleshooting the build.

Testing the code

• Tinderbox
  With many developers working on different platforms on the same codebase easiely leads to incompatibilities. A Tinderbox allows you to check the "buildability" of the current code and helps finding who broke the build. The Tinderbox provides the build logfiles so that it is easy to check what (and who) broke the build.

  If you have some CPU time to burn please consider running a tinderbox client. We need many tinderbox client machines that are doing builds!

  Tinderbox topics/issues can be discussed on the tinderbox@tools.openoffice.org mailing list.

Working on the code

• Coding Guidelines (.sxw)
• Usage Of Java Policies
• Checklist for C++ Interface Reviews (.sxw)
• DebuggingOpenOffice.org with Valgrind (.sxw)

OpenOffice.org Development with child workspaces (CWS):

• Overview
• Tools
  
• Policies
  
• Introduce a new module
  

Tools description

• Description of Autodoc (automatic documentation generation)
  ( for C++ and UNO-IDL;commandline syntax).

Performance and Profiling

Tools for performance measuring and related tasks.

• Performance Tuning and tools
• Profiling tools

Quality Assurance (QA)

QA is a separate project.

• Description of the Smoke Test
• Issue Writing Guidelines

Release Engineering

• Overview of Branches and Roadmap of OpenOffice.org releases and description of branches.
• Environment Information System is a Child Workspace (CWS) browsing interface
• File Naming Scheme

$Revision: 1.103 $ $Date: 2008/11/27 11:14:49 $