Line 56:

We find that sw depends on connectivity etc. These modules in turn depend on others creating a large complex dependancy tree.

We find that sw depends on connectivity etc. These modules in turn depend on others creating a large complex dependancy tree.

−

{{Template:Documentation/Note|For more information on modules, see:

+

{{Note|For more information on modules, see:

* [[Source code directories]]

* [[Source code directories]]

* [[Module Build Order]]

* [[Module Build Order]]

Line 69:

To avoid the need of a time-expensive complete re-build each time a change in the code is introduced, the developers are asked to introduce only ''binary compatible'' changes in the code unless the it is agreed with the project owner. This means that the changes made are of such a nature that no recompilation of further dependent modules become necessary (inserting a new, non-virtual method in a C++ class would be an example of such a binary compatible change). The office suite will then be re-compiled as a so-called ''respin build'' before the next 'master' s declared. A respin build obeys only weak dependencies, i.e. dependencies within a module. Using weak dependencies allows you to, for example, to modify a base library header file without needing to perform a full build. Since a respin build relies on binary compatible changes, modules can be build in parallel, and the build takes much less time (a few hours) in contrast to a full build.

To avoid the need of a time-expensive complete re-build each time a change in the code is introduced, the developers are asked to introduce only ''binary compatible'' changes in the code unless the it is agreed with the project owner. This means that the changes made are of such a nature that no recompilation of further dependent modules become necessary (inserting a new, non-virtual method in a C++ class would be an example of such a binary compatible change). The office suite will then be re-compiled as a so-called ''respin build'' before the next 'master' s declared. A respin build obeys only weak dependencies, i.e. dependencies within a module. Using weak dependencies allows you to, for example, to modify a base library header file without needing to perform a full build. Since a respin build relies on binary compatible changes, modules can be build in parallel, and the build takes much less time (a few hours) in contrast to a full build.

−

{{Template:Documentation/Note|By contrast, ''binary incompatible'' changes require a full build. For reasons of efficiency, this is allowed only with the approval of the project owner.}}

+

{{Note|By contrast, ''binary incompatible'' changes require a full build. For reasons of efficiency, this is allowed only with the approval of the project owner.}}

=== Snapshots / Milestone Builds ===

=== Snapshots / Milestone Builds ===

Line 89:

When you want to build a specific project, you only need the sources of the relevant SVN modules and the output tree <code>solver</code>. You do not need the entire source tree, though typically a developer will check out one of the branches and build it from scratch.

When you want to build a specific project, you only need the sources of the relevant SVN modules and the output tree <code>solver</code>. You do not need the entire source tree, though typically a developer will check out one of the branches and build it from scratch.

−

{{Template:Documentation/Note|For more information on the solenv and solver trees, see the [http://tools.openoffice.org/ Tools] project.}}

+

{{Note|For more information on the solenv and solver trees, see the [http://tools.openoffice.org/ Tools] project.}}

{{PDL1}}

{{PDL1}}

Documentation/Building Guide/Basic Concepts - Revision history

Sancho at 16:58, 25 August 2011

Admin: 1 версия