Difference between revisions of "Non Product Build"
| Line 3: | Line 3: | ||
Currently, Non-Product Builds are probably rarely used outside the Hamburg development team (which might be because the facilities are widely unknown). | Currently, Non-Product Builds are probably rarely used outside the Hamburg development team (which might be because the facilities are widely unknown). | ||
| − | Non-Product Builds are created using a [[Debugging#How_do_I_use_the_debug_console_.3F|special configure switch]], namely <code>--enable-dbgutil</code>. | + | Non-Product Builds are created using a [[Debugging#How_do_I_use_the_debug_console_.3F|special configure switch]], namely <code>--enable-dbgutil</code>. Note that you cannot mix libraries from Product and Non-Product builds. |
The most visible feature of Non-Product Builds are so-called assertions - Basically message boxes popping up, and saying that something went not the way the developer expected it to go. Such assertions are considered bugs, and as such should be [http://qa.openoffice.org/issue_handling/pre_submission.html reported in IssueZilla], with the summary starting with "ASSERT:" or "ERROR:" (since ERROR: is used by most of the assertion message boxes themself). | The most visible feature of Non-Product Builds are so-called assertions - Basically message boxes popping up, and saying that something went not the way the developer expected it to go. Such assertions are considered bugs, and as such should be [http://qa.openoffice.org/issue_handling/pre_submission.html reported in IssueZilla], with the summary starting with "ASSERT:" or "ERROR:" (since ERROR: is used by most of the assertion message boxes themself). | ||
Revision as of 10:04, 1 December 2005
A so-called Non-Product Build of OpenOffice.org is one that contains a lot of additional diagnostics and debug code, which is available in this special mode only. Such a build is usually larger (and slower :) than an ordinary Product Build (which basically means: every build you ever downloaded from OpenOffice.org), but is very useful for developers.
Currently, Non-Product Builds are probably rarely used outside the Hamburg development team (which might be because the facilities are widely unknown).
Non-Product Builds are created using a special configure switch, namely --enable-dbgutil. Note that you cannot mix libraries from Product and Non-Product builds.
The most visible feature of Non-Product Builds are so-called assertions - Basically message boxes popping up, and saying that something went not the way the developer expected it to go. Such assertions are considered bugs, and as such should be reported in IssueZilla, with the summary starting with "ASSERT:" or "ERROR:" (since ERROR: is used by most of the assertion message boxes themself).
