Apache OpenOffice Wiki - User contributions [en]

ReleaseStatus Minutes

2009-10-25T15:43:50Z

Maveric: /* Agenda for next meeting */

The various functional groups of OpenOffice (QA, Development, User Exp., Documentation, Release Engineering, Marketing, Localization, etc.) are represented here.
On every Monday 3pm German time ([http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=2&year=2008&hour=15&min=0&sec=0&p1=307 see here to convert to other time zones]) this meeting will track the status of the upcoming releases.

The members of this meeting review critical issues and deliverables for the releases and agree on the appropriate handling of those issues.
They coordinate the actual release schedule.

== Agenda for next meeting ==

* Meta-Issues: [http://qa.openoffice.org/issues/show_bug.cgi?id=104695 Issue 104695] for the Beta version and [http://qa.openoffice.org/issues/show_bug.cgi?id=99999 Issue 99999] for final

* Add your issue ID and description here:
** [http://qa.openoffice.org/issues/show_bug.cgi?id=106261 Issue 106261] No Sound in Impress under Mac OS X 10.6.x When using sound effects or sound files on animations, slide transisitions or via Insert Movie and Sound you hear nothing in preview and in the actual presentation.
** [http://qa.openoffice.org/issues/show_bug.cgi?id=104421 Issue 104421] Win build under Vista 64 bit and possible under Win 7 64 bit not installable (maybe in special circumstances) - fixed in installer11
** [http://qa.openoffice.org/issues/show_bug.cgi?id=86464 Issue 86464] Help: Index tab page listbox is empty, Help page is blank
** There are still more than 160 issues open which are targetted to 3.2, see [http://www.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&resolution=-blank-&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=&short_desc_type=fulltext&long_desc=&long_desc_type=fulltext&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query this list]. They should be looked after if anything has been missed or should be retargeted.

* Review of issues for OOo 3.2.0 if any
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]

== 2009-10-19 ==
Participants: Rene Engelhard, Stefan Baltzer, Chris Cheney, Oliver Craemer, Joost Andrae, Ruediger Timm, Uwe Luebbers, Mechtilde Stehmann, Olaf Felka, Marc Neumann, Volker Merschmann, Pavel Janik, Helge Delfs, Jens-Heiner Rechtien, Uwe Luebbers, Kai Ahrens, Shinji Enoki,

=== Review of issues for OOo 3.2.0 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]

* [http://qa.openoffice.org/issues/show_bug.cgi?id=86464 issue 86464] is about missing meta data. Volker Merschmann mentioned that this causes that the help page for the start center is not displayed. Stefan Baltzer answered it is not exactly a regression, but correct help in the very start center is a good thing. It is planned to add that one to CWS tl75 ->Issue has been accepted as show stopper issue
* [http://qa.openoffice.org/issues/show_bug.cgi?id=104421 issue 104421]. Issue has been accepted as show stopper issue

=== Other items ===
* There was a discussion wether it was good or not to upload OOO320_m2 developer snapshot build as 3.2 Beta (details to be read within the IRC log)
=== RE duties this week ===
DEV300_m62 by Kurt Zenker (kz)<br>
DEV300_m63 by Vladimir Glazunov (vg)<br>

=== Upload duties this week ===
Uploads by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-10-19_IRC_log ReleaseStatus Minutes 2009-10-19 IRC log]

== 2009-10-12 ==
Participants: Rene Engelhard, Fridrich Strba, Stefan Baltzer, Chris Cheney, Oliver Craemer, Joost Andrae, Ruediger Timm, Uwe Luebbers, Mechtilde Stehmann, Olaf Felka, Marc Neumann, Volker Merschmann, Pavel Janik, Martin Hollmichel, Marcus Lange

=== Review of issues for OOo 3.2.0 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]

* [http://qa.openoffice.org/issues/show_bug.cgi?id=99971 issue 99971] has been added to the stopper list because development found an easy way to fix it

=== Other items ===
* m2 should be the basis for beta
* m2 build should be started on 2009-10-13

=== RE duties this week ===
DEV300_m62 by Kurt Zenker (kz)<br>
OOO320_m2 by Oliver Bolte (obo)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-10-12_IRC_log ReleaseStatus Minutes 2009-10-12 IRC log]

== 2009-10-05 ==
Participants: Rene Engelhard, Fridrich Strba, Stefan Baltzer, Chris Cheney, Oliver Craemer, Joost Andrae, Ruediger Timm, Martin Hollmichel, Marcus Lange, Kai Ahrens, Uwe Luebbers, Jens-Heiner Rechtien, Mechtilde Stehmann, Shinji Enoki, Olaf Felka, Rafaella Braconi, Marc Neumann, Martin Damboldt

=== Review of issues for OOo 3.2.0 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]

* Martin Damboldt mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=105266 issue 105266]. The issue should be solved within the upcoming build.
* Lutz Hoeger announced within a blog update that the new ODF icons will not become part of the 3.2 release but the integration will be shifted to the 3.3 release
* We have much more strings for 3.2 release than expected. We are facing a word count of 46.000. As a result Rafaella requested two additional weeks for translation. This will bring the OOo 3.2 announce date to Tuesday, 15 December 2009. As a result Rafaella will communicate the two additional weeks for l10n. Martin will adjust the schedule in Wiki accordingly (incl. a new Beta release date)
* Mechtilde asked Rafaella if there is translation to be done for the presenter console. Rafaella answered usually the help of an extension is not included in the core help. As extensions are not necessarily released together with an OpenOffice.org release they follow a different release process (to be defined). Mechtilde asked that we need a discussion about the release process of the Extensions which are published by Sun. Martin confirmed.
As information Rafaella pubilshed a [http://wiki.services.openoffice.org/wiki/Extensions_Overview link] to an overview of where to find the resources for translation of Sun's extensions. Martin asked that he want's to have the english help in this (3.2.0) release and that no translation is required for now.
* Uwe Luebbers asked about [http://qa.openoffice.org/issues/show_bug.cgi?id=102464 issue 102464]. This issue has been accepted as blocker
* Uwe Luebbers asked about [http://qa.openoffice.org/issues/show_bug.cgi?id=99971 isssue 99971]. This issue has been rejected as blocker.

=== Other items ===
* Martin mentioned that we can start the OOO320_m1 round now. Martin said "As already mentioned there are some Beta blockers open, those I would like to see in OOO320_m2 which would become the Beta than.". Open are for example CWS fwk121 and it's successor fwk122 where stoppers are in. Impressnotes03 will already go into the OOO320_m1.

=== RE duties this week ===
DEV300_m61 by Vladimir Glazunov (vg)<br>
OOO320_m1 by Ivo Hinkelmann (ihi)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-10-05_IRC_log ReleaseStatus Minutes 2009-10-05 IRC log]

== 2009-09-28 ==
Participants: Rene Engelhard, Fridrich Strba, Stefan Baltzer, Chris Cheney, Oliver Craemer, Joost Andrae, Ruediger Timm, Martin Hollmichel, Marcus Lange, Sophie Gautier, Volker Merschmann, Kai Ahrens, Uwe Luebbers, Jens-Heiner Rechtien, Mechtilde Stehmann

=== Review of issues for OOo 3.2.0 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]

* Kai Ahrens mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=105185 issue 105185]. Martin asked him if this would include more l10n. Kai answered the word count is low and he suggests to do translation after the main translation process

=== Other items ===
* Martin Hollmichel mentioned we will collect some more feedback and will do a OOO320_m1 later this week
* OOO320_m2 is planned to be the build used for a beta
* Martin mentioned there's a [http://ux.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=4189 request] by Lutz Hoeger regarding icon updates. The proposal has been accepted by the majority. Martin will nominate this for OOO320_m1.

=== RE duties this week ===
DEV300_m61 by Vladimir Glazunov (vg)<br>
OOO320_m1 by Kurt Zenker (kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-09-28_IRC_log ReleaseStatus Minutes 2009-09-28 IRC log]

== 2009-09-21 ==
Participants: Rene Engelhard, Fridrich Strba, Stefan Baltzer, Chris Cheney, Oliver Craemer, Pavel Janik, Joost Andrae, Ruediger Timm, Martin Hollmichel, Martin Damboldt, Marcus Lange, Sophie Gautier, André Schnabel, Volker Merschmann, Kai Ahrens, Uwe Luebbers, Lutz Hoeger, David Tardon

=== Review of issues for OOo 3.2.0 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]

* Marcus Lange noted [http://qa.openoffice.org/issues/show_bug.cgi?id=103543 issue 103543]. Mikhail Voitenko is currently working on this but a fix is not yet available.
* Stefan Baltzer mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=105148 issue 105148]. A bugfix is available. Martin told Stefan that he would take the fix as master fix
* Stefan Baltzer mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=105149 issue 105149]

=== Other items ===
* Martin Damboldt mentioned that when looking at the 3.2 shedule, today is branch date for the 3.2 release. Build DEV300_m60 is currently in progress. OOO320_m0 will be created right after DEV300_m60 is finished. The build thereafter (OOO320_m1) will be promoted as "3.2 Beta".
* André Schnabel asked if it would be possible to shift the lateminute change of the iconset. Martin Damboldt asked André Schnabel and Lutz Hoeger to follow-up the discussion at [mailto:discuss@ux.openoffice.org discuss@ux.openoffice.org].

=== RE duties this week ===
DEV300_m60 by Ivo Hinkelmann (ihi)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-09-21_IRC_log ReleaseStatus Minutes 2009-09-21 IRC log]

== 2009-09-14 ==
Participants: Rene Engelhard, Shinji Enoki, Mechtilde Stehmann, Fridrich Strba, Stefan Baltzer, Chris Cheney, Christian Lippka, Oliver Craemer, Pavel Janik, Thorsten Ziehm, Joost Andrae, Ruediger Timm, Andreas Bartels, Kai Ahrens

=== Review of issues for OOo 3.2.0 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]
* Joost mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=105035 issue 105035]. Issue has been accepted for 3.2.
* René mentioned [http://www.openoffice.org/issues/show_bug.cgi?id=105016 issue 105016]. Issue has been accepted for 3.2.

=== Other items ===
* Martin mentioned the discussion about a possible Alpha/Beta schedule. The goal was to follow up on this topic in a separate meeting.. Martin Damboldt will follow up with this together with Martin Hollmichel.
* René asked if all nominated CWS will get integrated into DEV300_m59. Martin answered that m59 will be closed today to get the next milestone as soon as possible. The plan is to start the integration for the next and last round before the branch-off end of this week
* René mentioned CWS boost134 and asked if it will get integrated (it was nominated on Sept. 8th). Ruediger Timm asked Frank Schoenheit regarding a possible dependency of the MySQL connector. Frank denied on this. Martin Damboldt mentioned it sounds not that important to integrate boost134 now or at the end of this week.
* Ruediger sees the branch-off date on risk. Martin Damboldt will take an eye on this.

=== RE duties this week ===
DEV300_m59 by Kurt Zenker (kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-09-14_IRC_log ReleaseStatus Minutes 2009-09-14 IRC log]

== 2009-09-07 ==
Participants: Rene Engelhard, Shinji Enoki, Olaf Felka, Martin Hollmichel, Mechtilde Stehmann, Ruediger Timm, Fridrich Strba, Simon Wilper, Stefan Baltzer, Volker Merschmann, Kai Ahrens, Andreas Bartel

=== Discussion on 3.2.0 issues ===
* [http://qa.openoffice.org/issues/show_bug.cgi?id=103543 Issue 103543] (Help Viewer, Contents page: Links don't show Help pages) has been accepted.

=== Other items ===
* Volker has made a proposal for the timeline on releases@ooo, no decision yet:
** 2009-09-21 Branch off date (UI and feature freeze)
** 2009-end of September Alpha version, english only, langpacks would lack translation of new features
** 2009-mid/end of November Beta version, similar to the former RC1
** 2009-start/mid of December Final release of OOo 3.2
* Ongoing discussion about the correct wording and point of time for a 3.2.0 beta version

=== Review of issues for OOo 3.2.0 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=104695 Dependency list for 3.2 beta issues] <br>
[http://www.openoffice.org/issues/showdependencytree.cgi?id=99999 Dependency list for 3.2 final issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.2]

=== RE duties this week ===
DEV300_m58 by Oliver Bolte (obo)

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-09-07_IRC_log ReleaseStatus Minutes 2009-09-07 IRC log]

== 2009-08-31 ==
Participants: Rene Engelhard, Shinji Enoki, Olaf Felka, Martin Hollmichel, Pavel Janik, Marcus Lange, Mechtilde Stehmann, Ruediger Timm, Chris Cheney, Fridrich Strba, Joost Andrae, Martin Damboldt, Marc Neumann, Oliver Craemer, Simon Wilper, Stefan Baltzer, Volker Merschmann, Kai Ahrens, Andreas Bartel

=== Discussion on 2.4.3 stopper issues ===
* no stopper issues have been raised for RC2 but there are issues regarding JRE6u16 on Win98. As the issue is more complex Martin Damboldt will communicate the outcome regarding JRE 1.6 vs. JRE 1.5 on the releases list.

=== Discussion on 3.2.0 issues ===
* only three weeks left until branch date
* Mechtilde asked when translation needs to be finished for 3.2. Regarding [http://wiki.services.openoffice.org/wiki/OOoRelease32 3.2 Release map] translation delivery is on October 16th.
* a so called "Beta" will be provided as OOo-Dev build directly after the branch, naming will be discussed again

=== Other items ===
* The 3.1.1 release is done.

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]

=== RE duties this week ===
DEV300_m57 by Vladimir Glazunov (vg)

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-08-31_IRC_log ReleaseStatus Minutes 2009-08-31 IRC log]

== 2009-08-24 ==
Participants: Kai Ahrens, Antreas Bartel, Rene Engelhard, Enoki, Olaf Felka, Martin Hollmichel, Pavel Janik, Volker Merschmann, Marcus Lange, Uwe Luebbers, Mechtilde Stehmann, Ruediger Timm

=== Discussion on 3.1.1 stopper issues ===
* Mechtilde had problems to open the Extension Manager with Linux 64-bit (deb), but it would be also a false alarm.
* Until now it looks good on Win, Linux 32-bit, Linux-64 bit (rpm), Mac OS X Intel, Solaris x86 and Solaris Sparc. Linux 64-bit (deb) needs a bit more time for testing as they weren't uploaded in the first run.

=== Discussion on 2.4.3 stopper issues ===
* none

=== Discussion on 3.2.0 issues ===
* none

=== Other items ===
* Martin Hollmichel just reminded for the branch off day on September 21st.

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]

=== RE duties this week ===
DEV300_m56 by Ivo Hinkelmann (ihi) <br>
DEV300_m57 by Vladimir Glazunov (vg)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-08-24_IRC_log ReleaseStatus Minutes 2009-08-24 IRC log]

== 2009-08-17 ==
Participants: Kai Ahrens, Martin Damboldt, Rene Engelhard, Enoki, Olaf Felka, Sophie Gautier, Martin Hollmichel, Marcus Lange, Uwe Luebbers, Jens-Heiner Rechtien, Mechtilde Stehmann, Ruediger Timm

=== Discussion on 3.1.1 stopper issues ===
* [http://www.openoffice.org/issues/show_bug.cgi?id=104146 issue 104146] has been accepted
* It's planned to start RC2 on Tuesday evening, so it hopefully gets uploaded before the weekend.

=== Discussion on 2.4.3 stopper issues ===
* [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=OOO310%2Fsb114 CWS sb115] (new libxml2) has been accepted
* [http://www.openoffice.org/issues/show_bug.cgi?id=99672 issue 99672] has been accepted
* [http://www.openoffice.org/issues/show_bug.cgi?id=104277 issue 104277] has been accepted
* [http://www.openoffice.org/issues/show_bug.cgi?id=104263 issue 104263] was rejected, it is already fixed in 3.1.1 and there is no reason to fix this for 2.4.3, too
* 2.4.3 release date needs to be shifted, new planned date is September, 01st

=== Discussion on 3.2.0 issues ===
* [http://www.openoffice.org/issues/show_bug.cgi?id=104271 issue 104271] Martin D. will ask the developer for a statement and update the issue

=== Other items ===
* none

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]

=== RE duties this week ===
OOO310_m19 by Kurt Zenker (kz) <br>
OOH680_m21 by Kurt Zenker (kz) <br>
DEV300_m56 by Ivo Hinkelmann (ihi)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-08-17_IRC_log ReleaseStatus Minutes 2009-08-17 IRC log]

== 2009-08-10 ==
Participants: Kai Ahrens, Martin Damboldt, Rene Engelhard, Olaf Felka, Martin Hollmichel, Marcus Lange, Uwe Luebbers, Sophie Gautier, Mechtilde Stehmann, Ruediger Timm

=== Discussion on 3.1.1 stopper issues ===
* From the agenda:
** [http://www.openoffice.org/issues/show_bug.cgi?id=104116 issue 104116] has been accepted
** [http://www.openoffice.org/issues/show_bug.cgi?id=103896 issue 103896] was rejected due to the available workarounds
* The next RC will include install sets for Linux x86-64 wJRE.

=== Discussion on 2.4.3 stopper issues ===
* From the agenda:
** [http://www.openoffice.org/issues/show_bug.cgi?id=104115 issue 104115] has been accepted
* 2.4.3 will contain the most current version of JRE

=== Discussion on 3.2.0 issues ===
* From a mail on the dev@ooo, dev@l10n mailinglist: Sophie found files in CWS paw06 that needs to be translated and asked for a spec, as already suggested on the mailinglist she will ask the developer for more details.

=== Other items ===
* none

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues] <br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]

=== RE duties this week ===
DEV300_m55 by Vladimir Glazunov (vg) <br>
OOO310_m19 by Kurt Zenker (kz) <br>
OOH680_m21 by Kurt Zenker (kz)

=== Upload duties this week ===
Uploads by Marcus Lange (mla)

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-08-10_IRC_log ReleaseStatus Minutes 2009-08-10 IRC log]

== 2009-08-03 ==
Participants: Mechtilde Stehmann, Rene Engelhard, Stefan Baltzer, Joost Andrae, Olaf Felka, Oliver Craemer, Martin Damboldt, Pavel Janik, Shinji Enoki, Jens-Heiner Rechtien, Sophie Gautier, Uwe Luebbers, Marcus Lange, Martin Hollmichel

=== Other items ===
* 3.1.1 release
** Stefan Baltzer mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=101899 issue 101899]. This issue needs further evaluation

=== Discussion on 3.1.1 stopper issues ===
* From the agenda:
** [http://www.openoffice.org/issues/show_bug.cgi?id=103357 issue 103357] has been accepted
** [http://www.openoffice.org/issues/show_bug.cgi?id=103861 issue 103861] has been accepted
** [http://www.openoffice.org/issues/show_bug.cgi?id=103933 issue 103933] has been accepted
** [http://www.openoffice.org/issues/show_bug.cgi?id=103936 issue 103936] has been accepted
** [http://www.openoffice.org/issues/show_bug.cgi?id=103968 issue 103968] has been accepted

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]

=== RE duties this week ===
DEV300_m54 by Jens-Heiner Rechtien (hr)<br>
DEV300_m55 by Vladimir Glazunov (vg)<br>
OOO310_m17 by Kurt Zenker (kz)<br>
OOO310_m18 by Kurt Zenker (kz)

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-08-03_IRC_log ReleaseStatus Minutes 2009-08-03 IRC log]

== 2009-07-27 ==
Participants: Mechtilde Stehmann, Rene Engelhard, Stefan Baltzer, Joost Andrae, Olaf Felka, Marc Neumann, Oliver Craemer, Uwe Luebbers, Martin Damboldt, Chris Cheney, Marcus Lange, Kai Ahrens, Pavel Janik

=== Other items ===
* 3.1.1 release
** Martin proposed [http://qa.openoffice.org/issues/show_bug.cgi?id=103357 issue 103357] for which we received a patch by ayaninger. Henning Brinkmann will prepare a CWS for this patch. Target has been adjusted to 3.1.1
** Build OOO310_m17 is in progress to be started

=== Discussion on 3.1.1 stopper issues ===
From the agenda:
*
=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]

=== RE duties this week ===
DEV300_m54 by Jens-Heiner Rechtien (hr)<br>
OOO310_m17 by Kurt Zenker (kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-07-27_IRC_log ReleaseStatus Minutes 2009-07-27 IRC log]

== 2009-07-20 ==
Participants: Mechtilde Stehmann, Rene Engelhard, Stefan Baltzer, Joost Andrae, Olaf Felka, Marc Neumann, Oliver Craemer, Uwe Luebbers, Shinji Enoki, Jens-Heiner Rechtien, Martin Damboldt, David Tardon, Sophie Gautier, Thorsten Ziehm, Kai Ahrens, Makoto Takizawa

=== Other items ===
* 3.1.1 release
** Martin Damboldt raised [http://qa.openoffice.org/issues/show_bug.cgi?id=102486 issue 102486]. It has been accepted as a stopper.
** Martin also informed about the integration of CWS aw074 which contained several stopper fixes.

=== Discussion on 3.1.1 stopper issues ===
From the agenda:
* Martin Damboldt proposed to discuss and to decide about a [http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues proposal about how to handle fixed and verified issues]. The proposal has been appproved.

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m53 by Ivo Hinkelmann (ihi)<br>
DEV300_m54 by Jens-Heiner Rechtien (hr)<br>
OOO310_m16 by Oliver Bolte (obo)<br>
OOO310_m17 by Kurt Zenker (kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-07-20_IRC_log ReleaseStatus Minutes 2009-07-20 IRC log]

== 2009-07-13 ==
Participants: Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Joost Andrae, Olaf Felka, Fridrich Strba, Marc Neumann, Oliver Craemer, Uwe Luebbers, Shinji Enoki, Pavel Janik, Jens-Heiner Rechtien, Hristo Hristov, Martin Damboldt, Kai Ahrens, Andreas Bartels, Makoto Takizawa, Chris Cheney

=== Other items ===
* 3.1.1 release
** Martin Damboldt proposed [http://qa.openoffice.org/issues/show_bug.cgi?id=103454 issue 103454]. This issue has been accepted as a stopper.
** René Engelhardt raised [http://qa.openoffice.org/issues/show_bug.cgi?id=103357 issue 103357] again. This issue has not been accepted because there's currently no development resource available to fix it for version 3.1.1.
** Stefan Baltzer mentioned that issue [http://qa.openoffice.org/issues/show_bug.cgi?id=101420 101420] needs to be tested before CWS mav53 can be integrated. A Linux build of CWS mav53 will be provided to qa-upload.services to have this issue verified by somebody who can reproduce the crash.

=== Discussion on 3.1.1 stopper issues ===
From the agenda:
*

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m53 by Ivo Hinkelmann (ihi)<br>
OOO310_m16 by Oliver Bolte (obo)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-07-13_IRC_log ReleaseStatus Minutes 2009-07-13 IRC log]

== 2009-07-06 ==
Participants: Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Joost Andrae, Olaf Felka, Fridrich Strba, Marc Neumann, Chris Cheney, Oliver Craemer, Kai Ahrens, Uwe Luebbers, Shinji Enoki, Pavel Janik, Andreas Bartels, Jens-Heiner Rechtien

=== Other items ===
* 3.1.1 release
** René mentioned he had re-opened [http://qa.openoffice.org/issues/show_bug.cgi?id=102004 issue 102004]. Issue has been closed. The follow-up issue will be about 'table in RTL context' regarding the file attached to [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528836 Debian bug 528836]
** Discussion about platforms (Mac and Linux 64 bit) and languages to provide for l10n CWS builds is still open. There should be at least one platform having full builds to allow localization testing of the installer.

=== Discussion on 3.1.1 stopper issues ===
From the agenda:
*

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m52 by Vladimir Glazunov (vg)<br>
OOO310_m16 by Oliver Bolte (obo)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-07-06_IRC_log ReleaseStatus Minutes 2009-07-06 IRC log]

== 2009-06-29 ==
Participants: Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Joost Andrae, Olaf Felka, Fridrich Strba, Martin Hollmichel, Marcus Lange, Marc Neumann, Chris Cheney, Oliver Craemer, Kai Ahrens, Uwe Luebbers

=== Other items ===
* 3.1.1 release
** CWS localization36 is ready for QA. Integration will start at the end of the week as soon as final feedback is available.
** [http://qa.openoffice.org/issues/show_bug.cgi?id=98304 issue 98304] should be fixed. This needs to be clarified together with Rafaella because it needs to be clarified who owns Petr's issues first.
** OOO310_m14 has been uploaded for distribution.
** Localization CWS topics discussed
*** why not a tar.gz wich can be used under rpm and deb systems?
**** translations within the installer cannot be verified
*** Mac builds are missing also 64 bit builds for linux
**** capacity to create Mac builds is very low
**** for Linux 64 bit we need to define the number of languages to be built
*** why is it impossible to prepare only langpacks
**** in general it is possible but having full builds eases the usage for the testers

=== Discussion on 3.1.1 stopper issues ===
From the agenda:
* regarding [http://qa.openoffice.org/issues/show_bug.cgi?id=102485 issue 102485] the responsible developer is just opening a CWS to fix the issue. Target 3.1.1 has been accepted for this issue.
* [http://qa.openoffice.org/issues/show_bug.cgi?id=102378 issue 102378] has been accepted for 3.1.1. It will get integrated using CWS ooo311gsl05.

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m51 by Ivo Hinkelmann (ihi)<br>
DEV300_m52 by Vladimir Glazunov (vg)<br>
OOO310_m15 by Kurt Zenker(kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-06-29_IRC_log ReleaseStatus Minutes 2009-06-29 IRC log]

== 2009-06-22 ==
Participants: Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Joost Andrae, Olaf Felka, Shinji Enoki, Jens-Heiner Rechtien, Fridrich Strba, Kai Ahrens, Martin Hollmichel, Simon Wilper, Marcus Lange, Marc Neumann

=== Other items ===
* 3.1.1 release
** localization CWS is in progress. It's expected to be finished on Wednesday June 24th. Mechtilde asked it localizations will be provided as language packs. Martin answered that these builds will be provided as full installation sets
** for the next OOO310 build the integration work will start by Tuesday 23rd.

=== Discussion on 3.1.1 stopper issues ===
*regarding [http://qa.openoffice.org/issues/show_bug.cgi?id=101513 issue 101513] Olaf Felka proposed to integrate a fix into 3.2 because it's not a low hanging fruit to get a fix until 3.1.1 release.

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m51 by Ivo Hinkelmann (ihi) maybe not before the end of the week<br>
DEV300_m52 by Vladimir Glazunov (vg)<br>
OOO310_m14 by Oliver Bolte (obo) or by Kurt Zenker (kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-06-22_IRC_log ReleaseStatus Minutes 2009-06-22 IRC log]

== 2009-06-15 ==
Participants: Marcus Lange, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Joost Andrae, Olaf Felka, Oliver Craemer, Shinji Enoki, Jens-Heiner Rechtien, Fridrich Strba, Pavel Janik, Kai Ahrens, Martin Hollmichel

=== Other items ===
*

=== Discussion on 3.1.1 stopper issues ===
* Mechtilde added [http://qa.openoffice.org/issues/show_bug.cgi?id=101513 issue 101513] (migration of user settings). Olaf Felka got an action item to find out the development effort to get a fix in time.
* Issue [http://qa.openoffice.org/issues/show_bug.cgi?id=64357 64357] has been discussed. It has been fixed/verified for Solaris. A follow-up issue [http://qa.openoffice.org/issues/show_bug.cgi?id=101875 101875] has been created but it's undefined if there is a fix for 3.1.1 because there are still open questions regarding other platforms.

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m51 by Ivo Hinkelmann (ihi) maybe not before the end of the week<br>
DEV300_m52 by Vladimir Glazunov (vg)<br>
OOO310_m14 build not planned for this week (due to low traffic on that codeline)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-06-15_IRC_log ReleaseStatus Minutes 2009-06-15 IRC log]

== 2009-06-08 ==
Participants: Marcus Lange, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Chris Cheney, Joost Andrae, Olaf Felka, Oliver Craemer, Marc Neumann, Shinji Enoki, Jens-Heiner Rechtien, Uwe Luebbers, Fridrich Strba, Kai Ahrens, Rafaella Braconi

=== Other items ===
* OOo 3.1.1 timeline
** Martin Hollmichel proposed to add August 6th as desired date for OOo 3.1.1rc1
** last OOo 3.1.1 CWS integration date to be planned one week before: July 30th
** there are plans to nominate the already approved CWS for an intermediate milestone based on OOO310 this week
* OOo 3.2.0 timeline
* Possible OOo 2.4.3
** A new milestone based on OOH680 is available. Martin asked if we plan to release this as 2.4.3. Joost mentioned that current disk space usage on the extended mirror network doesn't allow to have 3.1.0rc2 and a 2.4.3 release side by side. The 3.1.0 release is about one month old and it is probable that there are native language teams that want to release a localization based on 3.1.0. Martin mentioned that we need a week to think about it.

=== Discussion on 3.1.1 stopper issues ===
*

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m50 by Ivo Hinkelmann (ihi)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-06-08_IRC_log ReleaseStatus Minutes 2009-06-08 IRC log]

== 2009-05-25 ==
Participants: Marcus Lange, Martin Damboldt, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Chris Cheney, Joost Andrae, Olaf Felka, Oliver Craemer, Marc Neumann, Shinji Enoki, Jens-Heiner Rechtien, Uwe Luebbers, Fridrich Strba, Andreas Bartel, Makoto Takizawa, Kai Ahrens

=== Other items ===
* Martin added a 3.2 timeline to the [http://wiki.services.openoffice.org/wiki/OOoRelease32 release plan] within OOo wiki
* There is currently no fixed day scheduled for the start of OpenOffice.org 3.2 "l10n TCM testing"
* Mechtilde asked to have more time for translation handover because having this schedule would lose one weekend. Martin Damboldt clarified the schedule together with some people involved and came back with a new date: Translation handover will be on Friday, 25th September 2009.
* Ruediger Timm mentioned that next week will be on a public holiday in Germany and it would be fine to either skip the meeting or to move it to another day (Tuesday). Martin Damboldt proposed to skip it. There were no further objections after his proposal.

=== Discussion on 3.1.1 stopper issues ===
* there were no 3.1.1 showstoppers to discuss within today's release status meeting

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m49 by Jens-Heiner Rechtien (hr)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-05-25_IRC_log ReleaseStatus Minutes 2009-05-25 IRC log]

== 2009-05-18 ==
Participants: Marcus Lange, Martin Damboldt, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Chris Cheney, Joost Andrae, Olaf Felka, Oliver Craemer, Marc Neumann, Shinji Enoki, Jens-Heiner Rechtien, Uwe Luebbers, Pavel Janik, Fridrich Strba, Volker Merschmann, Andreas Bartel, Mathias Bauer

=== Other items ===
* Mechtilde Stehmann asked about when the first 3.1.1 milestone is planned. Martin Damboldt is currently working on this topic.
* Schedule for OpenOffice.org 3.2
** 2009-09-28 translation handover
** 2009-10 translation delivery deadline
** No details about l10n CWS builds and l10n TCM testing for now

=== Discussion on 3.1.1 stopper issues ===
* Stefan Baltzer mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=101980 Issue 101980]
* René Engelhard mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=101883 Issue 101883]
The issues have been accepted for 3.1.1

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

=== RE duties this week ===
DEV300_m49 by Jens-Heiner Rechtien (hr)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-05-18_IRC_log ReleaseStatus Minutes 2009-05-18 IRC log]

== 2009-05-11 ==
Participants: Marcus Lange, Martin Damboldt, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Chris Cheney, Fridrich Strba, Joost Andrae, Olaf Felka, Oliver Craemer, Marc Neumann, Makoto Takizawa, Jens-Heiner Rechtien, Hristo Hristov, Kai Ahrens, Uwe Luebbers, Rafaella Braconi, Pavel Janik, Frank Peters, Stefan Weigel

=== Other items ===
* 3.1.0 release<br>
** en-US,da,de,es,fr,gl,ja,it,pl,pt,sh,ru,sr,tr,vi,zh-cn,zh-tw have been uploaded so far. (Not all of them have been registered yet at Bouncer)<br>

* 3.2 time line [proposal has been delayed to next week's meeting]
* 3.1.1 time line
** L10N deadline planned on June 12th 2009 as translation delivery date.
** planned release date on August 27th 2009

=== Discussion on stopper issues ===

=== Review of issues for OOo 3.1.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=101565 Dependency list for 3.1.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1.1]<br>

* discussed issues:
** From the agenda:<br>
*** [http://qa.openoffice.org/issues/show_bug.cgi?id=101504 Issue 101504] duplicate to [http://qa.openoffice.org/issues/show_bug.cgi?id=99842 Issue 99842]
*** [http://qa.openoffice.org/issues/show_bug.cgi?id=101512 Issue 101512]
*** [http://qa.openoffice.org/issues/show_bug.cgi?id=100214 Issue 100214] macrofpicker01 verified for MacOSX
** discussed within the meeting:<br>
*** [http://qa.openoffice.org/issues/show_bug.cgi?id=100878 Issue 100878] has been targeted to 3.1.1 by Stefan Baltzer
*** [http://qa.openoffice.org/issues/show_bug.cgi?id=101457 Issue 101457]
*** [http://qa.openoffice.org/issues/show_bug.cgi?id=101725 Issue 101725]
*** [http://qa.openoffice.org/issues/show_bug.cgi?id=101774 Issue 101774]
All issues mentioned above have been accepted as stoppers for 3.1.1 release and will get registered within the meta issue for 3.1.1.<br>

=== RE duties this week ===
DEV300_m48 by Vladimir Glazunov (vg)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-05-11_IRC_log ReleaseStatus Minutes 2009-05-11 IRC log]

== 2009-05-04 ==
Participants: Marcus Lange, Martin Damboldt, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Uwe Luebbers, Volker Merschmann, Chris Cheney, Fridrich Strba, Joost Andrae, Olaf Felka, Oliver Craemer, Pavel Janik, Sophie Gautier, Pavel Janik, Marc Neumann, Simon Wilper, Makoto Takizawa, enoki, Jens-Heiner Rechtien

=== Other items ===
* 3.1.0 release
** 3.1.0rc2 en-US files have been copied to ../stable/3.1.0/
** 3.1.0rc2 Portuguese localization has been copied to ../localized/pt/3.1.0/
** 3.1.0rc2 Spanish localization has approval but MD5SUMS are missing for the files from Pavel's builds
** 3.1.0rc2 SDK files will follow after approval
** Release announcement is planned for Thursday, May 7th at 11:00am (Hamburg time)
* René asked about the location of ../stable. ftp.stardiv.de is not used anymore as mirror master. Files are provided to master mirrors via rsync (like GWDG)

*Martin Hollmichel will step back as OpenOffice.org release manager and he will hand-over this role to Martin Damboldt

*3.1.1 release
** Mechtilde asked for a 3.1.1 timeline; a release is to be planned for August 2009
** Issue [http://qa.openoffice.org/issues/show_bug.cgi?id=74187 74187] has been re-targeted for 3.2 release but Martin will check if we can integrate the fix for 3.1.1
** Issue [http://qa.openoffice.org/issues/show_bug.cgi?id=97975 97975] has been proposed to be fixed for 3.1.1
** Issue [http://qa.openoffice.org/issues/show_bug.cgi?id=86443 86443] has been proposed to be fixed for 3.1.1
** Debian issue [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472461 472461] has been proposed to be fixed for 3.1.1 (Debian #472461 is Issue 97975)
** l10n teams would like to have some fixes in 3.1.1, mostly for function names in Calc UI; fixes profided as .sdf files on IZ and not a complete retrieve from Pootle; this has been accepted

* DEV300_m47 has been uploaded by Marcus Lange. Files are already visible on some mirrors.

=== Discussion on stopper issues ===
* for OpenOffice.org 3.1

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:

=== RE duties this week ===
DEV300_m48 by Vladimir Glazunov (vg)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-05-04_IRC_log ReleaseStatus Minutes 2009-05-04 IRC log]

== 2009-04-27 ==
Participants: Kai Ahrens, Marcus Lange, Martin Damboldt, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Uwe Luebbers, Volker Merschmann, Chris Cheney, Fridrich Strba, Joost Andrae, Olaf Felka, Oliver Craemer, Pavel Janik, Sophie Gautier, Pavel Janik

=== Other items ===
* OOO310_m11 to become release candidate 2<br>
** upload delayed due to technical problems during the signing process
** upload will start soon
* Martin would like to suggest a change for the 3.2 release schedule
** He'd like to see the next release with a new DSCM
** 3.2 codeline will be branched off in September
** all features for 3.2 release should be integrated before this "branch off" date
** there will be no more bugfixing phase after branch off anymore, we will fallover to showstopper modus then immediately doing on the branch then also the "usual" l10n work
** the 3.2.1 release would be around February 2010
* René mentioned some issues that he want's to get fixed [http://www.openoffice.org/issues/show_bug.cgi?id=86443 issue 86443], [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472461 Debian issue 472461] and [http://www.openoffice.org/issues/show_bug.cgi?id=97975 issue 97975]. Martin Hollmichel asked him to get them fixed for 3.1.1.
* Martin added the 3.1.1 target to Issuetracker

=== Discussion on stopper issues ===
* for OpenOffice.org 3.1

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:

=== RE duties this week ===
OOO310_m12 if needed by Oliver Bolte (obo)<br>
DEV300_m47 by Ivo Hinkelmann (ihi)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-04-27_IRC_log ReleaseStatus Minutes 2009-04-27 IRC log]

== 2009-04-20 ==
Participants: Kai Ahrens, Marcus Lange, Martin Damboldt, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Uwe Luebbers, Volker Merschmann, Chris Cheney, Fridrich Strba, Joost Andrae, Marc Neumann, Olaf Felka, Oliver Craemer, Pavel Janik, Sophie Gautier

=== Other items ===
* OOO310_m11 to become release candidate 2<br>
** one or two additional days needed for the remaining fixes<br>
=== Discussion on stopper issues ===
* for OpenOffice.org 3.1

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:
** Martin was a bit unsure about the current status of issue [http://qa.openoffice.org/issues/show_bug.cgi?id=100994 100994]
** René asked about a xpdf security issue.

=== RE duties this week ===
OOO310_m11 by Kurt Zenker (kz)<br>
DEV300_m47 by Ivo Hinkelmann (ihi)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-04-20_IRC_log ReleaseStatus Minutes 2009-04-20 IRC log]

== 2009-04-06 ==
Participants: Kai Ahrens, Marcus Lange, Martin Damboldt, Martin Hollmichel, Mechtilde Stehmann, Rene Engelhard, Ruediger Timm, Stefan Baltzer, Uwe Luebbers, Volker Merschmann

=== Other items ===
* The "OOo_3.1.0rc1_20090402_Solarisx86_install_wJRE_de.tar.gz" build was missing on the mirrors, in the meantime it was uploaded to the mirrors.
* Several languagepacks are missing, these will be available with the next build.

=== Discussion on stopper issues ===
* for OpenOffice.org 3.1
** Martin H. stated out [http://qa.openoffice.org/issues/show_bug.cgi?id=100851 1000851 "Fontwork deadly slow"]: It seems to be more effort in order to fix this. Discussion will go on on releses@ooo.
** Uwe stated out [http://qa.openoffice.org/issues/show_bug.cgi?id=68302 68302 "Add a 'License' item to Help menu"]: Will not be accepted as stopper since it is open for longer time and menu items are UI relevant.
** René mentioned [http://qa.openoffice.org/issues/show_bug.cgi?id=100836 100836 "Remove writer2latex extension"]: Accepted and will be done in CWS native241correct.

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:

=== RE duties this week ===
OOO310_m10 by Kurt Zenker (kz)<br>
DEV300_m47 by Ivo Hinkelmann (ihi) <br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-04-06_IRC_log ReleaseStatus Minutes 2009-04-06 IRC log]

== 2009-03-30 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Marc Neumann, Marcus Lange, Volker Merschmann, Stefan Baltzer, Ruediger Timm, Kai Ahrens, Martin Damboldt, Uwe Luebbers, Kai Ahrens, Pavel Janik, Oliver Craemer

=== Other items ===

=== Discussion on stopper issues ===
* for OpenOffice.org 3.1
** Martin Damboldt mentioned issue [http://qa.openoffice.org/issues/show_bug.cgi?id=100676 1000676]. This crash needs to be fixed
** Pavel Janik mentioned OpenSSL update. This will get updated with CWS tkr21
** René Engelhard mentioned to ship a newer Python version. He was unsure if the current version contains security issues
** Martin Damboldt mentioned issue [http://qa.openoffice.org/issues/show_bug.cgi?id=100373 100373]

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:
** a discussion about a move of the release schedule came up. We decided to move this decision to next monday's meeting

=== RE duties this week ===
OOO310_m9 by Oliver Bolte (obo)<br>
DEV300_m46 by Ivo Hinkelmann (ihi) <br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-03-30_IRC_log ReleaseStatus Minutes 2009-03-30 IRC log]

== 2009-03-23 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Marc Neumann, Marcus Lange, Sophie Gautier, Volker Merschmann, Stefan Baltzer, Ruediger Timm, Kai Ahrens, Martin Damboldt, Uwe Luebbers, Martin Hollmichel, Gilles, Helge Delfs

=== Other items ===
* Martin Hollmichel mentioned that we're not yet ready for a OpenOffice.org 3.1 release candidate
* Martin asked Sophie if she's confident with the localization status and she answered it's OK. No issues were reported so far.
* DEV300_m44 has been uploaded by Joost
* Volker Merschmann asked for a Release Status Meeting on April 14th to be able to react on the planned release on April 15th

=== Discussion on stopper issues ===
* for OpenOffice.org 3.1

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:

=== RE duties this week ===
OOO310_m8 by Oliver Bolte (obo)<br>
DEV300_m45 by Hans-Joachim Lankenau (hjs) <br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-03-23_IRC_log ReleaseStatus Minutes 2009-03-23 IRC log]

== 2009-03-16 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Fridrich Strba, Marc Neumann, Marcus Lange, Sophie Gautier, Volker Merschmann, Stefan Baltzer, Ruediger Timm, Simon Wilper, Stefan Weigel, Jens-Heiner Rechtien, Kai Ahrens, Martin Damboldt, Oliver Craemer, Uwe Luebbers, Martin Hollmichel

=== Other items ===
* Martin asked to get a localization status of version OOO310_m5 which includes the latest localization until next Monday
* Jens-Heiner will start OOO310_m6 after CWS smoketest21 has been integrated

=== Discussion on stopper issues ===
* for OpenOffice.org 3.1

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:
** René asked to get CWS smoketest21 integrated into 3.1. Jens-Heiner will ask Kurt to get it cloned for 3.1 codeline.
** René ased to get issue [http://qa.openoffice.org/issues/show_bug.cgi?id=100219 100219] fixed for 3.1. Kai Ahrens mentioned his team is taking a deeper look at the issue.
** Stefan Baltzer asked to get CWS fwk106 integrated (containing Mac performance issue fixes [http://qa.openoffice.org/issues/show_bug.cgi?id=100177 100177] and [http://qa.openoffice.org/issues/show_bug.cgi?id=100172 100172])
** Marcus Lange raised issue [http://qa.openoffice.org/issues/show_bug.cgi?id=100227 100227]. Stefan Baltzer confirmed that thias issue might be a release blocker.
** Sophie raised issue [http://qa.openoffice.org/issues/show_bug.cgi?id=100235 100235]

=== RE duties this week ===
OOO310_m6 by Jens-Heiner Rechtien (hr) <br>
Vladimir Glazunov (vg)will do DEV300_m44<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or by Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-03-16_IRC_log ReleaseStatus Minutes 2009-03-16 IRC log]

== 2009-03-09 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Fridrich Strba, Marc Neumann, Uwe Luebbers, Marcus Lange, Sophie Gautier, Ivo Hinkelmann, Volker Merschmann, Stefan Baltzer, Ruediger Timm, Simon Wilper, Stefan Weigel, Joerg Skottke

=== Other items ===
* regarding 2.4.3 release we again discussed that we do not want to have releases in parallel. The timeline should be set after 3.1 release

=== Discussion on stopper issues ===

* for OpenOffice.org 3.1
The following child workspaces have been discussed
** CWS [http://tools.services.openoffice.org/EIS2/cws.ShowCWS?logon=true&Id=8038&Path=OOO310%2Fcl12 mav48] should be integrated into OOO310 codeline if there is no integration risk.
** CWS [http://tools.services.openoffice.org/EIS2/cws.ShowCWS?logon=true&Id=8071&Path=OOO310%2Fmav48 cl12] should be integrated into OOO310 codeline if there is no integration risk
** Martin Hollmichel should have a look at CWS os2port05 if it can be cloned into OOO310 codeline without any danger. Otherwise it should not be integrated into OOO310 codeline.

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

* discussed issues:
** P1 issue [http://qa.openoffice.org/issues/show_bug.cgi?id=99511 999511] status is still unclear.

=== RE duties this week ===
OOO310_m5 by Ivo Hinkelmann (ihi)<br>
Oliver Bolte (obo) will do DEV300<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-03-09_IRC_log ReleaseStatus Minutes 2009-03-09 IRC log]

==2009-03-09==
* Problem with the localization CWS
: The cws OOO310/localization35_OOO310 is still not integrated (2009-03-09)
: It won't be integrated in OOO310_m5 but in OOO310_m6, which isn't scheduled

* The cws OOO310/cl12 which should fix blocker issues is not yet integrated

*'''Accepted Release Blocker'''
: [http://www.openoffice.org/issues/show_bug.cgi?id=98990 Issue 98990] unopkg won't install script extensions (missung: unopkg-desc) - Target 3.1
: [http://www.openoffice.org/issues/show_bug.cgi?id=99511 Issue 99511] MacOSX : build failure at instsetoo_native - ''No Target''
: [http://www.openoffice.org/issues/show_bug.cgi?id=99686 Issue 99686] RPT: images not inserted into report - Target 3.1
: [http://www.openoffice.org/issues/show_bug.cgi?id=100035 Issue 100035] Crash closing document after using styles - Target 3.1
: [http://www.openoffice.org/issues/show_bug.cgi?id=100040 Issue 100040] macro migration fails for forms with non-ascii names - Target 3.1
: <s>[http://www.openoffice.org/issues/show_bug.cgi?id=100042 Issue 100042] Linked sheets aren't updated after opening - Target 3.1</s> fixed while the meeting
: [http://www.openoffice.org/issues/show_bug.cgi?id=100043 Issue 100043] WW8: sub-points of list not in higher level after export - Target 3.1
: [http://www.openoffice.org/issues/show_bug.cgi?id=100044 Issue 100044] Testtool: Additional characters retrieved when reading content of listbox - Target 3.1

* Review of issues for OOo 3.1 if any
: [http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]
: [http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>
* possible time line for a 2.4.3 release?

== 2009-03-02 ==
Participants: Mechtilde Stehmann, Martin Hollmichel, Jens-Heiner Rechtien, Pavel Janik, Sophie Gautier, Michael Stehmann, Stefan Baltzer

=== Other items ===
no discussion

=== Discussion on stopper issues ===
no discussion

=== Review of issues for OOo 3.1 if any ===
* The only discussion today was about CWS locatization35. Martin wanted first to see the first RC with the CWS integrated which should be around March, 12th. But from the past experience it seems better to have another snapshot build before the RC with the CWS. Then we can see if the quality is OK for a RC. Martin is planning with OOO310_m5 or m6 with localization35. The next build will be m4 which should be ready this week.

[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

=== RE duties this week ===
OOO310_m4 by Kurt Zenker (kz)<br>
DEV300_m43 by Oliver Bolte (obo)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-03-02_IRC_log ReleaseStatus Minutes 2009-03-02 IRC log]

== 2009-02-23 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Fridrich Strba, Marc Neumann, Martin Hollmichel, Uwe Luebbers, Jens-Heiner Rechtien, Marcus Lange, Oliver Craemer, Pavel Janik, Martin Damboldt, Jaqueline Rahemipour, Sophie Gautier, Kai Ahrens, Ivo Hinkelmann, Rafaella Braconi, Michael Stehmann, Volker Merschmann, Eike Rathke

=== Other items ===
* Martin thinks we have all fixes for a 2.4.3 release together. Build can be done earliest in a week. Jaqueline asked if issue [http://qa.openoffice.org/issues/show_bug.cgi?id=97849 97849] can be taken into consideration. Martin Hollmichel will ask Martin Damboldt to review that issue.
* OOO310 m2 has been uploaded, waiting for bouncer links availability, should be available today late afternoon or in the evening

=== Discussion on stopper issues ===

* for OpenOffice.org 3.0.1
** de, fr, it, nl, en-US, pl, da, ru, pt-BR, tr, nb, nn, ja, vi uploaded/released

* for OpenOffice.org 3.1
** status localization: Ivo is working on a new localization CWS. He expects to have created it for Windows and for Linux and Solaris by tuesday or by wednesday. This time Ivo merged all strings again to the CWS to ensure this time nothing will get lost. There will be one week for testing. New deadline will be March 5th. Integration on master including localization will be not before March 12th. For broad testing it'll be available until March 15th. Localization build will be provided as "archive" build as tar.gz archive (without installer)
** CWS calc48: Martin Hollmichel had to retarget several CWS to reduce traffic for 3.1 release. CWS frmdlg was nominated. CWS calc48 fixes a bunch of regressions of CWS frmdlg. René asked to integrate rptfix04. With all these changes Martin asked to talk about a potential 3.1 delay. Martin asked Jens-Heiner Rechtien if he knew the current integration status of OOO310_m3. Heiner answered that there are two CWS left with conflicts. Martin calculates with two weeks of delay for the 3.1 release. Martin will nominate CWS calc48 for OOo 3.1 again because it includes a fix for a serious issue regarding external references in charts.
** Issue [http://qa.openoffice.org/issues/show_bug.cgi?id=99511 99511] is a P1 build failure and automatically approved
** For issue [http://qa.openoffice.org/issues/show_bug.cgi?id=98990 98990] a maintainer of the PyUNO code needs to be found
** Issue [http://qa.openoffice.org/issues/show_bug.cgi?id=96743 96743] is a regression to 2.4.1 but it has not been accepted to be fixed in 3.1. Target has been moved to 3.2
** Issue [http://qa.openoffice.org/issues/show_bug.cgi?id=92356 92356] has been retargeted to 3.2. This issue has no duplicates or votes.

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

=== RE duties this week ===
OOO310_m3 by Kurt Zenker (kz)<br>
Oliver Bolte (obo) will do DEV300_m42<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-02-23_IRC_log ReleaseStatus Minutes 2009-02-23 IRC log]

== 2009-02-16 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Fridrich Strba, Marc Neumann, Stefan Baltzer, Martin Hollmichel, Uwe Luebbers, Jens-Heiner Rechtien, Marcus Lange, Oliver Craemer, Pavel Janik, Ruediger Timm, Joerg Jahnke, Simon Wilper, Joerg Skottke, Martin Damboldt, Rafaella Braconi, Kai Ahrens

=== Other items ===
* Discussion about 3.1 CWS localization35. Mechtilde mentioned it should have been available on Feb. 10th. Martin Hollmichel answered that Vladimir Glazunov is going to upload it. Rafaella mentioned that l10n handover was too late. As a solution Pavel proposed to have more regular l10n updates. Joerg Jahnke answered that Ivo Hinkelmann is working on this. René mentioned that this CWS contains issues with status NEW.
* René mentioned: hunspell4thesaurus: nominated, but not in m42 yet and neither cloned to OOO310. (thouggh having 3.1 target and being ready in time). Martin answered that Ivo or Kurt will work on it ASAP
* René mentioned: rptfix04: sorry, didn't have time this weekend, will try to package from the new zips asap.
* the module "testautomation" has been created as separate source tarball since OOO310_m1
* CWS dba31i seems to have introduced UI changes by changing identifiers. Martin is still not sure about the CWS. Rafaella asked to revert the string changes of this CWS. Martin asked Ruediger Timm to pull back the changes. Kai Ahrens suggests to have Frank taking the ownership of the left tasks after backpulling.
* Martin asked about what to do with issue [http://qa.openoffice.org/issues/show_bug.cgi?id=97134 97134]
* Rafaella asked about what to do with issue [http://qa.openoffice.org/issues/show_bug.cgi?id=98693 98693]. Martin answered that the l10n community can ignore the fix.

=== Discussion on stopper issues ===

* for OpenOffice.org 3.0.1
** de, fr, it, nl, en-US, pl, da, ru, pt-BR, tr, nb, nn, ja, vi uploaded/released

* for OpenOffice.org 3.1
* Mechtilde asked about two stopper issues
** Issue [http://www.openoffice.org/issues/show_bug.cgi?id=98805 98805] is probably a duplicate to issue [http://qa.openoffice.org/issues/show_bug.cgi?id=87596 87596] which has been retargeted to 3.2.
** Issue [http://www.openoffice.org/issues/show_bug.cgi?id=98927 98927] has been retargeted to 3.2.
* Uwe Luebbers mentioned there are another four unopkg issues from Oliver Brinzing. Joachim Lingner is working on them

=== Review of issues for OOo 3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=95768 Dependency list for 3.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.1]<br>

=== RE duties this week ===
OOO310_m2 Ivo Hinkelmann (ihi)<br>
Oliver Bolte (obo) will do next milestone on DEV300<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-02-16_IRC_log ReleaseStatus Minutes 2009-02-16 IRC log]

== 2009-02-09 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Fridrich Strba, Marc Neumann, Stefan Baltzer, Martin Hollmichel, Kai Ahrens, Uwe Luebbers, Martin Damboldt, Jens-Heiner Rechtien, Marcus Lange, Frank Schoenheit, Oliver Craemer, Pavel Janik, Sophie Gautier, Volker Merschmann, Ruediger Timm, Nils Fuhrmann

=== Other items ===

=== Discussion on stopper issues ===

* for OpenOffice.org 3.0.1
** de, fr, it, nl, en-US, pl, da, ru, pt-BR, tr uploaded/released

* for OpenOffice.org 3.1
** build of OOO310_m1 is still in progress
** nomination and integration of CWS is a bit slow due to svn diff and merge operations that are much slower than expected. Not all nominated CWS got into m1. Remaining CWS will go into m2.
*** Frank Schoenheit asked about CWS dba31h and why it has not been integrated yet. Martin responded that not every issue within this CWS is declared as a stopper issue
** for CWS dv07 Martin discovered some new strings that were already translated within the database but resulting as new strings within Pootle export.
** CWS localization35 will get a bit delayed because we're still waiting for Arabic UI localization
** localization status: starting on Feb 10., one new language with a three letter ISO code from India. Vladimir Glazunov is thinking about a workaround for this language. Martin proposed to wait for Arabic translation and then start with CWS localization35 and to leave-out the new language (Dogri)
** discussion about rptfix04. Frank Schoenheit and René Engelhardt have been asked to follow-up with a phone call to clarify details. Frank will create a patch against vanilla jfreereport. René will write an issue for it with target 3.1.1 (if available)

=== Review of issues for OOo 3.0.1/3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=93339 3.0.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.0.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.0.1]<br>

=== RE duties this week ===
OOO310_m1 Kurt Zenker (kz)<br>
OOO310_m2 Ivo Hinkelmann (ihi)<br>
Oliver Bolte (obo) will do next milestone on DEV300<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-02-09_IRC_log ReleaseStatus Minutes 2009-02-09 IRC log]

== 2009-02-02 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Fridrich Strba, Marc Neumann, Stefan Baltzer, Martin Hollmichel, Kai Ahrens, Uwe Luebbers, Martin Damboldt, Ruediger Timm, Jens-Heiner Rechtien, Marcus Lange

=== Other items ===
* Possible timeline for 2.4.3 release
** issue [http://qa.openoffice.org/issues/show_bug.cgi?id=91466 91466] justifies a 2.4.3 release
** issue [http://qa.openoffice.org/issues/show_bug.cgi?id=96471 96471]
** All issues [http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=TASK&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&target_milestone=OOo+2.4.3&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=includ]
** Martin would like to talk about these issues within the next meeting
** A new milestone can be prepared for these fixes.

=== Discussion on stopper issues ===
* for OpenOffice.org 3.0.1
** no known stoppers available.
** de, fr, it, nl, en-US, pl, da, ru, pt-BR uploaded/released

* for OpenOffice.org 3.1
** Joost asked to get two CWS integrated
*** CWS kashidafix02 (approved by QA) containing [http://www.openoffice.org/issues/show_bug.cgi?id=98399 issue 98399]
*** CWS swftnnumbers02 (ready for QA) containing [http://www.openoffice.org/issues/show_bug.cgi?id=98418 issue 98418]
*** both issues are related to Arabic i18n
** Martin asked about the the proposal for the installation task priorities
*** Sophie Gautier commented on the releases mailing list that she can live with having [http://qa.openoffice.org/issues/show_bug.cgi?id=89394 issue 89394] implemented in 3.2
** Uwe Luebbers asked regarding meta issue cleanup.
*** regarding [http://qa.openoffice.org/issues/show_bug.cgi?id=97159 issue 97159] Mechtilde said she was not able to create an example Database to get this issue reproduced due to privacy reasons. There have been no decision yet on this issue.
** Mechtilde asked regarding the "NFS mount on FAT" [http://www.openoffice.org/issues/show_bug.cgi?id=97139 issue 97139]
** René mentioned rptfix04 is still not ready because he needs more time. Martin want's to wait until it's ready.

=== Review of issues for OOo 3.0.1/3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=93339 3.0.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.0.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.0.1]<br>

=== RE duties this week ===
DEV300_m41 or OOO310_m1 Kurt Zenker (kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-02-02_IRC_log ReleaseStatus Minutes 2009-02-02 IRC log]

== 2009-01-26 ==
Participants: Rene Engelhard, Olaf Felka, Mechtilde Stehmann, Joost Andrae, Chris Cheney, Fridrich Strba, Marc Neumann, Stefan Baltzer, Bettina Haberer, Martin Hollmichel, Kai Ahrens, Uwe Luebbers, Marcus Lange, Martin Damboldt, Ruediger Timm

=== Other items ===

=== Discussion on stopper issues ===
* for OpenOffice.org 3.0.1
** no known stoppers available. Release is planned for Tuesday January 27th on noon (Hamburg time). Binaries for en-US and de have been uploaded.

* for OpenOffice.org 3.1
** code freeze for 3.1 is this week
** there are still a lot of childworkspaces to integrate
** [http://qa.openoffice.org/issues/show_bug.cgi?id=92147 issue 92147] has been discussed. Martin on the one hand asked if this should be a release blocker and on the other hand he mentioned that the responsive developer currently has other priorities. Then he asked about a priorization of three different issues. The following proposal as been accepted to allow Ingo Schmidt and the localization teams to comment on this proposal: issue [http://qa.openoffice.org/issues/show_bug.cgi?id=92147] is most important, issue [http://qa.openoffice.org/issues/show_bug.cgi?id=89394] second and issue [http://qa.openoffice.org/issues/show_bug.cgi?id=91724] last

=== Review of issues for OOo 3.0.1/3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=93339 3.0.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.0.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.0.1]<br>

=== RE duties this week ===
DEV300_m40 Vladimir Glazunov (vg)<br>
DEV300_m41 or OOO310_m1 Kurt Zenker (kz)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-01-26_IRC_log ReleaseStatus Minutes 2009-01-26 IRC log]

== 2009-01-19 ==
Participants: Martin Damboldt, Rene Engelhard, Olaf Felka, Pavel Janik, Mechtilde Stehmann, Ruediger Timm, Joost Andrae, Chris Cheney, Fridrich Strba, Marcus Lange, Marc Neumann, Stefan Baltzer, Volker Merschmann, Jens-Heiner Rechtien, Bettina Haberer, Martin Hollmichel, Mathias Bauer, Kai Ahrens, Uwe Luebbers, Jens-Heiner Rechtien, Christian Jansen, Stefan Weigel

=== Other items ===

=== Discussion on stopper issues ===
* for OpenOffice.org 3.0.1
** René proposed to change the revision number of Sun Report Builder extension because there were changes for it in OOo 3.0.1. Martin Hollmichel will care about it independent of the 3.0.1 release
** For the Presenter Console there seems to be a similar issue. Martin will care about it
** René mentioned some versioning issue with ure
** Martin asked if we're fine with a 3.0.1 release of OOO300_m15. There were no objections

* for OpenOffice.org 3.1
** based on the fact that feature freeze date passed and all strings are now within translation process Martin objected that the schedule looks a little bit ambitious with the remaining child workspaces. Martin's proposal is to stay with the current code freeze but to calculate with some more time to the actual release. A new deadline Feb 12th, exceptional CWS approved by release team and a new estimated last CWS integration date on March 5th has been appproved.
** Martin Damboldt asked about the integration of usage tracking into this release. René asked if this doesn't affect community builds that are done outside of Sun domain. Heiner told René that it's a "BUILD_SPECIAL" item. In this case René is indifferent to this item. No other objections were raised.
** Martin plans to priorize the current approx. 30 urgent/critical CWS. He will make this transparent within EIS application

=== Review of issues for OOo 3.0.1/3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=93339 3.0.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.0.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.0.1]<br>

=== RE duties this week ===
DEV300_m40 Vladimir Glazunov (vg)<br>
OOO300 Oliver Bolte (obo)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) and Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-01-19_IRC_log ReleaseStatus Minutes 2009-01-19 IRC log]

== 2009-01-12 ==
Participants: Martin Damboldt, Rene Engelhard, Olaf Felka, Pavel Janik, Uwe Luebbers, Joerg Skottke, Mechtilde Stehmann, Ruediger Timm, Eric Bachard, Joost Andrae, Oliver Craemer, Chris Cheney, Fridrich Strba, Marcus Lange, Marc Neumann, Maximilian Odendahl, Stefan Baltzer, Volker Merschmann, Kai Ahrens, Jens-Heiner Rechtien

=== Other items ===

=== Discussion on stopper issues ===
* for OpenOffice.org 3.0.1
** no new show stoppers have been raised
** OOO300_m15 will get uploaded as OpenOffice.org 3.0.1 release candidate 2

* for OpenOffice.org 3.1/3.2
** build of DEV300_m39 is still in progress. There are currently open build issues. The build will get finished within the next days
** Maximilian Odendahl proposed a shift of "code freeze". There's been a discussion about this. The decision if there will be a shift of "code freeze" will be done at next weeks meeting and after DEV300_m39 has been finished and after a quality status of this version has been determined.

=== Review of issues for OOo 3.0.1/3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=93339 3.0.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.0.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.0.1]<br>

=== RE duties this week ===
DEV300_m39 Jens Heiner Rechtien (hr)<br>
DEV300_m40 Vladimir Glazunov (vg)<br>
OOO300 Oliver Bolte (obo)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) and Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-01-12_IRC_log ReleaseStatus Minutes 2009-01-12 IRC log]

== 2009-01-05 ==
Participants: Stefan Baltzer, Martin Damboldt, Rene Engelhard, Olaf Felka, Pavel Janik, Uwe Luebbers, Joerg Skottke, Mechtilde Stehmann, Ruediger Timm, Thorsten Ziehm, Eric Bachard, Hennes Rohling, Joost Andrae, Kai Ahrens, Mikhail Voitenko, Oliver Craemer, Sophie Gautier, Rafaella Bracconi, Jens Heiner Rechtien, Mathias Bauer, Chris Cheney

=== Other items ===
Eric Bachard asked why CWS macleofix4x11 has been nominated for 2.4.2 but has never been integrated. Ruediger answered that the CWS was too late for 2.4.2 and it'll get integrated into 2.4.3.<br>

=== Discussion on stopper issues ===
* for OpenOffice.org 3.0.1
** Issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=97710 97710]]: fix in progress<br>
** Issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=89713 89713]]: A documented workaround is available<br>
** Issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=97139 97139]]: cannot be fixed for 3.0.1.<br>
** Issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=97491 97491]]: fix in progress<br>
** Issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=97741 97741]]: the plan is to take the strings from the toolbar or to revert the string how it was in 3.0<br>

* for OpenOffice.org 3.1/3.2
** Issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=23658 23658]] in touch with
** Issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=86791 86791]]
** CWS datapilotrange will be shifted to 3.2.<br>
** CWS macmenusquit will be taken after feature freeze.<br>
** Reminder: Code freeze for 3.1 is January 29th 2009

=== Review of issues for OOo 3.0.1/3.1 if any ===
[http://www.openoffice.org/issues/showdependencytree.cgi?id=93339 3.0.1 issues]<br>
[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&target_milestone=OOo+3.0.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto Issues with generic target 3.0.1]<br>

=== RE duties this week ===
DEV300_m39 Jens Heiner Rechtien (hr)<br>
OOO300 Oliver Bolte (obo)<br>

=== Upload duties this week ===
Uploads by Marcus Lange (mla) or Joost Andrae (ja)<br>

=== Full IRC log ===
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes_2009-01-05_IRC_log ReleaseStatus Minutes 2009-01-05 IRC log]

== Historic Minutes ==
=== [[ReleaseStatus_Minutes_2008_05-12]] ===
=== [[ReleaseStatus_Minutes_2008_01-04]] ===
=== [[ReleaseStatus_Minutes_2007_09-12]] ===
=== [[ReleaseStatus_Minutes_2007_05-08]] ===
=== [[ReleaseStatus_Minutes_2007_04]] ===
=== [[ReleaseStatus_Minutes_2007_03]] ===
=== [[ReleaseStatus_Minutes_2007_02]] ===
=== [[ReleaseStatus_Minutes_2007_01]] ===
=== [[ReleaseStatus_Minutes_2006_12]] ===
=== [[ReleaseStatus_Minutes_2006_11]] ===
=== [[ReleaseStatus_Minutes_2006_10]] ===

[[Category:Minutes]]
[[Category:Releases]]

Mac port and WWDC2008

2008-06-11T06:12:43Z

Maveric: /* <div align="left" style="color:red; font-size:18px">'''Our needs with Aqua version '''</div> */

== '''Mac OS X porter Team at WWDC 2008''' ==

=== What is WWDC 2008? ===

See [http://developer.apple.com/wwdc/ Apple WWDC 2008]

==== <div align="left" style="color:red; font-size:18px">'''Our needs with Aqua version '''</div> ====
* Compile on Intel for PPC (if time UB) [ ]
* Proxy icon in the title bar [ ]
* Use of the apple remote, especially for presentations [7]
* Printing to PDF to keep links in the same way as iWork does it. [8]
* Translating the native dialogs to the Community supported languages (that Apple doesn't support).
* Compiling on Leopard to run on Tiger. Note: QuickLook plugin ( from quicklookplugin01 cws) builds on tiger [9]
* Import/Export of iWork documents [10]
* Signing OpenOffice.org .app bundle.
* Localize the voice for accessibility features ? (only english available for Voice Over at the moment)
* Implement the native Color Picker
* Knowing the API that integrates iLife (most important iPhoto, iTunes)

=== <div align="left" style="color:blue; font-size:18px">'''Interesting Labs '''</div> ===

It is extremely important to organize us for Labs. The rule is extremely simple: bring your laptop, your code, and ask :)

[[Mac_port_and_WWDC2008/Interesting Labs | ==> Interesting Labs (click me) <== ]]

[http://developer.apple.com/wwdc/schedules/#day=monday&time=morning&tab=lab '''The link for Labs agenda''' ]

=== <div align="left" style="color:blue; font-size:18px">'''Interesting Sessions '''</div> ===

* Performance Tuning Your Application with Shark
* Making Your Application Scriptable
* Managing X.509 Certificates and Digital Identities

[http://developer.apple.com/wwdc/schedules/#day=monday&time=morning&tab=session ==> '''All the Sessions (click me)<==''' ]

=== <div align="left" style="color:green; font-size:18px">'''Who? '''</div> ===

* Michael Sicotte
* Eric Bachard
* Philipp Lohmann

=== <div align="left" style="color:red; font-size:18px">'''Our Objectives at the WWDC 2008 '''</div> ===

==== Goals ====

'''1) Connection OOo Mac team / Apple engineers'''

-Goal 1.1: "Get infos, contacts, human to human conversation :-)"

-> Present our current work, methods and team to Apple people :

-> Meet them during WWDC: give us/them a face, keep contacts

-> Get their impression about what we have already done and what is still ToDo

'''2) Improve from Apple's engineers expertise'''

-Goal 2.1: "Give MacOS X users the OOo suite they deserve"

=> As mac platform and apple's product fans, we are proud to bring the quality and power of OOo to mac users community

=> Make OOo uses all the power of Mac OSX, including upcoming Leopard !

-Goal 2.2: "OO.org Mac port has to be as Apple HIG compliant as possible"

=> Define what is expected for User Interface of OpenOffice.org suite with people from Apple UI project

- FYI: Last year, Apple UI project proposed ericb to help us, once our native menus will be working.
This is now done.

'''3) Get code guidelines, tips, samples'''

-Goal 3.1: "Ask for code review and find code snippets"

-Goal 3.2: "Attend key Labs and Sessions to get full overview of Tiger/Leopard/Core's and useful code"

- Image capture
- Key signing (digital signature, to avoid Mozilla bazaar
- Apple Remote

'''4) Social Contacts / Team emulation'''

Try to contact Pierre de Filippis, Sébastien Plisson and some other frenchies :)

-> Discuss and meet new developers and / or american people working for Mac OS X port (like Michael Sicotte, other..)
-> Share ideas, tips, conviviality !

'''5) Visibility'''

OpenOffice.org Native Mac port has to be recognized as the professionnal office suite for Mac users it is !

==== ericb's Agenda====

The rule is extremely simple: bring your laptop, your code, and ask :)

{| border="1" cellpadding="10"
| Hours
|9:00 AM - 10:15 AM
|10:30 AM - 11:45 AM
|Noon - 1:45 PM
|2:00 PM - 3:15 PM
|3:30 PM - 4:45 PM
|5:00 PM - 6:15 PM
|Evening
|-
| monday<br>June 9
| Keynote <br> begins at 10:00 am
| Keynote
|
| Mac OS X <br>State of the Union <br> (Presidio)
| bgcolor="#dae6ff" |Open Hours <br> Compatibility Labs
| Graphics & Media<br> State of the Union <br>(Presidio)
| bgcolor="#ffff00" | WWDC <br>Welcome Reception
|-
| tuesday<br>June 10
| bgcolor="#55ffde" | Getting Started <br>with OpenGL <br>(North Beach)
| bgcolor="#539fde" | Application Accessibility <br> (Marina)
| bgcolor="#dae6ff" |Mac OS X <br>User Interface Design<br> Consulting Lab
| bgcolor="#dae6ff" | Objective-C: <br>Migrating from <br>Other Languages<br>(marina) <br>'''OR'''<br>Application Scripting Lab
| New Compiler <br>Technology and <br>Future Directions <br>(soma)
|
|
|-
| wednesday<br>June 11
| bgcolor="#539fde" | System-Wide <br>Previews <br>with Quick Look<br>(marina)
| bgcolor="#539fde" | Sync Services: <br>A Complete Tour<br>(Nob Hill)
| Lunchtime Speaker <br>12:30 PM - 1:30 PM <br>Room: Presidio
| bgcolor="#dae6ff" |Sync Services Lab
| bgcolor="#dae6ff" |File Systems Lab
|
|
|-
| thursday<br>June 12
| Cocoa <br>Tips and Tricks<br>(mission)
| Cocoa Layer <br>Backed Views <br>(mission)
|
| bgcolor="#539fde" | Making Your Application <br>Scriptable<br>(North Beach)
| Using Garbage Collection with Objective-C
| bgcolor="#539fde" | Image Capture <br> & Image Kit <br>(soma) <br>'''OR''' <br> Managing<br> X.509 Certificates<br> and Digital Identities
| bgcolor="#ffff00" |WWDC Bash <br>at Yerba Buena Gardens<br> San Francisco<br>6:30 PM - 9:30 PM
|-
| friday <br>June 13
| Getting Started with the I/O Kit: Device Drivers on Mac OS
| Departure for the airport
|
|
|
|
|
|}

==== Philipp's Agenda====

* On behalf of hdu: ask about "gray baseline" in aquabmpfix01

==== Michael's Agenda====

FIXME

=== <div align="left" style="color:red; font-size:18px">'''Todo list '''</div> ===

Please add topics, technical questions you would see asked by attendees to Apple engineers during WWDC

====Suggestions for current issues to be fixed ====

(ericb)

I am volunteer to take over what follows:

*Find information about SpotLight and QuickLook ( what happens with our generator ? How improve it ?)
*Find information about Image Capture : API obsolete on Tiger, under NDA on Leopard ... can we trust 10.4 sources ?
*Apple remote implementation

==== Travel ====

*describe the schedule of the travel

ericb :
<pre>
Basel -> Paris -> SF: 7th of June SFO scheduled arrival: 12:30
SFO departure 3:30 pm -> Paris -> Basel: 13th of June +1 (arrival 17:00h / 5:00 pm)

Hotel: Hotel des Arts (close to Union Square)

Airport to Hotel transportation: (BART) not included
</pre>

Michael Sicotte:
<pre>
June 8 Houston -> Oakland Arrive 12:05 pm
Hotel: Hotel des Arts (close to Union Square)
June 13 SFO -> Houston 4:25 pm
</pre>

Philipp Lohmann:

*Arrival in SF on 8th of June, 12:30 pm
*Departure from SF 15th of June, 3:30 pm

==== Misc ====

*don't forget sector adaptator for laptop: US connectors are '''different'''

*don't forget Cameras (and chargers)

*Prepare 50 to 100 business cards : the most simple is to use the model I can provide on demand , and print them with special paper (pre-cut)

[[Category:Aqua]]
[[Category:Development]]

DE/2.4 Release Test

2008-03-12T10:59:19Z

Maveric: /* Testmatrix */

[[Category:de.openoffice.org|Release Test 2.4]]
Diese Seite dient der Koordination der Release-Tests der deutschsprachigen 2.4 Version.
Die Tests sollen der Freigabe der deutschsprachigen Pakete von OpenOffice.org 2.4 dienen.

Der Freigabetest wird anhand des Release-Sanity Scenarios im TCM durchgeführt.
Zum Test werden die regulären RC's für die jeweilige Plattform verwendet. Dies ist diesmal die Version 2.4.0 RC 2

[http://qatrack.services.openoffice.org/view.php?action=filter_build&fltbuild_version_like=&fltbuild_avail_since=30&fltbuild_lang_in%5B%5D=de&fltbuild_status_in%5B%5D=UNTESTED&fltbuild_status_in%5B%5D=INQA&fltbuild_status_in%5B%5D=APPROVED&fltbuild_uri_like= Übersicht in qatrack]

==Liste der Plattformen (ggf. nicht aktuell):==
* SUN-Builds
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86 deb]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Windows ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Windows mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86 RPM ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86 RPM mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ SolarisSparc ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Solaris Sparc mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Solaris X86 ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Solaris X86 mit JRE]

* Pavels Build
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/.newserver Linux x86 deb]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/.newserver Linux x86 rpm]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/.newserver Linux x86_64 deb]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/.newserver Linux x86_64 rpm]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680 Windows]

* Mahos builds
** [ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/ Mac OS X x86 (Intel)+X11]
** [ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/ Mac OS X PPC + X11]

* [ftp://ooopackages.good-day.net/pub/OpenOffice.org/FreeBSD/ Jacks builds] FreeBSD 5 und 6 - Verzeichnisse .

Werden Fehler oder Probleme aufgedeckt, sollten unbedingt entsprechende Issues gesucht und ggf. neu erfasst werden. Diese sollten dann im TCM bei dem Testfall hinterlegt werden, bei dem das Problem entdeckt wurde.
Bei Problemen unbedingt auf der QA Liste melden. Gefundene Fehler sollten im Zweifelsfall auch dort diskutiert werden.
Bei Problemen mit Issuezilla (z.B. ungenügende Kenntnisse beim Aufgeben von Issues) ebenfalls auf der QA-Liste melden. Dort erhaltet Ihr Hilfe zur Erstellung und Bearbeitung der Issues.

Um bei den Tests mithelfen zu können, wird ein TCM-Account benötigt. Bei Interesse wendet euch bitte an qa@de.openoffice.org

= Informationen und Links =

* [http://de.openoffice.org/about-ooo/about_tcm.html Über TCM]
* [http://www.sunvirtuallab.com/tcm2/opensource/tcm_login.cgi?tcm_config=newooo TCM Login]

= Testmatrix =
wer macht welche Tests - es werden folgende Markierungen verwendet:

'''Bitte gebt an, ob ihr die Version mit oder ohne JRE installiert'''

* <span style="color: #a0a0a0">grau</span> - Test noch nicht zugeteilt
* normal - zum Testen eingeteilt / Test in Arbeit
* ''kursiv'' - Test mit unkritischen Fehlern bestanden
* '''fett''' - Test ohne Fehler bestanden
* '''''fett-kursiv''''' - Test mit kritischen Fehlern fehlgeschlagen

{| border="1" cellpadding="2"
|-
! Plattform
! Tester !! Ergebnis
|-
! Mac( PPC)
||Martin Hagmann (Torwart)||
|-
! Mac( x86)
||Eric Hoch (maveric) ||
* first.bas und topten.bas laufen durch.
* TCM Test kommt
|-
! PowerPC(Linux)
|| ||

|-
! Sparc(Solaris10)
|| ||

|-
! Sparc(Solaris8)
|| ||
|-
! Sparc(Solaris9)
|| ||

|-
! x86(FreeBSD5.3)
|| ||

|-
! x86(Linux/deb mit/ohne KDE)
|| Gerald (mit KDE) ||

* Keine kritischen Fehler gefunden.
* Automatische Tests nicht durchgeführt.
|-
! x86(Linux/RPM mit/ohne JRE)
|| SimonAW (ohne JRE) ||

* ''topten.bas: 1 Warning: Database Open Database -> error
* Chart2: [http://de.openoffice.org/issues/show_bug.cgi?id=86609 86609]
|-
! x86_64 (Linux/deb mit/ohne KDE)
|| ||
|-
! x86_64(Linux rpm)
|| ||
|-
! x86(Linux/JDS3)
|| ||

|-
! x86(Solaris10)
|| Marko||
Installation, first und topten ok

|-
! x86(Solaris10jre)
|| Marko||

|-
! X86(Solaris9)
|| ||

|-
! x86(Win2003 mit/ohne JRE)
|| ||

|-
! x86(Win2K mit/ohne JRE)
|| VolkerMe (ohne JRE) ||
Installation, first und topten ok
Ist keine JRE vorhanden erzeugt topten ohne jre 1 Fehler
|-
! x86(Win98 mit/ohne JRE (SE?))
|| VolkerMe (SE, ohne JRE)||
Installation, first und topten ok
|-
! x86(WinME mit/ohne JRE)
|| ||

|-
! x86(WinXP mit/ohne JRE)
|| VolkerMe (ohne JRE)||
Installation, first und topten ok
|-
! x86(WinVista mit/ohne JRE)
|| Marko||
Installation, first und topten ok
(Ist keine JRE vorhanden erzeugt topten ohne jre) 1 Fehler
|}

= Zusatzaufgaben =

== Issues verifizieren ==

Folgende Issues sind für OOo 2.4 geplant, aber noch nicht geschlossen. Diese sollten aufgearbeitet werden:

* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&target_milestone=OOo+2.4&Submit+query=Submit+query zu verifizierende Issues]

Vorgehen:
* einen Issue hernehmen (am besten, einen, mit dem man bereits zu tun hatte)
* prüfen, ob er tatsächlich gefixt ist ('''nur Issues bearbeiten, bei denen man sicher ist, das Problem zu verstehen''')
* wenn ja -> Status auf "Closed" wechseln (Mark Issue as Closed)
* wenn nein -> Issue wieder öffnen (reopen issue) und target auf 2.x ändern
* jeweils einen Kommentar hinterlassen, mit welcher Version (RC x) geprüft wurde und welche Probleme evtl. noch beobachtet wurden

Sonst keine Änderungen vornehmen .. auch keine Diskussionen, dass man den Fehler lieber anders gefixt haben möchte, oder dass es im Umfeld noch weitere Probleme gibt. Sollte das der Fall sein, einen neuen Issue aufgeben.

DE/2.3 Release Test

2007-09-18T22:37:03Z

Maveric: /* Testmatrix */

[[Category:de.openoffice.org|Release Test 2.3]]
Diese Seite dient der Koordination der Release-Tests der deutschsprachigen 2.3 Version. Die Version '''''OOG680_m5 = 2.3 RC 3 ''''' erscheint am 11.09.2007.
Die Tests sollen der Freigabe der deutschsprachigen Pakete von OpenOffice.org 2.3 dienen.

Der Freigabetest wird anhand des Release-Sanity Scenarios im TCM durchgeführt.
Zum Test werden die regulären RC's für die jeweilige Plattform verwendet.

[http://qatrack.services.openoffice.org/view.php?action=filter_build&fltbuild_version_like=&fltbuild_avail_since=30&fltbuild_lang_in%5B%5D=de&fltbuild_status_in%5B%5D=UNTESTED&fltbuild_status_in%5B%5D=INQA&fltbuild_status_in%5B%5D=APPROVED&fltbuild_uri_like= Übersicht in qatrack]

==Liste der Plattformen (ggf. nicht aktuell):==
* SUN-Builds
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_LinuxIntel_install_de_deb.tar.gz Linux x86 deb]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_Win32Intel_install_de.exe Windows ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_Win32Intel_install_wJRE_de.exe Windows mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_LinuxIntel_install_de.tar.gz Linux x86 RPM ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_LinuxIntel_install_wJRE_de.tar.gz Linux x86 RPM mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_SolarisSparc_install_de.tar.gz SolarisSparc ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_SolarisSparc_install_wJRE_de.tar.gz Solaris Sparc mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_Solarisx86_install_de.tar.gz Solaris X86 ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/2.3.0rc3/OOo_2.3.0rc3_20070910_Solarisx86_install_wJRE_de.tar.gz Solaris X86 mit JRE]

* Pavels Build
** [ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/OOG680_m5/Build-1/OOo_2.3.0_LinuxX86_install_de_deb.tar.gz Linux x86 deb]
** [ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/OOG680_m5/Build-1/OOo_2.3.0_LinuxX86-64_install_de_deb.tar.gz Linux x86_64 deb]
** [ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/OOG680_m5/Build-1/OOo_2.3.0_LinuxX86-64_install_de_rpm.tar.gz Linux x86_64 rpm]
** [ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/OOG680_m5/Build-1/OOo_2.3.0_070911_Win32Intel_install_de.exe Windows]

* Mahos builds
** [ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/2.3.0rc3_20070911/OOo_2.3.0rc3_20070911_MacOSXIntel_X11_install_de.dmg Mac OS X x86 (Intel)+X11]
** [ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/2.3.0rc3_20070911/OOo_2.3.0rc3_20070911_MacOSXPPC_X11_install_de.dmg Mac OS X PPC + X11]

* [ftp://ooopackages.good-day.net/pub/OpenOffice.org/FreeBSD/ Jacks builds] FreeBSD 5 und 6 - Verzeichnisse .

Werden Fehler oder Probleme aufgedeckt, sollten unbedingt entsprechende Issues gesucht und ggf. neu erfasst werden. Diese sollten dann im TCM bei dem Testfall hinterlegt werden, bei dem das Problem entdeckt wurde.
Bei Problemen unbedingt auf der QA Liste melden. Gefundene Fehler sollten im Zweifelsfall auch dort diskutiert werden.
Bei Problemen mit Issuezilla (z.B. ungenügende Kenntnisse beim Aufgeben von Issues) ebenfalls auf der QA-Liste melden. Dort erhaltet Ihr Hilfe zur Erstellung und Bearbeitung der Issues.

Um bei den Tests mithelfen zu können, wird ein TCM-Account benötigt. Bei Interesse wendet euch bitte an qa@de.openoffice.org

= Informationen und Links =

* [http://de.openoffice.org/about-ooo/about_tcm.html Über TCM]
* [http://www.sunvirtuallab.com/tcm2/opensource/tcm_login.cgi?tcm_config=newooo TCM Login]

= Testmatrix =
wer macht welche Tests - es werden folgende Markierungen verwendet:

'''Bitte gebt an, ob ihr die Version mit oder ohne JRE installiert'''

* <span style="color: #a0a0a0">grau</span> - Test noch nicht zugeteilt
* normal - zum Testen eingeteilt / Test in Arbeit
* ''kursiv'' - Test mit unkritischen Fehlern bestanden
* '''fett''' - Test ohne Fehler bestanden
* '''''fett-kursiv''''' - Test mit kritischen Fehlern fehlgeschlagen

{| border="1" cellpadding="2"
|-
! Plattform
! Tester !! Ergebnis
|-
! Mac( PPC)
||Martin Hagmann (torwart)||
|-
! Mac( x86)
||Raphael Bircher (rbircher) || Soweit ok
|-
! Mac( x86)
||Eric Hoch (maveric) || ''ok''
|-
! PowerPC(Linux)
|| ||

|-
! Sparc(Solaris10)
|| ||

|-
! Sparc(Solaris8)
|| ||
|-
! Sparc(Solaris9)
|| ||

|-
! x86(FreeBSD5.3)
|| ||

|-
! x86(Linux/deb mit/ohne KDE)
|| Gerald (mit KDE) ||
|-
! x86(Linux/RPM mit/ohne JRE)
|| ''andreasma (ohne JRE)'' ||
|-
! x86_64 (Linux/deb mit/ohne KDE)
||thackert||
|-
! x86_64(Linux rpm)
||berthold (mit JRE) ||
|-
! x86(Linux/JDS3)
|| ||

|-
! x86(Solaris10)
|| reichowmi (mit JRE) ||

|-
! X86(Solaris9)
|| ||

|-
! x86(Win2003 mit/ohne JRE)
|| ||

|-
! x86(Win2K mit/ohne JRE)
|| ||

|-
! x86(Win98 mit/ohne JRE (SE?))
|| ||
|-
! x86(WinME mit/ohne JRE)
|| ||

|-
! x86(WinXP mit/ohne JRE)
||andreschnabel ||

|-
! x86(WinVista mit/ohne JRE)
|| jrahemipour ||

|}

= Zusatzaufgaben =

== Issues verifizieren ==

Folgende Issues sind für OOo 2.3 geplant, aber noch nicht geschlossen. Diese sollten aufgearbeitet werden:

* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&target_milestone=OOo+2.3&Submit+query=Submit+query zu verifizierende Issues]

Vorgehen:
* einen Issue hernehmen (am besten, einen, mit dem man bereits zu tun hatte)
* prüfen, ob er tatsächlich gefixt ist ('''nur Issues bearbeiten, bei denen man sicher ist, das Problem zu verstehen''')
* wenn ja -> Status auf "Closed" wechseln (Mark Issue as Closed)
* wenn nein -> Issue wieder öffnen (reopen issue) und target auf 2.x ändern
* jeweils einen Kommentar hinterlassen, mit welcher Version (RC x) geprüft wurde und welche Probleme evtl. noch beobachtet wurden

Sonst keine Änderungen vornehmen .. auch keine Diskussionen, dass man den Fehler lieber anders gefixt haben möchte, oder dass es im Umfeld noch weitere Probleme gibt. Sollte das der Fall sein, einen neuen Issue aufgeben.

Documentation/Building Guide/Building on MacOSX

2007-09-12T07:36:54Z

Maveric: /* <div align="left" style="color:green; font-size:18px">'''Needed for Milestone build'''</div> */

<div align="left" style="color:blue; font-size:18px">'''WARNING: Important modifications of the current page in progress '''</div>

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

==== Mac OS X version ====

=> '''Minimal version for AquaBuild is Mac OS X 10.4 ( aka Tiger ).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

==== Xcode ====

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''. Older are deprecated.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xlib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

<pre>This issue should be fixed soon: a fix is scheduled in cloph09 cws</pre>

==== Java ====

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change the Java version -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables the build using java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. e.g. several known build issues have to be fixed e.g. hsqldb, but probably other modules are concerned.

Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:green; font-size:18px">'''Additional dependencies for current Milestone builds'''</div>===

==== prebuilt Mozilla archives ====

For the Milstone build, you'll have to put the prebuild archives of mozilla binaries in moz/zipped directory after renaming them properly.

URL : http://tools.openoffice.org/moz_prebuild/680/

Note: archives are Universal Binaries, and you'll have to rename them, depending on your architecture (either Intel or PowerPC)

Archives to be downloaded :

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBinc.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBlib.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBruntime.zip

If you want to build using them on PowerPC or Intel architecture (with Tiger) please rename them this way :

{| border="1"
|Archive || Name in Intel architecture || Name on PowerPC architecture
|-
| headers || MACOSXGCC'''I'''inc.zip || MACOSXGCC'''P'''inc.zip
|-
| runtime || MACOSXGCC'''I'''runtime.zip || MACOSXGCC'''P'''lib.zip
|-
| libs || MACOSXGCC'''I'''lib.zip || MACOSXGCC'''P'''lib.zip
|}

As you can see, '''P''' means PowerPC, and '''I''' means Intel

.. and put them into <ooo build directory>/680_mXXX/moz/zipped OpenOffice.org should detect and use them if you respect the configure command line as described in Milestone build.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build OpenOffice.org several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.

You can install it using fink. It is simply named "ccache". For MacPorts users the package is called "ccache".

If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/

In order to use ccache you need to change the following environment variables '''assuming you're using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

== '''Everything is installed ? Now choose the build you want to do... '''==

<br><br>

<div align="left" style="color:blue; font-size:18px">'''1. [[AquaBuild/Current]] - build aqua versions of current milestones'''</div>

<div align="left" style="color:green; font-size:18px">'''2. [[AquaBuild/Cocoa]] for advanced developers (Cocoa version, crashy, buggy and not complete)'''</div>

== '''Want to add a module into aquavcl03 cws ?''' ==

If you have changes and/or modifications in another module, a developer with correct rights will add it in the list.

<div align="left" style="color:red; font-size:16px">'''See [[AquaPortCocoa]] for more informations'''</div>

=== Important links or Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

== '''Current Work in progress (not integrated )''' ==

Developers are working on the following Child workspaces (Mac OSX dedicated) :

*'''macosxspellchecker''' : use Mac OS X spellchecker

Concerned modules: lingucomponent, solenv

*'''cloph09''' ( remove X11SDK dependance for Aquabuild )

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, svtools, vcl

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''aquaremovescripts''' (nominated) :

concerned module: instsetoo_native

*'''readme4macintel''' (status: undefined):

concerned module : readlicense_oo

Work in progress:

*'''macosxdnd'''

Concerned mmodule is dtrans ( Drag and Drop )

Integrated in m226

*'''aquaremovescripts'''

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

*Panther build (X11 only) : currently broken ( work in progress )

Since latest resync, no build issues have been reported.

*Tiger: no problem nor for X11 nor Aqua versions (main baseline)

*Leopard (Intel only, because no PowerPC developer ): build broken, but Carbon and Cocoa version work already. Java is not found, but using a working preferences files, everything Java works ( seems to be only Java detection fails ). Native FilePicker needs some work.

Lot of warnings in vcl, due to other deprecated stuff

<div align="left" style="color:grey; font-size:12px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

Documentation/Building Guide/Building on MacOSX

2007-09-12T07:23:56Z

Maveric: /* '''Everything is installed ? Now choose the build you want to do... ''' */

<div align="left" style="color:blue; font-size:18px">'''WARNING: Important modifications of the current page in progress '''</div>

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

==== Mac OS X version ====

=> '''Minimal version for AquaBuild is Mac OS X 10.4 ( aka Tiger ).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

==== Xcode ====

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''. Older are deprecated.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xlib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

<pre>This issue should be fixed soon: a fix is scheduled in cloph09 cws</pre>

==== Java ====

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change the Java version -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables the build using java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. e.g. several known build issues have to be fixed e.g. hsqldb, but probably other modules are concerned.

Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:green; font-size:18px">'''Needed for Milestone build'''</div>===

==== prebuilt Mozilla archives ====

For the Milstone build, you'll have to put the prebuild archives of mozilla binaries in moz/zipped directory after renaming them properly.

URL : http://tools.openoffice.org/moz_prebuild/680/

Note: archives are Universal Binaries, and you'll have to rename them, depending on your architecture (either Intel or PowerPC)

Archives to be downloaded :

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBinc.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBlib.zip

http://tools.openoffice.org/moz_prebuild/680/MACOSXGCCUBruntime.zip

If you want to build using them on PowerPC or Intel architecture (with Tiger) please rename them this way :

{| border="1"
|Archive || Name in Intel architecture || Name on PowerPC architecture
|-
| headers || MACOSXGCC'''I'''inc.zip || MACOSXGCC'''P'''inc.zip
|-
| runtime || MACOSXGCC'''I'''runtime.zip || MACOSXGCC'''P'''lib.zip
|-
| libs || MACOSXGCC'''I'''lib.zip || MACOSXGCC'''P'''lib.zip
|}

As you can see, '''P''' means PowerPC, and '''I''' means Intel

.. and put them into <ooo build directory>/680_mXXX/moz/zipped OpenOffice.org should detect and use them if you respect the configure command line as described in Milestone build.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build OpenOffice.org several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.

You can install it using fink. It is simply named "ccache". For MacPorts users the package is called "ccache".

If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/

In order to use ccache you need to change the following environment variables '''assuming you're using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

== '''Everything is installed ? Now choose the build you want to do... '''==

<br><br>

<div align="left" style="color:blue; font-size:18px">'''1. [[AquaBuild/Current]] - build aqua versions of current milestones'''</div>

<div align="left" style="color:green; font-size:18px">'''2. [[AquaBuild/Cocoa]] for advanced developers (Cocoa version, crashy, buggy and not complete)'''</div>

== '''Want to add a module into aquavcl03 cws ?''' ==

If you have changes and/or modifications in another module, a developer with correct rights will add it in the list.

<div align="left" style="color:red; font-size:16px">'''See [[AquaPortCocoa]] for more informations'''</div>

=== Important links or Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

== '''Current Work in progress (not integrated )''' ==

Developers are working on the following Child workspaces (Mac OSX dedicated) :

*'''macosxspellchecker''' : use Mac OS X spellchecker

Concerned modules: lingucomponent, solenv

*'''cloph09''' ( remove X11SDK dependance for Aquabuild )

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, svtools, vcl

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''aquaremovescripts''' (nominated) :

concerned module: instsetoo_native

*'''readme4macintel''' (status: undefined):

concerned module : readlicense_oo

Work in progress:

*'''macosxdnd'''

Concerned mmodule is dtrans ( Drag and Drop )

Integrated in m226

*'''aquaremovescripts'''

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

*Panther build (X11 only) : currently broken ( work in progress )

Since latest resync, no build issues have been reported.

*Tiger: no problem nor for X11 nor Aqua versions (main baseline)

*Leopard (Intel only, because no PowerPC developer ): build broken, but Carbon and Cocoa version work already. Java is not found, but using a working preferences files, everything Java works ( seems to be only Java detection fails ). Native FilePicker needs some work.

Lot of warnings in vcl, due to other deprecated stuff

<div align="left" style="color:grey; font-size:12px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

Documentation/Building Guide/Building on MacOSX

2007-08-21T19:02:28Z

Maveric: /* On PowerPC */

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

==== Mac OS X version ====

=> '''Minimal version for AquaBuild is Mac OS X 10.4 ( aka Tiger ).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

==== Xcode ====

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''

If you really cannot use XCode 2.4.1 nor XCode 2.4:

Xcode 2.2, 2.3 are known to work for Aqua development. If any earlier versions work as well, please add them here.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xlib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

<pre>This issue should be fixed soon.</pre>

==== Java ====

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build OpenOffice.org several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.

You can install it using fink. It is simply named "ccache". For MacPorts users the package is called "ccache".

If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/

In order to use ccache you need to change the following environment variables '''assuming you're using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

<div align="left" style="color:grey; font-size:18px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''Getting the code (checkout, merge and patch the puppy)''' ==

Two possibilities : either build Carbon version, and test the (soon) alpha version, or build Cocoa version and help us for the development.

Work in progress: a cws named aquavclcarbonfixes, based on milestone m225, concerning Top 5 of issues before Alpha is in progress.

The main changes will concern vcl, and desktop ( to add the native progressbar for the splashscreen).

-> Stay tuned

<big>'''If you want to to contribute on the development, please note that aquavcl03 is dedicated to our Carbon -> Cocoa migration.

So many things that worked before may be broken since that migration is not yet complete.'''</big>

<div align="left" style="color:blue; font-size:18px">'''For Carbon version, you'll need to (in the described order):'''</div>

*checkout m225 source code. For that, see :
** [[AquaBuild#Create_a_directory_for_a_given_milestone.2C_setup_CVS_access:| create a directory for OpenOffice.org sources]]
** [[AquaBuild#checkout_SRC680_.28Master_workspace_since_aquavcl01_integration.29_.281.2C5_GB.29:| Checkout the sources]]
* Jump into [[AquaBuild#One-Time_preparations_and_scripts]] section and build OpenOffice.org (the important is in the configure command line)

<div align="left" style="color:red; font-size:18px">'''For Cocoa version'''</div>

Now, all the changes are commited in aquavcl03, and all what you have to do is :

- checkout m225 source code

- checkout aquavcl03 modules.

Currently : <div align="left" style="color:blue">'''instsetoo_native, solenv and vcl'''</div>

Note: if you want to add a new module, have a look at [[AquaBuild#Want_to_add_a_module_into_aquavcl03_cws_.3F]] section.

aquavcl03 cws does use SRC680 master workspace, and is regularly resynchronized with recent milestones.

All these milestone numbers below highly depend on the given point-in-time. You can find the current milestone of each cws in the EIS database.

You also need to bear in mind that you have to access to the CVS-Server's default port (2401). If a firewall stop's you here you have to setup a CVS-Tunnel.

==== Create a directory for a given milestone, setup CVS access: ====
<code>[bash,N]
mkdir SRC680_m225
cd SRC680_m225
</code>
<code>[bash,N]
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs login
(password is 'anoncvs' ) + Enter
</code>
<code>[bash,N]
Note: The source should be downloaded to a path that does not contain any spaces, otherwise compiling might be troublesome.
</code>

==== checkout SRC680 (Master workspace since aquavcl01 integration) (1,5 GB): ====
<code>[N]
cvs -z3 co -r SRC680_m225 OpenOffice2
</code>
Once done, you'll obtain milestone 225.

==== checkout Aquavcl03 (50 MB): ====

SRC680_m225 is not exactly what we want, because all changes concerning aquavcl02 Child workspace are included, but not the last changes, now in aquavcl03. To complete, we need to check aquavcl03 changes.

1) First possibility: create a dedicated tree (cool backup)

To check aquavcl03 Child workspace, the most simple is to create aquavcl03 directory, and go inside this dir
<code>[bash,N]
mkdir aquavcl03-src

cd aquavcl03-src
</code>
(assuming you already did cvs login, and typing all the command line below in one line)

<code>[bash,N]

cvs -z3 co -r cws_src680_aquavcl03 desktop instsetoo_native solenv vcl
</code>

All the modules listed above will be present at the end ( everyone represents a new directory ) and they are the ones we modified to create the native version.

To verify nothing's wrong, all are tagged "aquavcl03" (see all CVS/Tag files in the tree) and all you have to do is either rename or delete the one located in SRC680_m225 and replace them with the one located in aquavcl03-src.

e.g. : vcl in SRC680_m225 will become vcl_m225 , and then, cp vcl from aquavcl03-src into src_m225

This applies for all the modules listed above.

2) Second possibility: use a little script to extract changes: extract_aquavcl03.sh

This shell script, located in SRC680_m225 will contain:
<code>[bash,N]
#!/bin/bash
list="desktop instsetoo_native solenv vcl"
for i in $list ; do
mv ${i} ${i}_m225
cvs -z3 co -r cws_src680_aquavcl03 $i
done
</code>

Then chmod +x extract_aquavcl03.sh

and run it:

./extract_aquavcl03.sh

When finished, and if no problem occurs, you should have a complete tree of aquavcl03.

=== One-Time preparations and scripts ===

OpenOffice.org's build environment is configured using the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
SRC680_m182/
SRC680_m196/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd SRC680_m225/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' (to be written) looks like :

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version: $OOVERSION
./configure \
--with-lang="de en-US" \
--with-jdk-home=/Library/Java/Home/ \
--with-epm=internal \
--disable-mozab \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-headless \
--disable-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--without-nas
</code>

Note : --disable-neon has been removed since m217 resync. See issue : [[http://qa.openoffice.org/issues/show_bug.cgi?id=78206 --disable-neon breaks aqua build]]

--disable-odk : disables SDK build, and will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

This is allowedly a pretty much limited setup for now, but it will progressively change, with the progress we'll do with Aqua port.

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd SRC680_m225/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

=== Mac Intel ===

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
cd instsetoo_native

build --all -P4 --dlv_switch -link --dontgraboutput

or

build --all -P4

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360 | issue 77360])

=== On PowerPC ===

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
cd instsetoo_native

build --all -P2 --dlv_switch -link --dontgraboutput

or

build --all -P2

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360|issue 77360])

The main purpose of the '''bootstrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set' should be substituted with 'MacOSXX86Env.Set'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours, and 3 to 6 hours on Mac Intel (3:30h on a 2GHz DualCore INTEL iMac). Be patient.

If you want to see how the progress on that build is you can use two '''build''' options to get a comfortable view:

build ... <see above> ... --html --html_path /Users/$USER/Sites

where $USER is your user name. Then you can load in Firefox (not Safari!) the HTML file '''unxmacxi.pro.build.html''' via the in Mac OS X included Apache web server or diretctly form the directory ''/Users/$USER/Sites/''. This file is automatically being updated and is showing the status of the build and also the time needed since the build started.

== '''Installing, preparing and running OpenOffice.org''' ==

===''' Find the Bundle''' ===

Once the build completed, the Final product ( en-US version ) is named : OpenOffice.org-2.3.0_en-US.dmg ( for version 2.3.0 e.g.)

And is located in instsetoo_native/unxmacxi.pro/OpenOffice/install/en-US directory ( replace en-US with your locale )

[[Image:Bundle_location.jpg]]

<br><br>

=== '''Run the soffice.bin''' ===

In one line :

<big>'''Double click the .dmg , drag the OpenOffice.org icon in the folder you want, and double click to run it !!'''</big>

Note : soffice.bin leads XCode to not work (because of the dot in the name). The issue has been reported to xcode-users list.

We're nearly through, let's fire-off the binary:

But a lot has to be done, and if you want to trace (using gdb e.g.), just do:

cd <INSTALL_DIR>/OpenOffice.org\ 2.3.app/Contents/MacOS

and run:

gdb --args soffice.bin

(add any breakpoint you want)

r to run OpenOffice.org

=== Use vcl menubar and / or vcl menus ===

Native menus are defaults. If you want to use vcl menus, do:

<pre>
AQUA_NATIVE_MENUS=FALSE ./soffice.bin
</pre>

Note: options to not recover is -norestore , and to bypass the user informations to fill in, use -nofirststartwizard

AQUA_NATIVE_MENUS=FALSE ./soffice.bin -nofirststartwizard -norestore

You can also insert environement variables in a Dictionary Class of Info.plist located in the Contents directory of OpenOffice.org bundle.

For example, you can add the following XML in a text editor (or make it generated by Property List Editor) in your Info.plist :

<key>LSEnvironment</key>
<dict>
<key>AQUA_NATIVE_MENUS</key>
<string>TRUE</string>
<key>OOO_DISABLE_RECOVERY</key>
<string>TRUE</string>
<key>SAL_NO_NWF</key>
<string>TRUE</string>
<dict>

Notice that in order to work, the OOO_DISABLE_RECOVERY variable detection must be manually inserted in OOo code using the following patch :
http://www.go-oo.org/patches/src680/disable-recovery.diff

This patch is outdated, but you can make the modifications yourself.

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="15" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=FALSE || disable native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

== '''Debug and contribute ''' ==
<ul>
<li>You want to provide crash issue details? Please see [[Providing_a_gdb_backtrace]]</li>
<li>You want to debug using XCode? Please see [[MacOSX_Debug_OpenOffice.org_using_XCode]]</li>
<li>You want to debug using Xemacs? Please see [http://www.mikesicotte.com/2007/02/21/debugging-ooo-with-xemacs-and-gdb Michael Sicotte's blog entry]</li>
</ul>

== '''Want to add a module into aquavcl03 cws ?''' ==

If you have changes and/or modifications in another module, a developer with correct rights will add it in the list.

<div align="left" style="color:red; font-size:16px">'''See [[AquaPortCocoa]] for more informations'''</div>

=== Important links or Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

== '''List of Patches requiring testing before for integration''' ==

Developers are working on the following Child workspaces (Mac OSX dedicated) :

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, vcl

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''aquaremovescripts''' (soon) :

concerned module: instsetoo_native

*'''readme4macintel''' :

concerned module : readlicense_oo

Work in progress: Drag and Drop , native spellchecker ( stay tuned )

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

Since latest resync, no build issues have been reported.

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

Documentation/Building Guide/Building on MacOSX

2007-08-21T18:58:33Z

Maveric: /* One-Time preparations and scripts */

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

==== Mac OS X version ====

=> '''Minimal version for AquaBuild is Mac OS X 10.4 ( aka Tiger ).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

==== Xcode ====

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''

If you really cannot use XCode 2.4.1 nor XCode 2.4:

Xcode 2.2, 2.3 are known to work for Aqua development. If any earlier versions work as well, please add them here.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xlib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

<pre>This issue should be fixed soon.</pre>

==== Java ====

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build OpenOffice.org several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.

You can install it using fink. It is simply named "ccache". For MacPorts users the package is called "ccache".

If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/

In order to use ccache you need to change the following environment variables '''assuming you're using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

<div align="left" style="color:grey; font-size:18px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''Getting the code (checkout, merge and patch the puppy)''' ==

Two possibilities : either build Carbon version, and test the (soon) alpha version, or build Cocoa version and help us for the development.

Work in progress: a cws named aquavclcarbonfixes, based on milestone m225, concerning Top 5 of issues before Alpha is in progress.

The main changes will concern vcl, and desktop ( to add the native progressbar for the splashscreen).

-> Stay tuned

<big>'''If you want to to contribute on the development, please note that aquavcl03 is dedicated to our Carbon -> Cocoa migration.

So many things that worked before may be broken since that migration is not yet complete.'''</big>

<div align="left" style="color:blue; font-size:18px">'''For Carbon version, you'll need to (in the described order):'''</div>

*checkout m225 source code. For that, see :
** [[AquaBuild#Create_a_directory_for_a_given_milestone.2C_setup_CVS_access:| create a directory for OpenOffice.org sources]]
** [[AquaBuild#checkout_SRC680_.28Master_workspace_since_aquavcl01_integration.29_.281.2C5_GB.29:| Checkout the sources]]
* Jump into [[AquaBuild#One-Time_preparations_and_scripts]] section and build OpenOffice.org (the important is in the configure command line)

<div align="left" style="color:red; font-size:18px">'''For Cocoa version'''</div>

Now, all the changes are commited in aquavcl03, and all what you have to do is :

- checkout m225 source code

- checkout aquavcl03 modules.

Currently : <div align="left" style="color:blue">'''instsetoo_native, solenv and vcl'''</div>

Note: if you want to add a new module, have a look at [[AquaBuild#Want_to_add_a_module_into_aquavcl03_cws_.3F]] section.

aquavcl03 cws does use SRC680 master workspace, and is regularly resynchronized with recent milestones.

All these milestone numbers below highly depend on the given point-in-time. You can find the current milestone of each cws in the EIS database.

You also need to bear in mind that you have to access to the CVS-Server's default port (2401). If a firewall stop's you here you have to setup a CVS-Tunnel.

==== Create a directory for a given milestone, setup CVS access: ====
<code>[bash,N]
mkdir SRC680_m225
cd SRC680_m225
</code>
<code>[bash,N]
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs login
(password is 'anoncvs' ) + Enter
</code>
<code>[bash,N]
Note: The source should be downloaded to a path that does not contain any spaces, otherwise compiling might be troublesome.
</code>

==== checkout SRC680 (Master workspace since aquavcl01 integration) (1,5 GB): ====
<code>[N]
cvs -z3 co -r SRC680_m225 OpenOffice2
</code>
Once done, you'll obtain milestone 225.

==== checkout Aquavcl03 (50 MB): ====

SRC680_m225 is not exactly what we want, because all changes concerning aquavcl02 Child workspace are included, but not the last changes, now in aquavcl03. To complete, we need to check aquavcl03 changes.

1) First possibility: create a dedicated tree (cool backup)

To check aquavcl03 Child workspace, the most simple is to create aquavcl03 directory, and go inside this dir
<code>[bash,N]
mkdir aquavcl03-src

cd aquavcl03-src
</code>
(assuming you already did cvs login, and typing all the command line below in one line)

<code>[bash,N]

cvs -z3 co -r cws_src680_aquavcl03 desktop instsetoo_native solenv vcl
</code>

All the modules listed above will be present at the end ( everyone represents a new directory ) and they are the ones we modified to create the native version.

To verify nothing's wrong, all are tagged "aquavcl03" (see all CVS/Tag files in the tree) and all you have to do is either rename or delete the one located in SRC680_m225 and replace them with the one located in aquavcl03-src.

e.g. : vcl in SRC680_m225 will become vcl_m225 , and then, cp vcl from aquavcl03-src into src_m225

This applies for all the modules listed above.

2) Second possibility: use a little script to extract changes: extract_aquavcl03.sh

This shell script, located in SRC680_m225 will contain:
<code>[bash,N]
#!/bin/bash
list="desktop instsetoo_native solenv vcl"
for i in $list ; do
mv ${i} ${i}_m225
cvs -z3 co -r cws_src680_aquavcl03 $i
done
</code>

Then chmod +x extract_aquavcl03.sh

and run it:

./extract_aquavcl03.sh

When finished, and if no problem occurs, you should have a complete tree of aquavcl03.

=== One-Time preparations and scripts ===

OpenOffice.org's build environment is configured using the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
SRC680_m182/
SRC680_m196/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd SRC680_m225/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' (to be written) looks like :

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version: $OOVERSION
./configure \
--with-lang="de en-US" \
--with-jdk-home=/Library/Java/Home/ \
--with-epm=internal \
--disable-mozab \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-headless \
--disable-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--without-nas
</code>

Note : --disable-neon has been removed since m217 resync. See issue : [[http://qa.openoffice.org/issues/show_bug.cgi?id=78206 --disable-neon breaks aqua build]]

--disable-odk : disables SDK build, and will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

This is allowedly a pretty much limited setup for now, but it will progressively change, with the progress we'll do with Aqua port.

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd SRC680_m225/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

=== Mac Intel ===

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
cd instsetoo_native

build --all -P4 --dlv_switch -link --dontgraboutput

or

build --all -P4

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360 | issue 77360])

=== On PowerPC ===

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
cd instsetoo_native

build --all -P2 --dlv_switch -link --dontgraboutput

or

build --all -P2

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360|issue 77360])

The main purpose of the '''bootstrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set' should be substituted with 'MacOSXX86Env.Set'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours, and 3 to 6 hours on Mac Intel (3:30h on a 2GHz DualCore INTeL iMac). Be patient.

If you want to see how the progress on that build is you can use two '''build''' options to get a comfortable view:

build ... <see above> ... --html --html_path /Users/$USER/Sites

where $USER is your user name. Then you can load in Firefox (not Safari!) the HTML file '''unxmacxi.pro.build.html''' via the in Mac OS X included Apache web server or diretctly form the directory ''/Users/$USER/Sites/''. This file is automatically being updated and is showing the status of the build and also the time needed since the build started.

== '''Installing, preparing and running OpenOffice.org''' ==

===''' Find the Bundle''' ===

Once the build completed, the Final product ( en-US version ) is named : OpenOffice.org-2.3.0_en-US.dmg ( for version 2.3.0 e.g.)

And is located in instsetoo_native/unxmacxi.pro/OpenOffice/install/en-US directory ( replace en-US with your locale )

[[Image:Bundle_location.jpg]]

<br><br>

=== '''Run the soffice.bin''' ===

In one line :

<big>'''Double click the .dmg , drag the OpenOffice.org icon in the folder you want, and double click to run it !!'''</big>

Note : soffice.bin leads XCode to not work (because of the dot in the name). The issue has been reported to xcode-users list.

We're nearly through, let's fire-off the binary:

But a lot has to be done, and if you want to trace (using gdb e.g.), just do:

cd <INSTALL_DIR>/OpenOffice.org\ 2.3.app/Contents/MacOS

and run:

gdb --args soffice.bin

(add any breakpoint you want)

r to run OpenOffice.org

=== Use vcl menubar and / or vcl menus ===

Native menus are defaults. If you want to use vcl menus, do:

<pre>
AQUA_NATIVE_MENUS=FALSE ./soffice.bin
</pre>

Note: options to not recover is -norestore , and to bypass the user informations to fill in, use -nofirststartwizard

AQUA_NATIVE_MENUS=FALSE ./soffice.bin -nofirststartwizard -norestore

You can also insert environement variables in a Dictionary Class of Info.plist located in the Contents directory of OpenOffice.org bundle.

For example, you can add the following XML in a text editor (or make it generated by Property List Editor) in your Info.plist :

<key>LSEnvironment</key>
<dict>
<key>AQUA_NATIVE_MENUS</key>
<string>TRUE</string>
<key>OOO_DISABLE_RECOVERY</key>
<string>TRUE</string>
<key>SAL_NO_NWF</key>
<string>TRUE</string>
<dict>

Notice that in order to work, the OOO_DISABLE_RECOVERY variable detection must be manually inserted in OOo code using the following patch :
http://www.go-oo.org/patches/src680/disable-recovery.diff

This patch is outdated, but you can make the modifications yourself.

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="15" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=FALSE || disable native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

== '''Debug and contribute ''' ==
<ul>
<li>You want to provide crash issue details? Please see [[Providing_a_gdb_backtrace]]</li>
<li>You want to debug using XCode? Please see [[MacOSX_Debug_OpenOffice.org_using_XCode]]</li>
<li>You want to debug using Xemacs? Please see [http://www.mikesicotte.com/2007/02/21/debugging-ooo-with-xemacs-and-gdb Michael Sicotte's blog entry]</li>
</ul>

== '''Want to add a module into aquavcl03 cws ?''' ==

If you have changes and/or modifications in another module, a developer with correct rights will add it in the list.

<div align="left" style="color:red; font-size:16px">'''See [[AquaPortCocoa]] for more informations'''</div>

=== Important links or Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

== '''List of Patches requiring testing before for integration''' ==

Developers are working on the following Child workspaces (Mac OSX dedicated) :

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, vcl

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''aquaremovescripts''' (soon) :

concerned module: instsetoo_native

*'''readme4macintel''' :

concerned module : readlicense_oo

Work in progress: Drag and Drop , native spellchecker ( stay tuned )

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

Since latest resync, no build issues have been reported.

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

Documentation/Building Guide/Building on MacOSX

2007-08-21T18:50:43Z

Maveric: /* ccache */

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

==== Mac OS X version ====

=> '''Minimal version for AquaBuild is Mac OS X 10.4 ( aka Tiger ).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

==== Xcode ====

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''

If you really cannot use XCode 2.4.1 nor XCode 2.4:

Xcode 2.2, 2.3 are known to work for Aqua development. If any earlier versions work as well, please add them here.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xlib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

<pre>This issue should be fixed soon.</pre>

==== Java ====

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build OpenOffice.org several times, you probably can benefit of ccache since it will speed up your future builds. The first time you make a build with ccache you won't notice it, but the next time the build will go up to five times faster.

You can install it using fink. It is simply named "ccache". For MacPorts users the package is called "ccache".

If you don't use fink, you can download and build it yourself using the source provided at http://ccache.samba.org/

In order to use ccache you need to change the following environment variables '''assuming you're using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

<div align="left" style="color:grey; font-size:18px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''Getting the code (checkout, merge and patch the puppy)''' ==

Two possibilities : either build Carbon version, and test the (soon) alpha version, or build Cocoa version and help us for the development.

Work in progress: a cws named aquavclcarbonfixes, based on milestone m225, concerning Top 5 of issues before Alpha is in progress.

The main changes will concern vcl, and desktop ( to add the native progressbar for the splashscreen).

-> Stay tuned

<big>'''If you want to to contribute on the development, please note that aquavcl03 is dedicated to our Carbon -> Cocoa migration.

So many things that worked before may be broken since that migration is not yet complete.'''</big>

<div align="left" style="color:blue; font-size:18px">'''For Carbon version, you'll need to (in the described order):'''</div>

*checkout m225 source code. For that, see :
** [[AquaBuild#Create_a_directory_for_a_given_milestone.2C_setup_CVS_access:| create a directory for OpenOffice.org sources]]
** [[AquaBuild#checkout_SRC680_.28Master_workspace_since_aquavcl01_integration.29_.281.2C5_GB.29:| Checkout the sources]]
* Jump into [[AquaBuild#One-Time_preparations_and_scripts]] section and build OpenOffice.org (the important is in the configure command line)

<div align="left" style="color:red; font-size:18px">'''For Cocoa version'''</div>

Now, all the changes are commited in aquavcl03, and all what you have to do is :

- checkout m225 source code

- checkout aquavcl03 modules.

Currently : <div align="left" style="color:blue">'''instsetoo_native, solenv and vcl'''</div>

Note: if you want to add a new module, have a look at [[AquaBuild#Want_to_add_a_module_into_aquavcl03_cws_.3F]] section.

aquavcl03 cws does use SRC680 master workspace, and is regularly resynchronized with recent milestones.

All these milestone numbers below highly depend on the given point-in-time. You can find the current milestone of each cws in the EIS database.

You also need to bear in mind that you have to access to the CVS-Server's default port (2401). If a firewall stop's you here you have to setup a CVS-Tunnel.

==== Create a directory for a given milestone, setup CVS access: ====
<code>[bash,N]
mkdir SRC680_m225
cd SRC680_m225
</code>
<code>[bash,N]
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs login
(password is 'anoncvs' ) + Enter
</code>
<code>[bash,N]
Note: The source should be downloaded to a path that does not contain any spaces, otherwise compiling might be troublesome.
</code>

==== checkout SRC680 (Master workspace since aquavcl01 integration) (1,5 GB): ====
<code>[N]
cvs -z3 co -r SRC680_m225 OpenOffice2
</code>
Once done, you'll obtain milestone 225.

==== checkout Aquavcl03 (50 MB): ====

SRC680_m225 is not exactly what we want, because all changes concerning aquavcl02 Child workspace are included, but not the last changes, now in aquavcl03. To complete, we need to check aquavcl03 changes.

1) First possibility: create a dedicated tree (cool backup)

To check aquavcl03 Child workspace, the most simple is to create aquavcl03 directory, and go inside this dir
<code>[bash,N]
mkdir aquavcl03-src

cd aquavcl03-src
</code>
(assuming you already did cvs login, and typing all the command line below in one line)

<code>[bash,N]

cvs -z3 co -r cws_src680_aquavcl03 desktop instsetoo_native solenv vcl
</code>

All the modules listed above will be present at the end ( everyone represents a new directory ) and they are the ones we modified to create the native version.

To verify nothing's wrong, all are tagged "aquavcl03" (see all CVS/Tag files in the tree) and all you have to do is either rename or delete the one located in SRC680_m225 and replace them with the one located in aquavcl03-src.

e.g. : vcl in SRC680_m225 will become vcl_m225 , and then, cp vcl from aquavcl03-src into src_m225

This applies for all the modules listed above.

2) Second possibility: use a little script to extract changes: extract_aquavcl03.sh

This shell script, located in SRC680_m225 will contain:
<code>[bash,N]
#!/bin/bash
list="desktop instsetoo_native solenv vcl"
for i in $list ; do
mv ${i} ${i}_m225
cvs -z3 co -r cws_src680_aquavcl03 $i
done
</code>

Then chmod +x extract_aquavcl03.sh

and run it:

./extract_aquavcl03.sh

When finished, and if no problem occurs, you should have a complete tree of aquavcl03.

=== One-Time preparations and scripts ===

OpenOffice building gets configured by the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
SRC680_m182/
SRC680_m196/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd SRC680_m225/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' (to be written) looks like :

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version: $OOVERSION
./configure \
--with-lang="de en-US" \
--with-jdk-home=/Library/Java/Home/ \
--with-epm=internal \
--disable-mozab \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-headless \
--disable-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--without-nas
</code>

Note : --disable-neon has been removed since m217 resync. See issue : [[http://qa.openoffice.org/issues/show_bug.cgi?id=78206 --disable-neon breaks aqua build]]

--disable-odk : disables SDK build, and will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

This is allowedly a pretty much limited setup for now, but it will progressively change, with the progress we'll do with Aqua port.

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd SRC680_m225/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

=== Mac Intel ===

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
cd instsetoo_native

build --all -P4 --dlv_switch -link --dontgraboutput

or

build --all -P4

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360 | issue 77360])

=== On PowerPC ===

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
cd instsetoo_native

build --all -P2 --dlv_switch -link --dontgraboutput

or

build --all -P2

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360|issue 77360])

The main purpose of the '''bootstrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set' should be substituted with 'MacOSXX86Env.Set'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours, and 3 to 6 hours on Mac Intel (3:30h on a 2GHz DualCore INTeL iMac). Be patient.

If you want to see how the progress on that build is you can use two '''build''' options to get a comfortable view:

build ... <see above> ... --html --html_path /Users/$USER/Sites

where $USER is your user name. Then you can load in Firefox (not Safari!) the HTML file '''unxmacxi.pro.build.html''' via the in Mac OS X included Apache web server or diretctly form the directory ''/Users/$USER/Sites/''. This file is automatically being updated and is showing the status of the build and also the time needed since the build started.

== '''Installing, preparing and running OpenOffice.org''' ==

===''' Find the Bundle''' ===

Once the build completed, the Final product ( en-US version ) is named : OpenOffice.org-2.3.0_en-US.dmg ( for version 2.3.0 e.g.)

And is located in instsetoo_native/unxmacxi.pro/OpenOffice/install/en-US directory ( replace en-US with your locale )

[[Image:Bundle_location.jpg]]

<br><br>

=== '''Run the soffice.bin''' ===

In one line :

<big>'''Double click the .dmg , drag the OpenOffice.org icon in the folder you want, and double click to run it !!'''</big>

Note : soffice.bin leads XCode to not work (because of the dot in the name). The issue has been reported to xcode-users list.

We're nearly through, let's fire-off the binary:

But a lot has to be done, and if you want to trace (using gdb e.g.), just do:

cd <INSTALL_DIR>/OpenOffice.org\ 2.3.app/Contents/MacOS

and run:

gdb --args soffice.bin

(add any breakpoint you want)

r to run OpenOffice.org

=== Use vcl menubar and / or vcl menus ===

Native menus are defaults. If you want to use vcl menus, do:

<pre>
AQUA_NATIVE_MENUS=FALSE ./soffice.bin
</pre>

Note: options to not recover is -norestore , and to bypass the user informations to fill in, use -nofirststartwizard

AQUA_NATIVE_MENUS=FALSE ./soffice.bin -nofirststartwizard -norestore

You can also insert environement variables in a Dictionary Class of Info.plist located in the Contents directory of OpenOffice.org bundle.

For example, you can add the following XML in a text editor (or make it generated by Property List Editor) in your Info.plist :

<key>LSEnvironment</key>
<dict>
<key>AQUA_NATIVE_MENUS</key>
<string>TRUE</string>
<key>OOO_DISABLE_RECOVERY</key>
<string>TRUE</string>
<key>SAL_NO_NWF</key>
<string>TRUE</string>
<dict>

Notice that in order to work, the OOO_DISABLE_RECOVERY variable detection must be manually inserted in OOo code using the following patch :
http://www.go-oo.org/patches/src680/disable-recovery.diff

This patch is outdated, but you can make the modifications yourself.

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="15" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=FALSE || disable native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

== '''Debug and contribute ''' ==
<ul>
<li>You want to provide crash issue details? Please see [[Providing_a_gdb_backtrace]]</li>
<li>You want to debug using XCode? Please see [[MacOSX_Debug_OpenOffice.org_using_XCode]]</li>
<li>You want to debug using Xemacs? Please see [http://www.mikesicotte.com/2007/02/21/debugging-ooo-with-xemacs-and-gdb Michael Sicotte's blog entry]</li>
</ul>

== '''Want to add a module into aquavcl03 cws ?''' ==

If you have changes and/or modifications in another module, a developer with correct rights will add it in the list.

<div align="left" style="color:red; font-size:16px">'''See [[AquaPortCocoa]] for more informations'''</div>

=== Important links or Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

== '''List of Patches requiring testing before for integration''' ==

Developers are working on the following Child workspaces (Mac OSX dedicated) :

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, vcl

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''aquaremovescripts''' (soon) :

concerned module: instsetoo_native

*'''readme4macintel''' :

concerned module : readlicense_oo

Work in progress: Drag and Drop , native spellchecker ( stay tuned )

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

Since latest resync, no build issues have been reported.

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

Documentation/Building Guide/Building on MacOSX

2007-08-21T18:44:38Z

Maveric: /* Java */

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on Mac OS X using the native windowing-toolkit of the platform named Aqua.''' </big>

To give a kickstart in the coding involved to get VCL ported to Carbon, please have a look at the excellent Pierre de Filippis [[Intro To Mac Porting]].

We use the bash shell in all examples, since to our belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html OpenOffice.org Build Environment].

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]].

'''Here we would like to outline the things you need to build the Aqua Version''' (besides the OS).

=== <div align="left" style="color:red; font-size:18px">'''Mandatory'''</div>===

==== Mac OS X version ====

=> '''Minimal version for AquaBuild is Mac OS X 10.4 ( aka Tiger ).'''

Due to important changes in the API, Aqua version cannot be built on Panther.

==== Xcode ====

This is the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is '''XCode 2.4.1'''

If you really cannot use XCode 2.4.1 nor XCode 2.4:

Xcode 2.2, 2.3 are known to work for Aqua development. If any earlier versions work as well, please add them here.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xlib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

<pre>This issue should be fixed soon.</pre>

==== Java ====

Aqua version of OpenOffice.org does not build yet using Java SDK 1.6.0.

'''Please use either J2SDK 1.4.2 or 1.5.0'''

To change -> go into folder : Applications -> Utilities -> Java and modify.

Else, you'll meet unfixed build breakers (patches are welcome anyway)

Note: If you are interested in helping us with Java 1.6 a patch which enables java 1.6 is available [http://eric.bachard.free.fr/mac/aquavcl/patches/aquavcl03_august2007/java1.6/java_1.6_build.diff '''here''']. Be aware that it may impact important work and/or incompatibilities will occur. Feel free to submit your patches at mac@porting mailing list.

=== <div align="left" style="color:blue; font-size:18px">''' Strongly recommended'''</div>===

==== ccache ====
If you intend to build several times OpenOffice, you probably can benefit of ccache. ccache will speed up your future builds. The first time you make a build with ccache you won't notice it, but then the build will go up to five times faster.

You can install it using fink. It is simply named "ccache".

If you don't use fink, you can download it and build it yourself using the source provided at http://ccache.samba.org/

Then, in order to use it, you need to change the following environment variables '''using bash, and just before doing configure command line''':

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

<div align="left" style="color:grey; font-size:18px">[[AquaBuild/Some Background | '''Some Background (what is aquavcl01, EIS) (click me to know more) ''']]</div><br><br>

== '''Getting the code (checkout, merge and patch the puppy)''' ==

Two possibilities : either build Carbon version, and test the (soon) alpha version, or build Cocoa version and help us for the development.

Work in progress: a cws named aquavclcarbonfixes, based on milestone m225, concerning Top 5 of issues before Alpha is in progress.

The main changes will concern vcl, and desktop ( to add the native progressbar for the splashscreen).

-> Stay tuned

<big>'''If you want to to contribute on the development, please note that aquavcl03 is dedicated to our Carbon -> Cocoa migration.

So many things that worked before may be broken since that migration is not yet complete.'''</big>

<div align="left" style="color:blue; font-size:18px">'''For Carbon version, you'll need to (in the described order):'''</div>

*checkout m225 source code. For that, see :
** [[AquaBuild#Create_a_directory_for_a_given_milestone.2C_setup_CVS_access:| create a directory for OpenOffice.org sources]]
** [[AquaBuild#checkout_SRC680_.28Master_workspace_since_aquavcl01_integration.29_.281.2C5_GB.29:| Checkout the sources]]
* Jump into [[AquaBuild#One-Time_preparations_and_scripts]] section and build OpenOffice.org (the important is in the configure command line)

<div align="left" style="color:red; font-size:18px">'''For Cocoa version'''</div>

Now, all the changes are commited in aquavcl03, and all what you have to do is :

- checkout m225 source code

- checkout aquavcl03 modules.

Currently : <div align="left" style="color:blue">'''instsetoo_native, solenv and vcl'''</div>

Note: if you want to add a new module, have a look at [[AquaBuild#Want_to_add_a_module_into_aquavcl03_cws_.3F]] section.

aquavcl03 cws does use SRC680 master workspace, and is regularly resynchronized with recent milestones.

All these milestone numbers below highly depend on the given point-in-time. You can find the current milestone of each cws in the EIS database.

You also need to bear in mind that you have to access to the CVS-Server's default port (2401). If a firewall stop's you here you have to setup a CVS-Tunnel.

==== Create a directory for a given milestone, setup CVS access: ====
<code>[bash,N]
mkdir SRC680_m225
cd SRC680_m225
</code>
<code>[bash,N]
export CVSROOT=":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs login
(password is 'anoncvs' ) + Enter
</code>
<code>[bash,N]
Note: The source should be downloaded to a path that does not contain any spaces, otherwise compiling might be troublesome.
</code>

==== checkout SRC680 (Master workspace since aquavcl01 integration) (1,5 GB): ====
<code>[N]
cvs -z3 co -r SRC680_m225 OpenOffice2
</code>
Once done, you'll obtain milestone 225.

==== checkout Aquavcl03 (50 MB): ====

SRC680_m225 is not exactly what we want, because all changes concerning aquavcl02 Child workspace are included, but not the last changes, now in aquavcl03. To complete, we need to check aquavcl03 changes.

1) First possibility: create a dedicated tree (cool backup)

To check aquavcl03 Child workspace, the most simple is to create aquavcl03 directory, and go inside this dir
<code>[bash,N]
mkdir aquavcl03-src

cd aquavcl03-src
</code>
(assuming you already did cvs login, and typing all the command line below in one line)

<code>[bash,N]

cvs -z3 co -r cws_src680_aquavcl03 desktop instsetoo_native solenv vcl
</code>

All the modules listed above will be present at the end ( everyone represents a new directory ) and they are the ones we modified to create the native version.

To verify nothing's wrong, all are tagged "aquavcl03" (see all CVS/Tag files in the tree) and all you have to do is either rename or delete the one located in SRC680_m225 and replace them with the one located in aquavcl03-src.

e.g. : vcl in SRC680_m225 will become vcl_m225 , and then, cp vcl from aquavcl03-src into src_m225

This applies for all the modules listed above.

2) Second possibility: use a little script to extract changes: extract_aquavcl03.sh

This shell script, located in SRC680_m225 will contain:
<code>[bash,N]
#!/bin/bash
list="desktop instsetoo_native solenv vcl"
for i in $list ; do
mv ${i} ${i}_m225
cvs -z3 co -r cws_src680_aquavcl03 $i
done
</code>

Then chmod +x extract_aquavcl03.sh

and run it:

./extract_aquavcl03.sh

When finished, and if no problem occurs, you should have a complete tree of aquavcl03.

=== One-Time preparations and scripts ===

OpenOffice building gets configured by the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
SRC680_m182/
SRC680_m196/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd SRC680_m225/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' (to be written) looks like :

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version: $OOVERSION
./configure \
--with-lang="de en-US" \
--with-jdk-home=/Library/Java/Home/ \
--with-epm=internal \
--disable-mozab \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-headless \
--disable-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--without-nas
</code>

Note : --disable-neon has been removed since m217 resync. See issue : [[http://qa.openoffice.org/issues/show_bug.cgi?id=78206 --disable-neon breaks aqua build]]

--disable-odk : disables SDK build, and will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

This is allowedly a pretty much limited setup for now, but it will progressively change, with the progress we'll do with Aqua port.

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd SRC680_m225/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

=== Mac Intel ===

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
cd instsetoo_native

build --all -P4 --dlv_switch -link --dontgraboutput

or

build --all -P4

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360 | issue 77360])

=== On PowerPC ===

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
cd instsetoo_native

build --all -P2 --dlv_switch -link --dontgraboutput

or

build --all -P2

if you run into trouble with --dlv_switch (see: [http://qa.openoffice.org/issues/show_bug.cgi?id=77360|issue 77360])

The main purpose of the '''bootstrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set' should be substituted with 'MacOSXX86Env.Set'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours, and 3 to 6 hours on Mac Intel (3:30h on a 2GHz DualCore INTeL iMac). Be patient.

If you want to see how the progress on that build is you can use two '''build''' options to get a comfortable view:

build ... <see above> ... --html --html_path /Users/$USER/Sites

where $USER is your user name. Then you can load in Firefox (not Safari!) the HTML file '''unxmacxi.pro.build.html''' via the in Mac OS X included Apache web server or diretctly form the directory ''/Users/$USER/Sites/''. This file is automatically being updated and is showing the status of the build and also the time needed since the build started.

== '''Installing, preparing and running OpenOffice.org''' ==

===''' Find the Bundle''' ===

Once the build completed, the Final product ( en-US version ) is named : OpenOffice.org-2.3.0_en-US.dmg ( for version 2.3.0 e.g.)

And is located in instsetoo_native/unxmacxi.pro/OpenOffice/install/en-US directory ( replace en-US with your locale )

[[Image:Bundle_location.jpg]]

<br><br>

=== '''Run the soffice.bin''' ===

In one line :

<big>'''Double click the .dmg , drag the OpenOffice.org icon in the folder you want, and double click to run it !!'''</big>

Note : soffice.bin leads XCode to not work (because of the dot in the name). The issue has been reported to xcode-users list.

We're nearly through, let's fire-off the binary:

But a lot has to be done, and if you want to trace (using gdb e.g.), just do:

cd <INSTALL_DIR>/OpenOffice.org\ 2.3.app/Contents/MacOS

and run:

gdb --args soffice.bin

(add any breakpoint you want)

r to run OpenOffice.org

=== Use vcl menubar and / or vcl menus ===

Native menus are defaults. If you want to use vcl menus, do:

<pre>
AQUA_NATIVE_MENUS=FALSE ./soffice.bin
</pre>

Note: options to not recover is -norestore , and to bypass the user informations to fill in, use -nofirststartwizard

AQUA_NATIVE_MENUS=FALSE ./soffice.bin -nofirststartwizard -norestore

You can also insert environement variables in a Dictionary Class of Info.plist located in the Contents directory of OpenOffice.org bundle.

For example, you can add the following XML in a text editor (or make it generated by Property List Editor) in your Info.plist :

<key>LSEnvironment</key>
<dict>
<key>AQUA_NATIVE_MENUS</key>
<string>TRUE</string>
<key>OOO_DISABLE_RECOVERY</key>
<string>TRUE</string>
<key>SAL_NO_NWF</key>
<string>TRUE</string>
<dict>

Notice that in order to work, the OOO_DISABLE_RECOVERY variable detection must be manually inserted in OOo code using the following patch :
http://www.go-oo.org/patches/src680/disable-recovery.diff

This patch is outdated, but you can make the modifications yourself.

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="15" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=FALSE || disable native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

== '''Debug and contribute ''' ==
<ul>
<li>You want to provide crash issue details? Please see [[Providing_a_gdb_backtrace]]</li>
<li>You want to debug using XCode? Please see [[MacOSX_Debug_OpenOffice.org_using_XCode]]</li>
<li>You want to debug using Xemacs? Please see [http://www.mikesicotte.com/2007/02/21/debugging-ooo-with-xemacs-and-gdb Michael Sicotte's blog entry]</li>
</ul>

== '''Want to add a module into aquavcl03 cws ?''' ==

If you have changes and/or modifications in another module, a developer with correct rights will add it in the list.

<div align="left" style="color:red; font-size:16px">'''See [[AquaPortCocoa]] for more informations'''</div>

=== Important links or Cocoa development ===

[http://www.cocoadev.com Cocoadev ]

[http://ktd.club.fr/programmation/objective-c.php Pierre Chatelier page about C++ to Cocoa conversion ]

Note: .pdf available in both english and french versions. Excellent.

== '''List of Patches requiring testing before for integration''' ==

Developers are working on the following Child workspaces (Mac OSX dedicated) :

*'''aquavclcarbonfixes''' ( Carbon version of Aqua OpenOffice.org ): fix the 5 most important issues.

concerned modules are : desktop, vcl

*'''aquavcl03''' ( Carbon -> Cocoa migration )

concerned modules are desktop, instsetoo_native, solenv, vcl

*'''macaddressbook01''' (QA in progress )

concerned modules are : scp2, dbaccess, extensions, connectivity

*'''aquaremovescripts''' (soon) :

concerned module: instsetoo_native

*'''readme4macintel''' :

concerned module : readlicense_oo

Work in progress: Drag and Drop , native spellchecker ( stay tuned )

Integrated in m223:

*'''aquavcl02'''

Integrated in m222 :

*'''aquaremovefondu'''

*macosxdmg23

Integrated in m221:

*'''aquafilepicker01'''

All patches that developers have that need testing or peer review should be added here.

== '''Known build issues '''==

Since latest resync, no build issues have been reported.

== '''External links''' ==

# [http://www.openoffice.org/issues/query.cgi Bug Database]
# Mailinglist: [http://porting.openoffice.org/servlets/ProjectMailingListList mac@porting.openoffice.org] (subscribe is mandatory )
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Sebastien Plisson Wiki: http://splisson.blogspot.com/
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== '''Screenshots''' ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue): http://blog.janik.cz/images/MacOSX/ => See: OOoMenus-separator-and-disabled_entries.png
# Aqua look (the begining):
http://eric.bachard.free.fr/mac/aquavcl/screenshots/mars2007/combobox_search_and_replace02_14mars07.jpg

More menus: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]
[[Category:Build_System]]

DE/2.2.1 Release Test

2007-06-12T16:00:20Z

Maveric: /* Testmatrix */

[[Category:de.openoffice.org|Release Test 2.2.1]]
Diese Seite dient der Koordination der Release-Tests der deutschsprachigen 2.2.1 Version.

Die Tests sollen der Freigabe der deutschsprachigen Pakete von OpenOffice.org 2.2.1 dienen.

Der Freigabetest wird anhand des Release-Sanity Scenarios im TCM durchgeführt.
Zum Test werden die regulären RC's für die jeweilige Plattform verwendet:
* [http://download.openoffice.org/680/ SUN-Builds] Windows, Linux x86 RPM, Solaris - Verzeichnisse 2.2.1rc* .
* [ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/ Pavels builds] Linux x86 deb - Verzeichnisse OOF680_m17 und höher.
* [ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/ Mahos builds] Mac OS X x86 und PPC - Verzeichnisse .
* [ftp://ooopackages.good-day.net/pub/OpenOffice.org/FreeBSD/ Jacks builds] FreeBSD 5 und 6 - Verzeichnisse .

Werden Fehler oder Probleme aufgedeckt, sollten unbedingt entsprechende Issues gesucht und ggf. neu erfasst werden. Diese sollten dann im TCM bei dem Testfall hinterlegt werden, bei dem das Problem entdeckt wurde.
Bei Problemen unbedingt auf der QA Liste melden. Gefundene Fehler sollten im Zweifelsfall auch dort diskutiert werden.
Bei Problemen mit Issuezilla (z.B. ungenügende Kenntnisse beim Aufgeben von Issues) ebenfalls auf der QA-Liste melden. André Schnabel kümmert sich dann um die Bearbeitung der Issues.

Um bei den Tests mithelfen zu können, wird ein TCM-Account benötigt. Bei Interesse wendet euch bitte an qa@de.openoffice.org

= Informationen und Links =

* [http://de.openoffice.org/about-ooo/about_tcm.html Über TCM]
* [http://www.sunvirtuallab.com/tcm2/opensource/tcm_login.cgi?tcm_config=newooo TCM Login]

= Testmatrix =
wer macht welche Tests - es werden folgende Markierungen verwendet:
* <span style="color: #a0a0a0">grau</span> - Test noch nicht zugeteilt
* normal - zum Testen eingeteilt / Test in Arbeit
* ''kursiv'' - Test mit unkritischen Fehlern bestanden
* '''fett''' - Test ohne Fehler bestanden
* '''''fett-kursiv''''' - Test mit kritischen Fehlern fehlgeschlagen

{| border="1" cellpadding="2"
|-
! Plattform
! Tester !! Ergebnis
|-
! Mac( PPC)
|| torwart <br/> lomograf <br /> cloph || T:28, P:19, F:6, S:3 (RC2)<br />---<br /> ----
|-
! Mac( x86)
|| '''fein(RC3)''' <br /> michaelkoechling <br /> ''maveric''|| <br /> <br /> ok
|-
! PowerPC(Linux)
|| ||

|-
! Sparc(Solaris10)
|| ||

|-
! Sparc(Solaris8)
|| ||
|-
! Sparc(Solaris9)
|| ||

|-
! x86(FreeBSD5.3)
|| ||

|-
! x86(Linux/deb)
||''mechtilde''||ok
|-
! x86(Linux/RPM)
||''SimonAW''<br /> cloph<br />andreasma||T:28, P:21, F:4, S:3<br />n/A<br /> n/A
|-
! x86(Linux/JDS3)
|| ||

|-
! x86(Solaris10)
|| axxl <br /> markomlm ||

|-
! X86(Solaris9)
|| ||

|-
! x86(Win2003)
|| ||

|-
! x86(Win2K)
|| volkerme || Installation und Basisfunktionalität ok

|-
! x86(Win98)
|| volkerme || Installation und Basisfunktionalität ok

|-
! x86(WinME)
|| ||

|-
! x86(WinXP)
||jrahemipour <br /> epix || autom. Tests u. manuelle Tests ok

|-
! x86(WinVista)
|| ||
|}

= Zusatzaufgaben =

== Issues verifizieren ==

Folgende Issues sind für OOo 2.2.1 geplant, aber noch nicht geschlossen. Diese sollten aufgearbeitet werden:

* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&target_milestone=OOo+2.2.1&Submit+query=Submit+query zu verifizierende Issues]

Vorgehen:
* einen Issue hernehmen (am besten, einen, mit dem man bereits zu tun hatte)
* prüfen, ob er tatsächlich gefixt ist ('''nur Issues bearbeiten, bei denen man sicher ist, das Problem zu verstehen''')
* wenn ja -> Status auf "Closed" wechseln (Mark Issue as Closed)
* wenn nein -> Issue wieder öffnen (reopen issue) und target auf 2.x ändern
* jeweils einen Kommentar hinterlassen, mit welcher Version (RC x) geprüft wurde und welche Probleme evtl. noch beobachtet wurden

Sonst keine Änderungen vornehmen .. auch keine Diskussionen, dass man den Fehler lieber anders gefixt haben möchte, oder dass es im Umfeld noch weitere Probleme gibt. Sollte das der Fall sein, einen neuen Issue aufgeben.

Documentation/Building Guide/Building on MacOSX

2007-02-12T08:32:37Z

Maveric:

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on MacOS X using the native windowing-toolkit of the platform named Aqua.''' </big>

An important goal is to get the demonstration programs "svdem" up and running. They act as a fairly good starting point to further endeavours, since they are used to test the capabilities of the underlying [[VCL]] layer. If this is achieved, one can build and Install the full-fledged OpenOffice.org Package. The purpose of this document is to describe the cumbersome build process of OpenOffice.org rather than to give a kickstart in the coding involved to get VCL ported to Carbon. A starting point for this is Pierre de Filippis excellent [[Intro To Mac Porting]].

I use the bash shell in all examples, since to my belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html Open OfficeBuild Environment].

Many thanks for help and assistance go to Pavel Janik and Eric Bachard.

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]]. Here I like to outline the things you need to build the Aqua Version (besides the OS).

=== Mandatory ===

==== Xcode ====

This is (with GNU cp, soon optional) the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is XCode 2.4.

Xcode 2.2, 2.3 are known to work for Aqua development. If any earlier versions work as well, please add them here.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xllib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

'''Workaround''' : XCode does contain Xlib headers. Just modify INCLUDE path properly will solve the build issue.

Meant replace ( not existing)
/usr/X11R6/include

with (existing) : /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/include

Doing a symlink between them :
<code>
If X11 and /or X11SDK is(are) not installed :
sudo mkdir -p /usr/X11R6

sudo ln -s /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/include /usr/X11R6/include
</code>

<pre>This issue should be fixed soon.</pre>

=== Strongly recommended ===

==== ccache ====
If you intend to build several times OpenOffice, you probably can benefit of ccache. ccache will speed up your future builds. The first time you make a build with ccache you won't notice it, but then the build will go up to five times faster.

You can install it using fink. It is simply named "ccache".

If you don't use fink, you can download it and build it yourself using the source provided at http://ccache.samba.org/

Then, in order to use it, you need to change the following environment variables (using bash) :

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

=== Optional ===

==== Java ====

Normally installed with XCode.

==== The perl module Archive::Zip ( optional ) ====

Nothing is needed anymore with recent versions of XCode (means : not needed with XCode 2.4 at least).

If you still have issues doing configure because of that, please install Archive::Zip repecting the instructions below :

<code>[bash,N]
perl -MCPAN -eshell
install Archive::Zip
</code>

==== gpc ( optional) ====
GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>
Attention: Direct Link to the download but it's only a few hundred KB.
Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

==== pkg-config (optional) ====

Nothing to install on Aqua build, since --disable-gtk is forced

Called ''pkgconfig'' in Fink.

pkg-config can be found here : http://pkgconfig.freedesktop.org/wiki/

== '''Some Background (what is aquavcl01, EIS)''' ==

=== EIS ===
OpenOffice sources are basically kept in the CVS server located at anoncvs.services.openoffice.org. However this repository is managed by a database on top called EIS (Environment Information System) which is used to keep track of Master- and Client Workspaces. Master Workspaces are used to keep track of changes going back of the mainline trunk and undergo extensive QA-cycles. These Master Workspaces are driven to official releases. Child workspaces in contrast are copies of certain Master Workspaces used to develop and test bugfixes and additional functionality. These Child Workspaces are later (hopefully) merged back to mainlain Master Workspaces. The TX20 Report mentioned in the Links section gives a very good overview about the overall process. To learn more about Childworkspaces (CWS) have a look here: [[CWS]].

Go to EIS http://eis.services.openoffice.org/EIS2/servlet/Logon and Logon as guest/guest to get yourself an impression. You can find information about the different workspaces, their dates and times there.

=== VCL (Visual Class Libraries) ===

Porting OpenOffice.org to a new Windowing Toolkit is mostly porting of the OpenOffice's VCL Layer (Visual Class Libraries) to the new platforms toolkit. The VCL-Layer is responsible of mapping the OpenOffice Application calls to the windowing toolkit.

The (native) OpenOffice port to MacOSX using the Aqua Windowing Toolkit is developed in a child workspace called '''aquavcl01'''. This child workspace consists of the modules (aka subdirs): canvas dtrans extensions freetype padmin scp2 sj2 solenv vcl.

The basic approach to prepare a developer's client system to successfully build OpenOffice/Aqua is the following:

# checkout a given OpenOffice Milestone.
# checkout aquavcl01 Child Workspace.
# merge them together.
# apply the latest patches.

The last point here is a cumbersome but nevertheless necessary operation, since this porting project is in flux. Thanks to Pavel and many others improvements are happening at tremendous pace at the moment. All of these improvements get distributed as patches/diffs against aquavcl01. Aquavcl01 needs to remain stable all the time, therefore the team needs to work on this patch-by-patch aproach at the moment.

== '''Getting the code (checkout, merge and patch the puppy)''' ==

Now let's have a look what to check-out and where. All these milestone numbers below highly depend on the given point-in-time. The current milestone as of now (February 2nd 2007) is m202. You may change this to your needs. You can find the current milestone of each cws in the EIS database.

You also need to bear in mind that you have to access to the CVS-Server's default port (2401). If a firewall stop's you here you have to setup a CVS-Tunnel.

==== create a directory for a given milestone, setup CVS access: ====
<code>[bash,N]
mkdir src680-m202
cd src680-m202

export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
cvs login
</code>
Please Enter the password 'anoncvs'

==== checkout Milestone m202 (1,5 GB): ====
<code>[bash,N]
cvs -z3 co -r SRC680_m202 OpenOffice2
</code>
Once done, you'll obtain milestone 202. this not exactly what we want, because all changes concerning aquavcl01 Child workspace are not included. To complete, we need to check aquavcl01 changes.

==== checkout Aquavcl01 (50 MB): ====

1) First possibility : create a dedicated tree (cool backup )

To check aquavcl01 Child workspace, the most simple is to create aquavcl01 directory, and go inside this dir
<code>[bash,N]
mkdir aquavcl01-src

cd aquavcl01-src
</code>
(assuming you already did cvs login ..etc )
<code>[bash,N]
cvs -z3 co -r cws_src680_aquavcl01 OpenOffice2
</code>
The following modules will be present at the end :
<div style="background-color: lightyellow; border: 1px red dashed; padding: 3px 0 3px 15px;">
canvas

extensions

fpicker

padmin

sal

scp2

sfx2

solenv

dtrans

freetype

psprint

sj2

vcl

toolkit
</div>

All these modules are the ones we modified to create the native version : they all are tagged "aquavcl01" (see all CVS/Tag files in the tree) and all you have to do is either rename or delete the one located in src680-m202 and replace them with the one located in aquavcl01-src.

e.g. : canvas in src680-m202 will become canvas_m202 , and then, cp canvas from aquavcl01-src into src-m202

This applies for all the modules listed above.

2) Second possibility : use a little script to extract changes : extract_aquavcl01.sh

This shell script, located in src680-m202 will contain :
<code>[bash,N]
#!/bin/bash
list="canvas extensions fpicker padmin scp2 sfx2 solenv dtrans freetype psprint sj2 vcl sal toolkit"
for i in $list ; do
mv $i $i-m202
cvs -z3 co -r cws_src680_aquavcl01 $i
done
</code>

Then chmod +x extract_aquavcl01.sh

and run it :

./extract_aquavcl01.sh

When finished, and if no problem occurs, you should have a complete tree.

=== One-Time preparations and scripts ===

OpenOffice building gets configured by the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
src680-m182/
src680-m196/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd src680-m202/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' looks like:

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version : $OOVERSION
./configure \
--with-lang="de en-US" \
--with-jdk-home=/Library/Java/Home/ \
--with-gnu-cp=/sw/bin/cp \
--with-epm=internal \
--disable-mozab \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--disable-neon \
--without-nas
</code>

--disable-odk will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--without-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

This is allowedly a pretty much limited setup, but my overall goal is to get people to have 'svdem' build to start coding rather than to have a production ready build for the final release. Therefore I switched off most of the stuff. How these offical builds are done in the long run is to be decided when we get there.

== '''List of Patches for a given Milestone''' ==

Here is a list of Patches one has to apply against a given Milestone of SRC680 (including CWS aquavcl01). Please keep the older Milestones here, since people are probably still on these Versions.

PLEASE NOTE : '''Current milestone for Aqua build is m202''' (older milestones are deprecated)

{| border="1" cellpadding="5" cellspacing="0"
|-
! Milestone || Patch to apply || Status
|-
| '''m202''' || see [[List of Patches requiring testing before for integration]] || work in progress
|-
| ''' (deprecated) m202''' || To avoid crashes with several entries in menu apply [http://eric.bachard.free.fr/patches/aqua/about_workaround/diff_salframe.diff about_workaround patch] in vcl/aqua/source/window ||Work in progress
|-
| ''' (deprecated) m200''' || To avoid crashes with several entries in menu apply [http://eric.bachard.free.fr/patches/aqua/about_workaround/diff_salframe.diff about_workaround patch] in vcl/aqua/source/window ||Work in progress
|}

== '''List of Patches requiring testing before for integration''' ==

All patches that developers have that need testing or peer review should be added here.

salatslayout.cxx : new implementation of text layout has to be tested.

== '''Known build issues''' ==

'''(deprecated) m200''': Breakage in instsetoo_native

See [http://eric.bachard.free.fr/mac/aquavcl/patches/m200_aquavcl01/instsetoo_native_util_makefile.mk.diff Fix for instsetoo_native breakage]

how apply the patch ?

Place it in <install_dir>/instsetoo_native/util

type :

patch -p0<instsetoo_native_util_makefile.mk.diff

m196: Breakage in pyuno

See [http://www.openoffice.org/issues/show_bug.cgi?id=72372 pyuno not found]

'''Workaround''' :

<pre>
1) either use the patch provided in issue 72372

2) or simply do ( in the same terminal, or please source the environment before):

cd bridges
build && deliver
cd ../pyuno
build && deliver

-> pyuno should build without any problem

cd .. && dmake

will complete your build

</pre>
[[User:Ericb|Ericb]] 14:52, 13 December 2006 (CET)

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd src680-m202/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

On PowerPC :

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
time dmake

Or (on Mac Intel ) :

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
time dmake

The main purpose of the '''boostrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set' should be substituted with 'MacOSXX86Env.Set'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours. Be patient. What can you do meanwhile? Do this:
<code>[bash,N]
while true ; do find . -maxdepth 1 -type d -anewer MacOSXPPCEnv.Set.sh |wc -l ; sleep 5; done
</code>
and wait till the number reaches 174

== '''Creating Debug-Versions of Modules''' ==

<pre> Important: a new section about use XCode for OpenOffice.org debug has been created.
See :</pre>

[[MacOSX_Debug_OpenOffice.org_using_XCode]]

'''Is it possible to build the complete set with symbols included ?'''

Currently not possible, and not advised.

''' is it possible to build some modules with symbols ?'''

Yes, and that's the simplest way to proceed. Some modules, like sal and vcl can be rebuilt using debug.

Example :

To rebuild sal with symbols included, do:

<code>[bash,N]
cd sal
rm -rf unxmacxp.pro
build debug=true
</code>

and recopy the libs into the bundle. gdb will display the symbols, and make your life easier.

Note : debug string is tested, and DEBUG is active when debug string is not empty. So debug=t works too.

''' How change gdb options, and use e.g. -g -ggdb or -gdwarf-2 ?'''

To rebuild the module, you just have to modify the option in solenv/inc/unxmacx.mk, replacing -g with -ggdb

'''Known issues'''

Sometimes a build error, or a runtime error, may be seen in the normal build,
but the error goes away when --enable-debug is used or if the module is compiled with debug=true.

The DEBUG build turns off optimisation, so this is a hint that compiler optimisation causes the error.

The error might be due to incorrect code or a compiler fault. Such errors might not be seen on all platforms,

and might not be seen in different compiler versions on one platform.

If the code can not be fixed there is a workaround using NOOPTFILES to build specified files with no optimisation.

Example :

jvmfwk on Mac OS X: build jvmfwk in m183 on Mac OS X Intel leads to Bus Error when javaldx is run.

Solution : use trial and error to rebuild individual files with debug=true. This proves the problem lies with vendorbase.cxx

Have a look in sc/source/core/data/makefile.mk for an example to use NOOPTFILES

To solve our problem: just add : NOOPTFILES= $(SLO)$/vendorbase.obj in the corresponding makefile.

Take care in case some .IF is needed to prevent interference with other platforms.

There's some additional information around debugging on Christians Page [[User:CL#2006-09-03]]

== Building and running svdem ==

We want to run the demonstration programs called "svdem". There are a couple of binaries called "svdem", which area they cover is still somewhat unclear to me, I hope some of you guys can shed some light here. But hey, this is a wiki! Just correct here :-).

==== svdem from VCL ====
To have the VCL Testprogram build you have to do:

'''[FIXME] replace this scetion with the same, but about svdem from svtools'''

cd vcl; build --all

This should have created a file called "svdem" here: vcl/unxmacxp.pro/bin/svdem. If you managed to build these binaries, you are nearly there. What you need now, is a wrapper directory structure to make this binary a fellow Mac OSX application. I mean the ones which have this structure:

svdem.app/
svdem.app/Contents
svdem.app/Contents/Info.plist
svdem.app/Contents/MacOS
svdem.app/Contents/MacOS/applicat.rdb
svdem.app/Contents/MacOS/svdem

You can basically create this structure anywhere you want. And you can link-in the file you just created (svdem). So you build up this structure once and link-in the freshly created svdem there:

ls -l svdem applicat.rdb
svdem -> /opt/src/openoffice/src680-m202/vcl/unxmacxp.pro/bin/svdem
applicat.rdb -> /opt/src/openoffice/src680-m202/vcl/unxmacxp.pro/bin/applicat.rdb

Now only the Info.plist file is missing, so here we go:

<code>[xml,N]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleDisplayName</key>
<string>SvDem</string>
<key>CFBundleExecutable</key>
<string>svdem</string>
<key>CFBundleIdentifier</key>
<string>com.yourcompany.svdem</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>1.0</string>
<key>LSRequiresCarbon</key>
<true/>
</dict>
</plist>
</code>

If you created the directory structure properly you can do './svdem' in the 'svdem.app/Contents/MacOS/' directory. You should see the svdem coming up.

==== svdem from svtools ====
* Copy the application package you created for the vcl svdem.
* Source your MacOSX[PPC-X86]Env.Set.sh
* Go into svtools/workben
* build svdem using dmake in the workben directory
* link the svdem and applicat.rdb from Contents/MacOS to the ones located in svtools/unxmacxp.pro/bin

You are done : you can now source your environment and run svdem using your usual shell.

== '''Installing, preparing and running OpenOffice.org''' ==

Here I like to outline the steps to run OpenOffice.org after a successful build from the sources. Running the native Aqua Version of OpenOffice.org is somewhat tricky at the moment, since the installation procedure and mode are not in their final state. So right now one has to manually do some preparations to run the Office suite. This will change in the future when we are about to release some Alpha Builds to a wider audience.

=== Drag & Drop Install the Application from the Diskimage ===

When you are one of the lucky few (Don't give up, Eric!), who have a successful build, you are going to see something like this as the last lines of the build:

.
.
.
......................................................................................................................................................
(CRC32 $11685D33: DiscRecording 3.1.3f2 (Apple_HFS : 2))
Ressourcen hinzufügen…
......................................................................................................................................................
Dauer: 15.406s
Dateigröße: 144732418 Bytes, Prüfsumme: CRC32 $14E0BB67
Bearbeitete Sektoren: 773848, 773845 komprimiert
Geschwindigkeit: 24.5M Bytes/Sek
Ersparnis: 63.5 %
created: /opt/src/openoffice/src680-m202/instsetoo_native/unxmacxp.pro/OpenOffice/install/de/OpenOffice.org-2.2_de.dmg

In this final step the ""instsetoo_native"" target creates the install Diskimages using Apple's 'hdiutil'. In my case it gives its output in German. After this disk image(s) have been created, double click the disk image to mount it (or type open <path to the DMG Image>) , and then move the icon named "OpenOffice.org 2.2" to your ''Applications'' folder (or any other folder you want this program to reside). The "OpenOffice.org 2.1" icon shown in the Finder is in fact a subdirectory called "OpenOffice.org 2.2.app". Subdirectories named ".app" (along with some well-know files inside like Info.plist, etc) are called ''Bundles'' in Apple's lingo.

=== Prepare the installation ===

'''Soon optional (tests in progress) '''

After the OpenOffice 2.2 Application has been copied to its destination, you have to go into this bundle and run a small shell script provided by Pavel Janik to prepare soffice.bin (OpenOffice.org launcher) for running. You have to run this script in the directory where a Universal Binary called "droplet" is located. This "droplet" binary was used to fire-off the X11 version of OpenOffice.org. Expect this to change, but as of now we have to do it like this.

I have put my OpenOffice.org build in my home directory's private "Application" folder (/Users/schmidtm/Applications), so please change this path to your installation. Now go to into the bundle and run the script:

cd /Users/schmidtm/Applications/OpenOffice.org 2.2.app/Contents/MacOS
/opt/src/openoffice/bin/fix_installed_OOo

<code>[bash,N]
#!/bin/bash

[ ! -f droplet ] && {
echo "Please run me in the directory, where binary named droplet is located."
exit 0
}

mv THIRDPARTYLICENSEREADME.html help presets share ..
mv droplet droplet.orig
mv program/* .
rmdir program

cd ..
ln -sf MacOS program
sed 's#droplet#soffice.bin#' Info.plist >Info.plist.new
mv Info.plist.new Info.plist
cd MacOS
</code>

=== Run the soffice.bin ===

We're nearly through, let's fire-off the binary:

AQUA_NATIVE_MENUS=TRUE ./soffice.bin -nofirststartwizard -norestore

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="5" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=TRUE || enable experimental native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

'''HACK''' : with current code, to enable native menus by defaut without have to define an environment variable, just comment as follow :

in vcl/aqua/source/window/salmenu.cxx, around line 124 :
<code>
/*
static const char *pExperimental = getenv ("AQUA_NATIVE_MENUS");

if ( !pExperimental || strcasecmp(pExperimental, "TRUE") )
return FALSE;
*/
</code>

== External links ==

# Bug Database: http://www.openoffice.org/issues/query.cgi
# Mailinglist: mac@porting.openoffice.org
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== Screenshots ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue) : http://blog.janik.cz/images/MacOSX/ => See : OOoMenus-separator-and-disabled_entries.png
# Native Menus : http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_native_controls_03_11_06/aqua_menus_01.jpg

More menus : http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]

Documentation/Building Guide/Building on MacOSX

2007-02-12T08:26:27Z

Maveric: /* '''List of Patches for a given Milestone''' */

<big>'''This document tries to wrap-up the build process for [[OpenOffice.org]] on MacOS X using the native windowing-toolkit of the platform named Aqua.''' </big>

An important goal is to get the demonstration programs "svdem" up and running. They act as a fairly good starting point to further endeavours, since they are used to test the capabilities of the underlying [[VCL]] layer. If this is achieved, one can build and Install the full-fledged OpenOffice.org Package. The purpose of this document is to describe the cumbersome build process of OpenOffice.org rather than to give a kickstart in the coding involved to get VCL ported to Carbon. A starting point for this is Pierre de Filippis excellent [[Intro To Mac Porting]].

I use the bash shell in all examples, since to my belief users of the C-shell are smart enough to figure out the differences anyway. If you want to dig deeper into the build process, please have a look at the description of the build environment here: [http://tools.openoffice.org/build_env.html Open OfficeBuild Environment].

Many thanks for help and assistance go to Pavel Janik and Eric Bachard.

== '''Prerequisites''' ==

This document was derived from the description of the X11 build thanksworthy provided by Eric Hoch in this document: [[MacOSXBuildInstructions]]. Here I like to outline the things you need to build the Aqua Version (besides the OS).

=== Mandatory ===

==== Xcode ====

This is (with GNU cp, soon optional) the only mandatory part to be installed to build Aqua version of OpenOffice.org.

Current verified working version is XCode 2.4.

Xcode 2.2, 2.3 are known to work for Aqua development. If any earlier versions work as well, please add them here.

==== X11SDK (soon optional) ====

A dependency for Mozilla plugin needs some prototype defined in some Xllib.h header.

Please note, this dependency is not needed in runtime, but only at buildtime.

X11SDK.pkg archive is located in your Tiger's DVD, and has to be installed in the case of you're using Mozilla prebuild archives

'''Workaround''' : XCode does contain Xlib headers. Just modify INCLUDE path properly will solve the build issue.

Meant replace ( not existing)
/usr/X11R6/include

with (existing) : /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/include

Doing a symlink between them :
<code>
If X11 and /or X11SDK is(are) not installed :
sudo mkdir -p /usr/X11R6

sudo ln -s /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/include /usr/X11R6/include
</code>

<pre>This issue should be fixed soon.</pre>

=== Strongly recommended ===

==== ccache ====
If you intend to build several times OpenOffice, you probably can benefit of ccache. ccache will speed up your future builds. The first time you make a build with ccache you won't notice it, but then the build will go up to five times faster.

You can install it using fink. It is simply named "ccache".

If you don't use fink, you can download it and build it yourself using the source provided at http://ccache.samba.org/

Then, in order to use it, you need to change the following environment variables (using bash) :

<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

=== Optional ===

==== Java ====

Normally installed with XCode.

==== The perl module Archive::Zip ( optional ) ====

Nothing is needed anymore with recent versions of XCode (means : not needed with XCode 2.4 at least).

If you still have issues doing configure because of that, please install Archive::Zip repecting the instructions below :

<code>[bash,N]
perl -MCPAN -eshell
install Archive::Zip
</code>

==== gpc ( optional) ====
GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>
Attention: Direct Link to the download but it's only a few hundred KB.
Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

==== pkg-config (optional) ====

Nothing to install on Aqua build, since --disable-gtk is forced

Called ''pkgconfig'' in Fink.

pkg-config can be found here : http://pkgconfig.freedesktop.org/wiki/

== '''Some Background (what is aquavcl01, EIS)''' ==

=== EIS ===
OpenOffice sources are basically kept in the CVS server located at anoncvs.services.openoffice.org. However this repository is managed by a database on top called EIS (Environment Information System) which is used to keep track of Master- and Client Workspaces. Master Workspaces are used to keep track of changes going back of the mainline trunk and undergo extensive QA-cycles. These Master Workspaces are driven to official releases. Child workspaces in contrast are copies of certain Master Workspaces used to develop and test bugfixes and additional functionality. These Child Workspaces are later (hopefully) merged back to mainlain Master Workspaces. The TX20 Report mentioned in the Links section gives a very good overview about the overall process. To learn more about Childworkspaces (CWS) have a look here: [[CWS]].

Go to EIS http://eis.services.openoffice.org/EIS2/servlet/Logon and Logon as guest/guest to get yourself an impression. You can find information about the different workspaces, their dates and times there.

=== VCL (Visual Class Libraries) ===

Porting OpenOffice.org to a new Windowing Toolkit is mostly porting of the OpenOffice's VCL Layer (Visual Class Libraries) to the new platforms toolkit. The VCL-Layer is responsible of mapping the OpenOffice Application calls to the windowing toolkit.

The (native) OpenOffice port to MacOSX using the Aqua Windowing Toolkit is developed in a child workspace called '''aquavcl01'''. This child workspace consists of the modules (aka subdirs): canvas dtrans extensions freetype padmin scp2 sj2 solenv vcl.

The basic approach to prepare a developer's client system to successfully build OpenOffice/Aqua is the following:

# checkout a given OpenOffice Milestone.
# checkout aquavcl01 Child Workspace.
# merge them together.
# apply the latest patches.

The last point here is a cumbersome but nevertheless necessary operation, since this porting project is in flux. Thanks to Pavel and many others improvements are happening at tremendous pace at the moment. All of these improvements get distributed as patches/diffs against aquavcl01. Aquavcl01 needs to remain stable all the time, therefore the team needs to work on this patch-by-patch aproach at the moment.

== '''Getting the code (checkout, merge and patch the puppy)''' ==

Now let's have a look what to check-out and where. All these milestone numbers below highly depend on the given point-in-time. The current milestone as of now (February 2nd 2007) is m202. You may change this to your needs. You can find the current milestone of each cws in the EIS database.

You also need to bear in mind that you have to access to the CVS-Server's default port (2401). If a firewall stop's you here you have to setup a CVS-Tunnel.

==== create a directory for a given milestone, setup CVS access: ====
<code>[bash,N]
mkdir src680-m202
cd src680-m202

export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
cvs login
</code>
Please Enter the password 'anoncvs'

==== checkout Milestone m202 (1,5 GB): ====
<code>[bash,N]
cvs -z3 co -r SRC680_m202 OpenOffice2
</code>
Once done, you'll obtain milestone 202. this not exactly what we want, because all changes concerning aquavcl01 Child workspace are not included. To complete, we need to check aquavcl01 changes.

==== checkout Aquavcl01 (50 MB): ====

1) First possibility : create a dedicated tree (cool backup )

To check aquavcl01 Child workspace, the most simple is to create aquavcl01 directory, and go inside this dir
<code>[bash,N]
mkdir aquavcl01-src

cd aquavcl01-src
</code>
(assuming you already did cvs login ..etc )
<code>[bash,N]
cvs -z3 co -r cws_src680_aquavcl01 OpenOffice2
</code>
The following modules will be present at the end :
<div style="background-color: lightyellow; border: 1px red dashed; padding: 3px 0 3px 15px;">
canvas

extensions

fpicker

padmin

sal

scp2

sfx2

solenv

dtrans

freetype

psprint

sj2

vcl

toolkit
</div>

All these modules are the ones we modified to create the native version : they all are tagged "aquavcl01" (see all CVS/Tag files in the tree) and all you have to do is either rename or delete the one located in src680-m202 and replace them with the one located in aquavcl01-src.

e.g. : canvas in src680-m202 will become canvas_m202 , and then, cp canvas from aquavcl01-src into src-m202

This applies for all the modules listed above.

2) Second possibility : use a little script to extract changes : extract_aquavcl01.sh

This shell script, located in src680-m202 will contain :
<code>[bash,N]
#!/bin/bash
list="canvas extensions fpicker padmin scp2 sfx2 solenv dtrans freetype psprint sj2 vcl sal toolkit"
for i in $list ; do
mv $i $i-m202
cvs -z3 co -r cws_src680_aquavcl01 $i
done
</code>

Then chmod +x extract_aquavcl01.sh

and run it :

./extract_aquavcl01.sh

When finished, and if no problem occurs, you should have a complete tree.

=== One-Time preparations and scripts ===

OpenOffice building gets configured by the popular open-source configuration-management package 'autoconf'. So you can do your beloved './configure' command, but in our case this is done in the 'config_office' subdirectory. To save the configure parameters and use them with different milestones I used to link-in my shellscript to fire up the ./configure line.

My directory-structure looks like this:

bin/
src680-m182/
src680-m196/
...

Now I go to the 'config_office' subdir and link in my startscript:
<code>[bash,N]
cd src680-m202/config_office/
ln -s ../../bin/build.sh
</code>
And this is how 'build.sh' looks like:

<code>[bash,N]
#!/bin/sh
export BASE=`pwd|sed 's/\/config_office//'`
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`
echo Building from : $BASE
echo OpenOffice Version : $OOVERSION
./configure \
--with-lang="de en-US" \
--with-jdk-home=/Library/Java/Home/ \
--with-gnu-cp=/sw/bin/cp \
--with-epm=internal \
--disable-mozab \
--disable-odk \
--disable-pasf \
--disable-gtk \
--disable-mozilla \
--with-build-version=$OOVERSION-`date +%d-%m-%y` \
--disable-fontconfig \
--disable-neon \
--without-nas
</code>

--disable-odk will avoid you to download some windows dll which is not needed for aqua-build.

--disable-pasf : pasf stands for Portable Audio System file. As we want to use system library rather than portable ones, we disabled this. However, at this time not all functionality will be available with pasf disabled. You might willing to use --with-pasf if you want working audio in your build.

--disable-nas : nas stands for Network Audio System, it uses X11, if you want to use it in your build, just remove this flag. You will need to install the X11 package provided in your CDs/DVD Mac OS X installation. X11 SDK from xCode tools is not required for build this.

This is allowedly a pretty much limited setup, but my overall goal is to get people to have 'svdem' build to start coding rather than to have a production ready build for the final release. Therefore I switched off most of the stuff. How these offical builds are done in the long run is to be decided when we get there.

== '''List of Patches for a given Milestone''' ==

Here is a list of Patches one has to apply against a given Milestone of SRC680 (including CWS aquavcl01). Please keep the older Milestones here, since people are probably still on these Versions.



PLEASE NOTE : '''Current milestone for Aqua build is m202''' (older milestones are deprecated)

{| border="1" cellpadding="5" cellspacing="0"
|-
! Milestone || Patch to apply || Status
|-
| '''m202''' || no additional patches needed || see patches to be tested
|-
| ''' (deprecated) m202''' || To avoid crashes with several entries in menu apply [http://eric.bachard.free.fr/patches/aqua/about_workaround/diff_salframe.diff about_workaround patch] in vcl/aqua/source/window ||Work in progress
|-
| ''' (deprecated) m200''' || To avoid crashes with several entries in menu apply [http://eric.bachard.free.fr/patches/aqua/about_workaround/diff_salframe.diff about_workaround patch] in vcl/aqua/source/window ||Work in progress
|}

== '''List of Patches requiring testing before for integration''' ==

All patches that developers have that need testing or peer review should be added here.

salatslayout.cxx : new implementation of text layout has to be tested.

== '''Known build issues''' ==

'''(deprecated) m200''': Breakage in instsetoo_native

See [http://eric.bachard.free.fr/mac/aquavcl/patches/m200_aquavcl01/instsetoo_native_util_makefile.mk.diff Fix for instsetoo_native breakage]

how apply the patch ?

Place it in <install_dir>/instsetoo_native/util

type :

patch -p0<instsetoo_native_util_makefile.mk.diff

m196: Breakage in pyuno

See [http://www.openoffice.org/issues/show_bug.cgi?id=72372 pyuno not found]

'''Workaround''' :

<pre>
1) either use the patch provided in issue 72372

2) or simply do ( in the same terminal, or please source the environment before):

cd bridges
build && deliver
cd ../pyuno
build && deliver

-> pyuno should build without any problem

cd .. && dmake

will complete your build

</pre>
[[User:Ericb|Ericb]] 14:52, 13 December 2006 (CET)

== '''Doing the build (about 4,5 GB)''' ==

Fine, now we have a (hopefully) working 'build.sh' in the config_office subdir. We need to run it beforehand:

cd src680-m202/config_office/
./build.sh

This will setup the necessary includefiles and create a couple of files in the '''parent''' directory (bootstrap, MacOSXPPCEnv.Set.sh, MacOSXPPCEnv.Set). If you are using the sh, ksh or bash you only need to take care for 'MacOSXPPCEnv.Set.sh'.

Now we need to get back to our base-directory, run the bootstrap script, source our Enviroment (MacOSXPPCEnv.Set.sh) and finally start the build-process:

On PowerPC :

cd ..
./bootstrap
source MacOSXPPCEnv.Set.sh
time dmake

Or (on Mac Intel ) :

cd ..
./bootstrap
source MacOSXX86Env.Set.sh
time dmake

The main purpose of the '''boostrap''' script is to build (if necessary) the dmake utility used. Dmake once was a unix make-clone made by wticorp but got incorporated into OpenOffice since it was orphaned. For more information about dmake, it's history and manpage have a look here: http://tools.openoffice.org/dmake/index.html

Sourcing MacOSXPPCEnv.Set.sh is very important not only for building but also for '''running''' svdem later on. Here all the Environment-Variables for the Build will be set up. For a detailed description see [[Environment_Variables]]. Please note that on Intel machines, 'MacOSXPPCEnv.Set' should be substituted with 'MacOSXX86Env.Set'.

This Build process takes on my box (Dual 1.8 GHz G5, 1.5GB RAM) roughly 10 hours. Be patient. What can you do meanwhile? Do this:
<code>[bash,N]
while true ; do find . -maxdepth 1 -type d -anewer MacOSXPPCEnv.Set.sh |wc -l ; sleep 5; done
</code>
and wait till the number reaches 174

== '''Creating Debug-Versions of Modules''' ==

<pre> Important: a new section about use XCode for OpenOffice.org debug has been created.
See :</pre>

[[MacOSX_Debug_OpenOffice.org_using_XCode]]

'''Is it possible to build the complete set with symbols included ?'''

Currently not possible, and not advised.

''' is it possible to build some modules with symbols ?'''

Yes, and that's the simplest way to proceed. Some modules, like sal and vcl can be rebuilt using debug.

Example :

To rebuild sal with symbols included, do:

<code>[bash,N]
cd sal
rm -rf unxmacxp.pro
build debug=true
</code>

and recopy the libs into the bundle. gdb will display the symbols, and make your life easier.

Note : debug string is tested, and DEBUG is active when debug string is not empty. So debug=t works too.

''' How change gdb options, and use e.g. -g -ggdb or -gdwarf-2 ?'''

To rebuild the module, you just have to modify the option in solenv/inc/unxmacx.mk, replacing -g with -ggdb

'''Known issues'''

Sometimes a build error, or a runtime error, may be seen in the normal build,
but the error goes away when --enable-debug is used or if the module is compiled with debug=true.

The DEBUG build turns off optimisation, so this is a hint that compiler optimisation causes the error.

The error might be due to incorrect code or a compiler fault. Such errors might not be seen on all platforms,

and might not be seen in different compiler versions on one platform.

If the code can not be fixed there is a workaround using NOOPTFILES to build specified files with no optimisation.

Example :

jvmfwk on Mac OS X: build jvmfwk in m183 on Mac OS X Intel leads to Bus Error when javaldx is run.

Solution : use trial and error to rebuild individual files with debug=true. This proves the problem lies with vendorbase.cxx

Have a look in sc/source/core/data/makefile.mk for an example to use NOOPTFILES

To solve our problem: just add : NOOPTFILES= $(SLO)$/vendorbase.obj in the corresponding makefile.

Take care in case some .IF is needed to prevent interference with other platforms.

There's some additional information around debugging on Christians Page [[User:CL#2006-09-03]]

== Building and running svdem ==

We want to run the demonstration programs called "svdem". There are a couple of binaries called "svdem", which area they cover is still somewhat unclear to me, I hope some of you guys can shed some light here. But hey, this is a wiki! Just correct here :-).

==== svdem from VCL ====
To have the VCL Testprogram build you have to do:

'''[FIXME] replace this scetion with the same, but about svdem from svtools'''

cd vcl; build --all

This should have created a file called "svdem" here: vcl/unxmacxp.pro/bin/svdem. If you managed to build these binaries, you are nearly there. What you need now, is a wrapper directory structure to make this binary a fellow Mac OSX application. I mean the ones which have this structure:

svdem.app/
svdem.app/Contents
svdem.app/Contents/Info.plist
svdem.app/Contents/MacOS
svdem.app/Contents/MacOS/applicat.rdb
svdem.app/Contents/MacOS/svdem

You can basically create this structure anywhere you want. And you can link-in the file you just created (svdem). So you build up this structure once and link-in the freshly created svdem there:

ls -l svdem applicat.rdb
svdem -> /opt/src/openoffice/src680-m202/vcl/unxmacxp.pro/bin/svdem
applicat.rdb -> /opt/src/openoffice/src680-m202/vcl/unxmacxp.pro/bin/applicat.rdb

Now only the Info.plist file is missing, so here we go:

<code>[xml,N]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleDisplayName</key>
<string>SvDem</string>
<key>CFBundleExecutable</key>
<string>svdem</string>
<key>CFBundleIdentifier</key>
<string>com.yourcompany.svdem</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>1.0</string>
<key>LSRequiresCarbon</key>
<true/>
</dict>
</plist>
</code>

If you created the directory structure properly you can do './svdem' in the 'svdem.app/Contents/MacOS/' directory. You should see the svdem coming up.

==== svdem from svtools ====
* Copy the application package you created for the vcl svdem.
* Source your MacOSX[PPC-X86]Env.Set.sh
* Go into svtools/workben
* build svdem using dmake in the workben directory
* link the svdem and applicat.rdb from Contents/MacOS to the ones located in svtools/unxmacxp.pro/bin

You are done : you can now source your environment and run svdem using your usual shell.

== '''Installing, preparing and running OpenOffice.org''' ==

Here I like to outline the steps to run OpenOffice.org after a successful build from the sources. Running the native Aqua Version of OpenOffice.org is somewhat tricky at the moment, since the installation procedure and mode are not in their final state. So right now one has to manually do some preparations to run the Office suite. This will change in the future when we are about to release some Alpha Builds to a wider audience.

=== Drag & Drop Install the Application from the Diskimage ===

When you are one of the lucky few (Don't give up, Eric!), who have a successful build, you are going to see something like this as the last lines of the build:

.
.
.
......................................................................................................................................................
(CRC32 $11685D33: DiscRecording 3.1.3f2 (Apple_HFS : 2))
Ressourcen hinzufügen…
......................................................................................................................................................
Dauer: 15.406s
Dateigröße: 144732418 Bytes, Prüfsumme: CRC32 $14E0BB67
Bearbeitete Sektoren: 773848, 773845 komprimiert
Geschwindigkeit: 24.5M Bytes/Sek
Ersparnis: 63.5 %
created: /opt/src/openoffice/src680-m202/instsetoo_native/unxmacxp.pro/OpenOffice/install/de/OpenOffice.org-2.2_de.dmg

In this final step the ""instsetoo_native"" target creates the install Diskimages using Apple's 'hdiutil'. In my case it gives its output in German. After this disk image(s) have been created, double click the disk image to mount it (or type open <path to the DMG Image>) , and then move the icon named "OpenOffice.org 2.2" to your ''Applications'' folder (or any other folder you want this program to reside). The "OpenOffice.org 2.1" icon shown in the Finder is in fact a subdirectory called "OpenOffice.org 2.2.app". Subdirectories named ".app" (along with some well-know files inside like Info.plist, etc) are called ''Bundles'' in Apple's lingo.

=== Prepare the installation ===

'''Soon optional (tests in progress) '''

After the OpenOffice 2.2 Application has been copied to its destination, you have to go into this bundle and run a small shell script provided by Pavel Janik to prepare soffice.bin (OpenOffice.org launcher) for running. You have to run this script in the directory where a Universal Binary called "droplet" is located. This "droplet" binary was used to fire-off the X11 version of OpenOffice.org. Expect this to change, but as of now we have to do it like this.

I have put my OpenOffice.org build in my home directory's private "Application" folder (/Users/schmidtm/Applications), so please change this path to your installation. Now go to into the bundle and run the script:

cd /Users/schmidtm/Applications/OpenOffice.org 2.2.app/Contents/MacOS
/opt/src/openoffice/bin/fix_installed_OOo

<code>[bash,N]
#!/bin/bash

[ ! -f droplet ] && {
echo "Please run me in the directory, where binary named droplet is located."
exit 0
}

mv THIRDPARTYLICENSEREADME.html help presets share ..
mv droplet droplet.orig
mv program/* .
rmdir program

cd ..
ln -sf MacOS program
sed 's#droplet#soffice.bin#' Info.plist >Info.plist.new
mv Info.plist.new Info.plist
cd MacOS
</code>

=== Run the soffice.bin ===

We're nearly through, let's fire-off the binary:

AQUA_NATIVE_MENUS=TRUE ./soffice.bin -nofirststartwizard -norestore

Notice the enviroment variable here. AQUA_NATIVE_MENUS is experimental stuff created by Pavel, SAL_NO_NWF was created some times ago, and is located in vcl/source/window/window.cxx . At the moment we have:

{| border="1" cellpadding="5" cellspacing="0"
|-
! Variable || Function
|-
| SAL_NO_NWF=TRUE || disable native controls code
|-
| AQUA_NATIVE_MENUS=TRUE || enable experimental native menus code
|}

Both changes are marked with comments in the source code, and when we remove them in the future, native controls and native menus will be enabled by default.

'''HACK''' : with current code, to enable native menus by defaut without have to define an environment variable, just comment as follow :

in vcl/aqua/source/window/salmenu.cxx, around line 124 :
<code>
/*
static const char *pExperimental = getenv ("AQUA_NATIVE_MENUS");

if ( !pExperimental || strcasecmp(pExperimental, "TRUE") )
return FALSE;
*/
</code>

== External links ==

# Bug Database: http://www.openoffice.org/issues/query.cgi
# Mailinglist: mac@porting.openoffice.org
# IRC Meeting-Logs (#ooo_macport@freenode.org): [[Previous_Mac_Meeting_logs]] [[MacOSXPortMeetings]]
# TX20: http://eric.bachard.free.fr/UTBM_TX20/reports/Carbon_vcl.pdf
# OpenOffice Source Directory Structure: http://wiki.services.openoffice.org/wiki/Source_code_directories
# Pavels Patch Wiki: http://blog.janik.cz/
# Eric Bachard Wiki: http://wiki.services.openoffice.org/wiki/User:Ericb
# Christian Lippka Wiki: http://wiki.services.openoffice.org/wiki/User:CL
# Carbon: http://developer.apple.com/carbon
# EIS: http://eis.services.openoffice.org/EIS2/servlet/Logon
# Runtime Configuration: http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html
# OpenOffice Domain Developer http://wiki.services.openoffice.org/wiki/DomainDeveloper

== Screenshots ==

# Eric Bachard screenshots (some are from Stephan Schaefer) http://eric.bachard.free.fr/mac/aquavcl/screenshots/
# Most recent: http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/
# Pavel Janik screenshots http://blog.janik.cz/images/MacOSX/2006-08-10
# Important screenshot (eventloop issue) : http://blog.janik.cz/images/MacOSX/ => See : OOoMenus-separator-and-disabled_entries.png
# Native Menus : http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_native_controls_03_11_06/aqua_menus_01.jpg

More menus : http://eric.bachard.free.fr/mac/aquavcl/screenshots/aqua_menus_05_nov_06/index.html

[[Category:MacOSX]]
[[Category:Porting]]
[[Category:Development]]
[[Category:Aqua]]

Mac OS X Build Instructions (X11)

2007-01-23T11:44:48Z

Maveric:

The current build instructions also at: http://porting.openoffice.org/mac/build_680_X11.html. Those are being moved to this page at OOo Wiki.

For historical reasons, there is also [[Mac OS X Build Instructions of SRC_m71]]

Note: supported compilers for Mac can be found in [[Compiler versions used by port maintainers and release engineers]]

Other [[:Category:MacOSX|Mac OS X related Wiki pages]].

=== Building OpenOffice.org X11 for Mac OS X PPC and Mac OS X x86===

Authors: Eric Hoch

Revised 2006-01-23

=== Introduction===

These build instructions are based upon milestone 680_m140 and higher.

Due to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. To get this informations we recommend you to subscribe to our porting mailing list dev@porting.openoffice.org.

There you'll get all the latest informations about patches and everything else related to and needed to port OpenOffice.org to the Mac.

=== Special Thanks===
Before we begin let me thank all the people without whom those build instructions would make no sense, the coders that help bringing OOo 2.0 to Mac OS X.
The coders and supporters behind the Mac port are:

Eric Bachard
Thorsten Behrens
Etsushi Kato
Florian Heckl
Pavel Janik
Nakata Maho
James McKenzie
Tino Rachui
Stephan Schäfer
Eric Hoch
Shaun McDonald

=== Requirements ===

* The fastest machine you can find. It'd be good if it had memory, too.
* Mac OS X 10.3.5 or Mac OS X 10.4.x including all the latest available Security Updates for
your version of Mac OS X
* on Mac OS X 10.3.x: XCode 1.5 plus November 2004 gcc 3.3 Update for
* on Mac OS X 10.4.x: XCode 2.1
Note: You can get both applications after a free registration at http://connect.apple.com
* JDK 1.4.2 plus latest SDK Updates (with full JDK SDK for the headers)
* an installed X-Server. We recommend Apple's X11 but you can also use the ones of X.org or Xfree86
* A minimum of 4 to 5GB for a standard build.
Note: Usage of disk space depends upon the number of localizations you build for.
More localizations means more disk space needed.
A minimum of 18GB for a full debug build.
* If you can afford it we recommend you to backup clean sources and work with a second set of sources.
With a second set of clean sources you can easily go back to clean sources if a module doesn't build,
a patch doesn't solve the problem, you have to revert a patch or for any other reason there may be.
In the meantime cvs sources could have been edited and you need to recompile more modules then just
one and that's probably not what you want...

===Determine the shell you use for compilation===

The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash.
If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x.

Where necessary this read-me distinguishes between bash and tcsh.

To determine the shell you currently use open Terminal.app and type the following command:

ps -p $$

The output shows you which shell you're currently using.

-/bin/bash or -bash means you are using bash

-/bin/tcsh or -tcsh means you are using the c-shell

===Getting OpenOffice.org and External Sources===

====Getting OpenOffice.org Source from CVS====

Once you have X properly installed, it's time to get the OpenOffice.org sources and other external sources. If you've built OpenOffice.org from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.

Download the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):

1. Open a new Terminal (/Applications/Utilities/Terminal)
2. mkdir 680_mXXX/source
3. cd 680_mXXX/source
4. Now set the CVSROOT
* for bash do:
export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
* for tcsh do:
setenv CVSROOT :pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
5. cvs login
6. Enter the password anoncvs
7. cvs -z3 co -r SRC680_mXXX OpenOffice2
for later milestones simply replace the XXX with the most current milestonenumber
8. go get some coffee, or a beer, since it'll take a while to get it all

Note that if your computer is behind a firewall and you're trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. The protocol runs on port 2401, and some firewalls will not allow communication on this port.

Attention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.

For further informations on this topic see get the source

To get a second copy of the sources use the following commands within your 680_mXXX directory:

1. cd
2. mkdir build
3. cd build
4. cp -R ../source/* .

==== Additional software that's not in the official OpenOffice.org sources ====

Now that you have the sources it's time to get the software that is not in the official OOo Source Code Tree.

* The perl module Archive::Zip
* Apache Ant - optional - not needed
* gpc
* pkg-config
* gnu_copy
* cups headers (for those building on Mac OS X 10.3. Panther)
* gtk2 - optional - not needed
* X11
* unowinreg.dll

To install Archive::Zip use the following commands in Terminal.app:

1. perl -MCPAN -eshell
2. install Archive::Zip

If this is your first installation of a module using CPAN you're asked to configure the CPAN environment. If you're not 100% sure what to answer simply accept the default answers.

Note: In some cases using CPAN with Mac OS X is a bit problematic. In this case simply follow the instructions given here on this website http://sial.org/howto/perl/life-with-cpan/macosx/ to solve the problem.

You can grep Apache Ant 1.6.5 here: http://ant.apache.org/bindownload.cgi
Attention: Direct Link to the download site. Before the download starts you need to choose a mirror. The size of Apache Ant is about 6.4MB.

After the download put Apache Ant into the following directory: <your path>/680_mxx/apache-ant-1.6.5

GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>

Attention: Direct Link to the download but it's only a few hundred KB.

Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

Since OS X comes with no pkg-config, or to be more specific it's simply not complete in OS X, you have to install it via fink (http://fink.sourceforge.net), MacPorts (http://www.macports.org) or the gentoo port system (http://www.metadistribution.org/macos/).

Beginning with m101 for Mac OS X gnu_copy is needed to copy files within the build process of OOo. Please use your porting mechanism to install gnu_copy.
For Macports the package name is coreutils, for fink it's fileutils.

If you need cups headers (on Mac OS X 10.3., building reports "cups.h missing"), then download them from http://ftp.cusoo.org/MacOSX/Utilities/PowerPC/cups_Panther/cups.tar.gz and put the headers to "/usr/include/cups".

If you want to compile OpenOffice.org with gtk2 support you have to install gtk2 via your porting_mechanism
Note: The most current versions of gkt2 and pkg-config are in about 90% of all cases only available as sources that you need to compile and not as binaries. Please consider this while preparing your mac.

Additional Note for fink users: You need to install both packages gtk2 and gtk2-devel using fink install </package name>

Yes, there are other porting mechanisms out there such as the one of NetBSD or you can get precompiled versions of gtk, gnu_copy and pkg-config via pages like osxgnu but the author of these build instructions has no experiences with these so no recommendation for them here.

Note: If you need help with installing or maintaining packages please contact the project that provides the porting_mechanism.

It's also possible to compile pkg-config, gnu_copy as part of the gnu-coreutils and gtk2 without fink or Macports. Be aware that in this case you need to resolve the various dependencies yourself. So we recommend using one of the porting mechanisms.

Because OS X does not install X11 by default and up to now you haven't installed one, now may be the time do so.
There are various X for Mac OS X out there e.g. Apple's X11, XDarwin.org's XDarwin or simply use your porting_mechanism to install either X.org 6.8.x or Xfree86 >=4.3.
For help with your X11 please contact the provider of the package or your porting mechanism project

By default OOo builds an Office Development Kit. This ODK requires you to download the unowinreg.dll from here http://tools.openoffice.org/unowinreg_prebuild/680/.

===Preparing to Build===

====Adding gpc to OOo sources====

1. uncompress <path to gpc>/gpc231.tar.Z
2. tar xvf <path to gpc>/gpc231.tar
3. cp <path to gpc>/gpc.[hc] <ooo source directory>/build/external/gpc/
4. rmdir gpc231

====Adding unowinreg.dll to OOo sources====

Copy the downloaded unowinreg.dll to <ooo source directory>/build/external/unowinreg/

====Applying Patches====

To apply a patch
cd
into the direcotory for the module which needs to be patched and do a:
patch -p0 <path/to/the patch>

Most of the patches use the naming scheme
modul_(subdirectory_subdirectory_etc)_filetopatch.patch.

To find all current patches do a search for issues in component subcomponent MacOSX.

You can grab the patches necessary to avoid the freetype crash from my idisk public folder

Due to the fact that not all the patches are from one author it's sometimes necessary to change to the subdirectory/ies or not. In this case the patch knows which subdirectories to jump over.
====Additional steps for Mac OS X 10.4.x aka Tiger Users====

OpenOffice.org1.9.xxx milestones and OpenOffice.org 2.0.x stable both now compile with gcc 4.0. Remember that you have to use XCode2.1 gcc 4.0
If you're using Mac OS X 10.4 aka Tiger and you want to use gcc 3.3 instead of the default gcc 4.0 you can do so by using the following commands within your shell.

1. Open up a new Terminal
2. sudo gcc_select 3.3

Do not use XCode 2.2.1 due to [http://qa.openoffice.org/issues/show_bug.cgi?id=69314 Issue 69314]

===Building OpenOffice.org===
Now that we've got it all the source, it's time to execute the build!

1. Open up a new Terminal.
2. Configure for your build
3. cd <path to ooo>/680_mXXX/build/config_office
4. ./configure --with-x --with-lang="de fr en-US"
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home/
--with-gnu-cp=<path to your version of gnu_copy> --disable-build-mozilla

Instead of using --with-freetype2=... you can also use --with-system-freetype
Attention: Darwinports gnu_copy is named gcp to avoid conflicts with Mac OS X cp

If you want to build with gtk-support please add --with-gtk2 to your configure script
and/or want to use your own apache-ant add --with-ant-home=<your path>/680_mxx/apache-ant-1.6.5

5. If configure fails it will output an error message saying what's missing or
what else causes it's breakage.
Be sure to also check the warnings configure outputs at the end of the configuration process.
Please report any breakage here with the error message output to dev@porting.openoffice.org
6. cd ..
7. ./bootstrap
8. Set up your shell build enviroment:
* for bash do:
PPC: source MacosxPPCEnv.Set.sh
Intel: source MacosxX86Env.Set.sh
* for tcsh do:
PPC: source MacosxPPCEnv.Set
Intel: source MacosxX86Env.Set
9. dmake
10. Report any and all build failures to mac@porting.openoffice.org mail list
11. cd instsetoo_native/unxmacxp.pro/OpenOffice/install
Within this directory you will find a folder for each language that
you build OpenOffice.org for. Those folders contain the installation disk images.

====Additional Informations for Macports Users====
When using Darwinports be sure to use ./configure without freetype since it leads to OpenOffice.org crashing with a version mismatch error when using Macport's freetype. You will find the additional patches needed to build freetype within OpenOffice.org in the subdirectory freetype2_patches of the patch archive.
====Using Mozilla within OpenOffice.org====

If you decided to use Mozilla packages to get special functions OpenOffice.org provides you, as I did in the example configure script, you have two choices to get them:

First:

You let OpenOffice.org compile them. Be aware that this adds additional tim to your compiling time.

If you decide to let OpenOffice.org compile Mozilla remove --disable-build-mozilla from the
./configure script and OpenOffice.org will compile Mozilla within the moz directory.

1. Before building Mozilla be sure to download Mozilla Sources. You can get them e.g. here:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.5/source/
2. cp mozilla-source-1.7.5.tar.gz <your path>/680_mXXX/moz/download
3. cd <your path>/680_mXXX/moz
4. cd config_office
5. Use the same ./configure script out of but this time remove --disable-build-mozilla
6. Continue with Step 5 of the "Building OpenOffice.org" paragraph

OpenOffice.org should now compile mozilla within its build process.

Second:

You grab the Mozilla packages for PPC here:
http://florian-heckl.de/ooo/MACOSXGCCPinc.zip
http://florian-heckl.de/ooo/MACOSXGCCPlib.zip
http://florian-heckl.de/ooo/MACOSXGCCPruntime.zip
and put them into <ooo build directory>/680_mXXX/moz/zipped
OpenOffice.org should detect and use them.

For Intel please use the ones from http://eric.bachard.free.fr/mac/moz/zipped/ these libraries appear to be universal binaries, can someone building on PPC (with Tiger) please check at some point?

===Building the whole OpenOffice.org suite or just a single Project with Debug Information===

To build the whole OpenOffice.org Suite with debug informations add
--enable-debug
to the configure command.

To rebuild a complete project with debug information, remove all object files by removing the unxmacxp.pro directory. Then run dmake with the debug option set to true:

cd $SRC_ROOT/(module-name)
$SRC_ROOT/(module-name)> rm -rf unxmacxp.pro
$SRC_ROOT/(module-name)> build debug=true
$SRC_ROOT/(module-name)> deliver

[[Category:Porting]]
[[Category:MacOSX]]

Mac OS X Build Instructions (X11)

2007-01-23T11:31:44Z

Maveric: /* Additional software that's not in the official OpenOffice.org sources */

The current build instructions also at: http://porting.openoffice.org/mac/build_680_X11.html. Those are being moved to this page at OOo Wiki.

For historical reasons, there is also [[Mac OS X Build Instructions of SRC_m71]]

Note: supported compilers for Mac can be found in [[Compiler versions used by port maintainers and release engineers]]

Other [[:Category:MacOSX|Mac OS X related Wiki pages]].

=== Building OpenOffice.org X11 on Darwin PPC===

Authors: Eric Hoch

Revised 2006-01-15

=== Introduction===

These build instructions are based upon milestone 680_m140 and higher.

Due to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. To get this informations we recommend you to subscribe to our porting mailing list dev@porting.openoffice.org.

There you'll get all the latest informations about patches and everything else related to and needed to port OpenOffice.org to the Mac.

=== Special Thanks===
Before we begin let me thank all the people without whom those build instructions would make no sense, the coders that help bringing OOo 2.0 to Mac OS X.
The coders and supporters behind the Mac port are:

Eric Bachard
Thorsten Behrens
Etsushi Kato
Florian Heckl
Pavel Janik
Nakata Maho
James McKenzie
Tino Rachui
Stephan Schäfer
Eric Hoch

=== Requirements ===

* The fastest machine you can find. It'd be good if it had memory, too.
* Mac OS X 10.3.5 or Mac OS X 10.4.x including all the latest available Security Updates for
your version of Mac OS X
* on Mac OS X 10.3.x: XCode 1.5 plus November 2004 gcc 3.3 Update for
* on Mac OS X 10.4.x: XCode 2.1
Note: You can get both applications after a free registration at http://connect.apple.com
* JDK 1.4.2 plus latest SDK Updates (with full JDK SDK for the headers)
* an installed X-Server. We recommend Apple's X11 but you can also use the ones of X.org or Xfree86
* A minimum of 4 to 5GB for a standard build.
Note: Usage of disk space depends upon the number of localizations you build for.
More localizations means more disk space needed.
A minimum of 18GB for a full debug build.
* If you can afford it we recommend you to backup clean sources and work with a second set of sources.
With a second set of clean sources you can easily go back to clean sources if a module doesn't build,
a patch doesn't solve the problem, you have to revert a patch or for any other reason there may be.
In the meantime cvs sources could have been edited and you need to recompile more modules then just
one and that's probably not what you want...

===Determine the shell you use for compilation===

The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash.
If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x.

Where necessary this read-me distinguishes between bash and tcsh.

To determine the shell you currently use open Terminal.app and type the following command:

ps -p $$

The output shows you which shell you're currently using.

-/bin/bash or -bash means you are using bash

-/bin/tcsh or -tcsh means you are using the c-shell

===Getting OpenOffice.org and External Sources===

====Getting OpenOffice.org Source from CVS====

Once you have X properly installed, it's time to get the OpenOffice.org sources and other external sources. If you've built OpenOffice.org from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.

Download the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):

1. Open a new Terminal (/Applications/Utilities/Terminal)
2. mkdir 680_mXXX/source
3. cd 680_mXXX/source
4. Now set the CVSROOT
* for bash do:
export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
* for tcsh do:
setenv CVSROOT :pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
5. cvs login
6. Enter the password anoncvs
7. cvs -z3 co -r SRC680_mXXX OpenOffice2
for later milestones simply replace the XXX with the most current milestonenumber
8. go get some coffee, or a beer, since it'll take a while to get it all

Note that if your computer is behind a firewall and you're trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. The protocol runs on port 2401, and some firewalls will not allow communication on this port.

Attention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.

For further informations on this topic see get the source

To get a second copy of the sources use the following commands within your 680_mXXX directory:

1. cd
2. mkdir build
3. cd build
4. cp -R ../source/* .

==== Additional software that's not in the official OpenOffice.org sources ====

Now that you have the sources it's time to get the software that is not in the official OOo Source Code Tree.

* The perl module Archive::Zip
* Apache Ant - optional - not needed
* gpc
* pkg-config
* gnu_copy
* cups headers (for those building on Mac OS X 10.3. Panther)
* gtk2 - optional - not needed
* X11
* unowinreg.dll

To install Archive::Zip use the following commands in Terminal.app:

1. perl -MCPAN -eshell
2. install Archive::Zip

If this is your first installation of a module using CPAN you're asked to configure the CPAN environment. If you're not 100% sure what to answer simply accept the default answers.

Note: In some cases using CPAN with Mac OS X is a bit problematic. In this case simply follow the instructions given here on this website http://sial.org/howto/perl/life-with-cpan/macosx/ to solve the problem.

You can grep Apache Ant 1.6.5 here: http://ant.apache.org/bindownload.cgi
Attention: Direct Link to the download site. Before the download starts you need to choose a mirror. The size of Apache Ant is about 6.4MB.

After the download put Apache Ant into the following directory: <your path>/680_mxx/apache-ant-1.6.5

GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>

Attention: Direct Link to the download but it's only a few hundred KB.

Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

Since OS X comes with no pkg-config, or to be more specific it's simply not complete in OS X, you have to install it via fink (http://fink.sourceforge.net), MacPorts (http://www.macports.org) or the gentoo port system (http://www.metadistribution.org/macos/).

Begining with m101 for Mac OS X gnu_copy is needed to copy files within the build process of OOo. Please use your porting mechanism to install gnu_copy.
For Darwinports the package name is coreutils, for fink it's fileutils.

If you need cups headers (on Mac OS X 10.3., building reports "cups.h missing"), then download them from http://ftp.cusoo.org/MacOSX/Utilities/PowerPC/cups_Panther/cups.tar.gz and put the headers to "/usr/include/cups".

If you want to compile OpenOffice.org with gtk2 support you have to install gtk2 via your porting_mechanism
Note: The most current versions of gkt2 and pkg-config are in about 90% of all cases only available as sources that you need to compile and not as binaries. Please consider this while preparing your mac.

Additional Note for fink users: You need to install both packages gtk2 and gtk2-devel using fink install </package name>

Yes, there are other porting mechanisms out there such as the one of NetBSD or you can get precompiled versions of gtk, gnu_copy and pkg-config via pages like osxgnu but the author of these build instructions has no experiences with these so no recommendation for them here.

Note: If you need help with installing or maintaining packages please contact the project that provides the porting_mechanism.

It's also possible to compile pkg-config, gnu_copy as part of the gnu-coreutils and gtk2 without fink or Darwinports. Be aware that in this case you need to resolve the various dependencies yourself. So we recommend using one of the porting mechanisms.

Because OS X does not install X11 by default and up to now you haven't installed one, now may be the time do so.
There are various X for Mac OS X out there e.g. Apple's X11, XDarwin.org's XDarwin or simply use your porting_mechanism to install either X.org 6.8.x or Xfree86 >=4.3.
For help with your X11 please contact the provider of the package or your porting mechanism project

By default OOo builds an Office Development Kit. This ODK requires you to download the unowinreg.dll from here http://tools.openoffice.org/unowinreg_prebuild/680/.

===Preparing to Build===

====Adding gpc to OOo sources====

1. uncompress <path to gpc>/gpc231.tar.Z
2. tar xvf <path to gpc>/gpc231.tar
3. cp <path to gpc>/gpc.[hc] <ooo source directory>/build/external/gpc/
4. rmdir gpc231

====Applying Patches====

To apply a patch
cd
into the direcotory for the module which needs to be patched and do a:
patch -p0 <path/to/the patch>

Most of the patches use the naming scheme
modul_(subdirectory_subdirectory_etc)_filetopatch.patch.

To find all current patches do a search for issues in component subcomponent MacOSX.

You can grab the patches necessary to avoid the freetype crash from my idisk public folder

Due to the fact that not all the patches are from one author it's sometimes necessary to change to the subdirectory/ies or not. In this case the patch knows which subdirectories to jump over.
====Additional steps for Mac OS X 10.4.x aka Tiger Users====

OpenOffice.org1.9.xxx milestones and OpenOffice.org 2.0.x stable both now compile with gcc 4.0. Remember that you have to use XCode2.1 gcc 4.0
If you're using Mac OS X 10.4 aka Tiger and you want to use gcc 3.3 instead of the default gcc 4.0 you can do so by using the following commands within your shell.

1. Open up a new Terminal
2. sudo gcc_select 3.3

Do not use XCode 2.2.1 due to [http://qa.openoffice.org/issues/show_bug.cgi?id=69314 Issue 69314]

===Building OpenOffice.org===
Now that we've got it all the source, it's time to execute the build!

1. Open up a new Terminal.
2. Configure for your build
3. cd <path to ooo>/680_mXXX/build/config_office
4. ./configure --with-x --with-lang="de fr en-US"
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home/
--with-gnu-cp=<path to your version of gnu_copy> --disable-build-mozilla

Instead of using --with-freetype2=... you can also use --with-system-freetype
Attention: Darwinports gnu_copy is named gcp to avoid conflicts with Mac OS X cp

If you want to build with gtk-support please add --with-gtk2 to your configure script.

5. If configure fails it will output an error message saying what's missing or
what else causes it's breakage.
Be sure to also check the warnings configure outputs at the end of the configuration process.
Please report any breakage here with the error message output to dev@porting.openoffice.org
6. cd ..
7. ./bootstrap
8. Set up your shell build enviroment:
* for bash do:
PPC: source MacosxPPCEnv.Set.sh
Intel: source MacosxX86Env.Set.sh
* for tcsh do:
PPC: source MacosxPPCEnv.Set
Intel: source MacosxX86Env.Set
9. dmake
10. Report any and all build failures to mac@porting.openoffice.org mail list
11. cd instsetoo_native/unxmacxp.pro/OpenOffice/install
Within this directory you will find a folder for each language that
you build OpenOffice.org for. Those folders contain the installation disk images.

====Additional Informations for Darwinports Users====
When using Darwinports be sure to use ./configure without freetype since it leads to OpenOffice.org crashing with a version mismatch error when using Darwinport's freetype. You will find the additional patches needed to build freetype within OpenOffice.org in the subdirectory freetype2_patches of the patch archive.
====Using Mozilla within OpenOffice.org====

If you decided to use Mozilla packages to get special functions OpenOffice.org provides you, as I did in the example configure script, you have two choices to get them:

First:

You let OpenOffice.org compile them. Be aware that this adds additional tim to your compiling time.

If you decide to let OpenOffice.org compile Mozilla remove --disable-build-mozilla from the
./configure script and OpenOffice.org will compile Mozilla within the moz directory.

1. Before building Mozilla be sure to download Mozilla Sources. You can get them e.g. here:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.5/source/
2. cp mozilla-source-1.7.5.tar.gz <your path>/680_mXXX/moz/download
3. cd <your path>/680_mXXX/moz
4. cd config_office
5. Use the same ./configure script out of but this time remove --disable-build-mozilla
6. Continue with Step 5 of the "Building OpenOffice.org" paragraph

OpenOffice.org should now compile mozilla within its build process.

Second:

You grab the Mozilla packages for PPC here:
http://florian-heckl.de/ooo/MACOSXGCCPinc.zip
http://florian-heckl.de/ooo/MACOSXGCCPlib.zip
http://florian-heckl.de/ooo/MACOSXGCCPruntime.zip
and put them into <ooo build directory>/680_mXXX/moz/zipped
OpenOffice.org should detect and use them.

For Intel please use the ones from http://eric.bachard.free.fr/mac/moz/zipped/ these libraries appear to be universal binaries, can someone building on PPC (with Tiger) please check at some point?

===Building the whole OpenOffice.org suite or just a single Project with Debug Information===

To build the whole OpenOffice.org Suite with debug informations add
--enable-debug
to the configure command.

To rebuild a complete project with debug information, remove all object files by removing the unxmacxp.pro directory. Then run dmake with the debug option set to true:

cd $SRC_ROOT/(module-name)
$SRC_ROOT/(module-name)> rm -rf unxmacxp.pro
$SRC_ROOT/(module-name)> build debug=true
$SRC_ROOT/(module-name)> deliver

[[Category:Porting]]
[[Category:MacOSX]]

Mac OS X Build Instructions (X11)

2007-01-23T11:30:44Z

Maveric: /* Additional software that's not in the official OpenOffice.org sources */

The current build instructions also at: http://porting.openoffice.org/mac/build_680_X11.html. Those are being moved to this page at OOo Wiki.

For historical reasons, there is also [[Mac OS X Build Instructions of SRC_m71]]

Note: supported compilers for Mac can be found in [[Compiler versions used by port maintainers and release engineers]]

Other [[:Category:MacOSX|Mac OS X related Wiki pages]].

=== Building OpenOffice.org X11 on Darwin PPC===

Authors: Eric Hoch

Revised 2006-01-15

=== Introduction===

These build instructions are based upon milestone 680_m140 and higher.

Due to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. To get this informations we recommend you to subscribe to our porting mailing list dev@porting.openoffice.org.

There you'll get all the latest informations about patches and everything else related to and needed to port OpenOffice.org to the Mac.

=== Special Thanks===
Before we begin let me thank all the people without whom those build instructions would make no sense, the coders that help bringing OOo 2.0 to Mac OS X.
The coders and supporters behind the Mac port are:

Eric Bachard
Thorsten Behrens
Etsushi Kato
Florian Heckl
Pavel Janik
Nakata Maho
James McKenzie
Tino Rachui
Stephan Schäfer
Eric Hoch

=== Requirements ===

* The fastest machine you can find. It'd be good if it had memory, too.
* Mac OS X 10.3.5 or Mac OS X 10.4.x including all the latest available Security Updates for
your version of Mac OS X
* on Mac OS X 10.3.x: XCode 1.5 plus November 2004 gcc 3.3 Update for
* on Mac OS X 10.4.x: XCode 2.1
Note: You can get both applications after a free registration at http://connect.apple.com
* JDK 1.4.2 plus latest SDK Updates (with full JDK SDK for the headers)
* an installed X-Server. We recommend Apple's X11 but you can also use the ones of X.org or Xfree86
* A minimum of 4 to 5GB for a standard build.
Note: Usage of disk space depends upon the number of localizations you build for.
More localizations means more disk space needed.
A minimum of 18GB for a full debug build.
* If you can afford it we recommend you to backup clean sources and work with a second set of sources.
With a second set of clean sources you can easily go back to clean sources if a module doesn't build,
a patch doesn't solve the problem, you have to revert a patch or for any other reason there may be.
In the meantime cvs sources could have been edited and you need to recompile more modules then just
one and that's probably not what you want...

===Determine the shell you use for compilation===

The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash.
If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x.

Where necessary this read-me distinguishes between bash and tcsh.

To determine the shell you currently use open Terminal.app and type the following command:

ps -p $$

The output shows you which shell you're currently using.

-/bin/bash or -bash means you are using bash

-/bin/tcsh or -tcsh means you are using the c-shell

===Getting OpenOffice.org and External Sources===

====Getting OpenOffice.org Source from CVS====

Once you have X properly installed, it's time to get the OpenOffice.org sources and other external sources. If you've built OpenOffice.org from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.

Download the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):

1. Open a new Terminal (/Applications/Utilities/Terminal)
2. mkdir 680_mXXX/source
3. cd 680_mXXX/source
4. Now set the CVSROOT
* for bash do:
export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
* for tcsh do:
setenv CVSROOT :pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
5. cvs login
6. Enter the password anoncvs
7. cvs -z3 co -r SRC680_mXXX OpenOffice2
for later milestones simply replace the XXX with the most current milestonenumber
8. go get some coffee, or a beer, since it'll take a while to get it all

Note that if your computer is behind a firewall and you're trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. The protocol runs on port 2401, and some firewalls will not allow communication on this port.

Attention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.

For further informations on this topic see get the source

To get a second copy of the sources use the following commands within your 680_mXXX directory:

1. cd
2. mkdir build
3. cd build
4. cp -R ../source/* .

==== Additional software that's not in the official OpenOffice.org sources ====

Now that you have the sources it's time to get the software that is not in the official OOo Source Code Tree.

* The perl module Archive::Zip
* Apache Ant - optional - not needed
* gpc
* pkg-config
* gnu_copy
* cups headers (for those building on Mac OS X 10.3. Panther)
* gtk2 - optional - not needed
* X11
*unowinreg.dll

To install Archive::Zip use the following commands in Terminal.app:

1. perl -MCPAN -eshell
2. install Archive::Zip

If this is your first installation of a module using CPAN you're asked to configure the CPAN environment. If you're not 100% sure what to answer simply accept the default answers.

Note: In some cases using CPAN with Mac OS X is a bit problematic. In this case simply follow the instructions given here on this website http://sial.org/howto/perl/life-with-cpan/macosx/ to solve the problem.

You can grep Apache Ant 1.6.5 here: http://ant.apache.org/bindownload.cgi
Attention: Direct Link to the download site. Before the download starts you need to choose a mirror. The size of Apache Ant is about 6.4MB.

After the download put Apache Ant into the following directory: <your path>/680_mxx/apache-ant-1.6.5

GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>

Attention: Direct Link to the download but it's only a few hundred KB.

Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

Since OS X comes with no pkg-config, or to be more specific it's simply not complete in OS X, you have to install it via fink (http://fink.sourceforge.net), MacPorts (http://www.macports.org) or the gentoo port system (http://www.metadistribution.org/macos/).

Begining with m101 for Mac OS X gnu_copy is needed to copy files within the build process of OOo. Please use your porting mechanism to install gnu_copy.
For Darwinports the package name is coreutils, for fink it's fileutils.

If you need cups headers (on Mac OS X 10.3., building reports "cups.h missing"), then download them from http://ftp.cusoo.org/MacOSX/Utilities/PowerPC/cups_Panther/cups.tar.gz and put the headers to "/usr/include/cups".

If you want to compile OpenOffice.org with gtk2 support you have to install gtk2 via your porting_mechanism
Note: The most current versions of gkt2 and pkg-config are in about 90% of all cases only available as sources that you need to compile and not as binaries. Please consider this while preparing your mac.

Additional Note for fink users: You need to install both packages gtk2 and gtk2-devel using fink install </package name>

Yes, there are other porting mechanisms out there such as the one of NetBSD or you can get precompiled versions of gtk, gnu_copy and pkg-config via pages like osxgnu but the author of these build instructions has no experiences with these so no recommendation for them here.

Note: If you need help with installing or maintaining packages please contact the project that provides the porting_mechanism.

It's also possible to compile pkg-config, gnu_copy as part of the gnu-coreutils and gtk2 without fink or Darwinports. Be aware that in this case you need to resolve the various dependencies yourself. So we recommend using one of the porting mechanisms.

Because OS X does not install X11 by default and up to now you haven't installed one, now may be the time do so.
There are various X for Mac OS X out there e.g. Apple's X11, XDarwin.org's XDarwin or simply use your porting_mechanism to install either X.org 6.8.x or Xfree86 >=4.3.
For help with your X11 please contact the provider of the package or your porting mechanism project

By default OOo builds an Office Development Kit. This ODK requires you to download the unowinreg.dll from here http://tools.openoffice.org/unowinreg_prebuild/680/.

===Preparing to Build===

====Adding gpc to OOo sources====

1. uncompress <path to gpc>/gpc231.tar.Z
2. tar xvf <path to gpc>/gpc231.tar
3. cp <path to gpc>/gpc.[hc] <ooo source directory>/build/external/gpc/
4. rmdir gpc231

====Applying Patches====

To apply a patch
cd
into the direcotory for the module which needs to be patched and do a:
patch -p0 <path/to/the patch>

Most of the patches use the naming scheme
modul_(subdirectory_subdirectory_etc)_filetopatch.patch.

To find all current patches do a search for issues in component subcomponent MacOSX.

You can grab the patches necessary to avoid the freetype crash from my idisk public folder

Due to the fact that not all the patches are from one author it's sometimes necessary to change to the subdirectory/ies or not. In this case the patch knows which subdirectories to jump over.
====Additional steps for Mac OS X 10.4.x aka Tiger Users====

OpenOffice.org1.9.xxx milestones and OpenOffice.org 2.0.x stable both now compile with gcc 4.0. Remember that you have to use XCode2.1 gcc 4.0
If you're using Mac OS X 10.4 aka Tiger and you want to use gcc 3.3 instead of the default gcc 4.0 you can do so by using the following commands within your shell.

1. Open up a new Terminal
2. sudo gcc_select 3.3

Do not use XCode 2.2.1 due to [http://qa.openoffice.org/issues/show_bug.cgi?id=69314 Issue 69314]

===Building OpenOffice.org===
Now that we've got it all the source, it's time to execute the build!

1. Open up a new Terminal.
2. Configure for your build
3. cd <path to ooo>/680_mXXX/build/config_office
4. ./configure --with-x --with-lang="de fr en-US"
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home/
--with-gnu-cp=<path to your version of gnu_copy> --disable-build-mozilla

Instead of using --with-freetype2=... you can also use --with-system-freetype
Attention: Darwinports gnu_copy is named gcp to avoid conflicts with Mac OS X cp

If you want to build with gtk-support please add --with-gtk2 to your configure script.

5. If configure fails it will output an error message saying what's missing or
what else causes it's breakage.
Be sure to also check the warnings configure outputs at the end of the configuration process.
Please report any breakage here with the error message output to dev@porting.openoffice.org
6. cd ..
7. ./bootstrap
8. Set up your shell build enviroment:
* for bash do:
PPC: source MacosxPPCEnv.Set.sh
Intel: source MacosxX86Env.Set.sh
* for tcsh do:
PPC: source MacosxPPCEnv.Set
Intel: source MacosxX86Env.Set
9. dmake
10. Report any and all build failures to mac@porting.openoffice.org mail list
11. cd instsetoo_native/unxmacxp.pro/OpenOffice/install
Within this directory you will find a folder for each language that
you build OpenOffice.org for. Those folders contain the installation disk images.

====Additional Informations for Darwinports Users====
When using Darwinports be sure to use ./configure without freetype since it leads to OpenOffice.org crashing with a version mismatch error when using Darwinport's freetype. You will find the additional patches needed to build freetype within OpenOffice.org in the subdirectory freetype2_patches of the patch archive.
====Using Mozilla within OpenOffice.org====

If you decided to use Mozilla packages to get special functions OpenOffice.org provides you, as I did in the example configure script, you have two choices to get them:

First:

You let OpenOffice.org compile them. Be aware that this adds additional tim to your compiling time.

If you decide to let OpenOffice.org compile Mozilla remove --disable-build-mozilla from the
./configure script and OpenOffice.org will compile Mozilla within the moz directory.

1. Before building Mozilla be sure to download Mozilla Sources. You can get them e.g. here:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.5/source/
2. cp mozilla-source-1.7.5.tar.gz <your path>/680_mXXX/moz/download
3. cd <your path>/680_mXXX/moz
4. cd config_office
5. Use the same ./configure script out of but this time remove --disable-build-mozilla
6. Continue with Step 5 of the "Building OpenOffice.org" paragraph

OpenOffice.org should now compile mozilla within its build process.

Second:

You grab the Mozilla packages for PPC here:
http://florian-heckl.de/ooo/MACOSXGCCPinc.zip
http://florian-heckl.de/ooo/MACOSXGCCPlib.zip
http://florian-heckl.de/ooo/MACOSXGCCPruntime.zip
and put them into <ooo build directory>/680_mXXX/moz/zipped
OpenOffice.org should detect and use them.

For Intel please use the ones from http://eric.bachard.free.fr/mac/moz/zipped/ these libraries appear to be universal binaries, can someone building on PPC (with Tiger) please check at some point?

===Building the whole OpenOffice.org suite or just a single Project with Debug Information===

To build the whole OpenOffice.org Suite with debug informations add
--enable-debug
to the configure command.

To rebuild a complete project with debug information, remove all object files by removing the unxmacxp.pro directory. Then run dmake with the debug option set to true:

cd $SRC_ROOT/(module-name)
$SRC_ROOT/(module-name)> rm -rf unxmacxp.pro
$SRC_ROOT/(module-name)> build debug=true
$SRC_ROOT/(module-name)> deliver

[[Category:Porting]]
[[Category:MacOSX]]

Mac OS X Build Instructions (X11)

2007-01-23T11:27:01Z

Maveric: /* Building OpenOffice.org */

The current build instructions also at: http://porting.openoffice.org/mac/build_680_X11.html. Those are being moved to this page at OOo Wiki.

For historical reasons, there is also [[Mac OS X Build Instructions of SRC_m71]]

Note: supported compilers for Mac can be found in [[Compiler versions used by port maintainers and release engineers]]

Other [[:Category:MacOSX|Mac OS X related Wiki pages]].

=== Building OpenOffice.org X11 on Darwin PPC===

Authors: Eric Hoch

Revised 2006-01-15

=== Introduction===

These build instructions are based upon milestone 680_m140 and higher.

Due to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. To get this informations we recommend you to subscribe to our porting mailing list dev@porting.openoffice.org.

There you'll get all the latest informations about patches and everything else related to and needed to port OpenOffice.org to the Mac.

=== Special Thanks===
Before we begin let me thank all the people without whom those build instructions would make no sense, the coders that help bringing OOo 2.0 to Mac OS X.
The coders and supporters behind the Mac port are:

Eric Bachard
Thorsten Behrens
Etsushi Kato
Florian Heckl
Pavel Janik
Nakata Maho
James McKenzie
Tino Rachui
Stephan Schäfer
Eric Hoch

=== Requirements ===

* The fastest machine you can find. It'd be good if it had memory, too.
* Mac OS X 10.3.5 or Mac OS X 10.4.x including all the latest available Security Updates for
your version of Mac OS X
* on Mac OS X 10.3.x: XCode 1.5 plus November 2004 gcc 3.3 Update for
* on Mac OS X 10.4.x: XCode 2.1
Note: You can get both applications after a free registration at http://connect.apple.com
* JDK 1.4.2 plus latest SDK Updates (with full JDK SDK for the headers)
* an installed X-Server. We recommend Apple's X11 but you can also use the ones of X.org or Xfree86
* A minimum of 4 to 5GB for a standard build.
Note: Usage of disk space depends upon the number of localizations you build for.
More localizations means more disk space needed.
A minimum of 18GB for a full debug build.
* If you can afford it we recommend you to backup clean sources and work with a second set of sources.
With a second set of clean sources you can easily go back to clean sources if a module doesn't build,
a patch doesn't solve the problem, you have to revert a patch or for any other reason there may be.
In the meantime cvs sources could have been edited and you need to recompile more modules then just
one and that's probably not what you want...

===Determine the shell you use for compilation===

The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash.
If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x.

Where necessary this read-me distinguishes between bash and tcsh.

To determine the shell you currently use open Terminal.app and type the following command:

ps -p $$

The output shows you which shell you're currently using.

-/bin/bash or -bash means you are using bash

-/bin/tcsh or -tcsh means you are using the c-shell

===Getting OpenOffice.org and External Sources===

====Getting OpenOffice.org Source from CVS====

Once you have X properly installed, it's time to get the OpenOffice.org sources and other external sources. If you've built OpenOffice.org from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.

Download the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):

1. Open a new Terminal (/Applications/Utilities/Terminal)
2. mkdir 680_mXXX/source
3. cd 680_mXXX/source
4. Now set the CVSROOT
* for bash do:
export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
* for tcsh do:
setenv CVSROOT :pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
5. cvs login
6. Enter the password anoncvs
7. cvs -z3 co -r SRC680_mXXX OpenOffice2
for later milestones simply replace the XXX with the most current milestonenumber
8. go get some coffee, or a beer, since it'll take a while to get it all

Note that if your computer is behind a firewall and you're trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. The protocol runs on port 2401, and some firewalls will not allow communication on this port.

Attention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.

For further informations on this topic see get the source

To get a second copy of the sources use the following commands within your 680_mXXX directory:

1. cd
2. mkdir build
3. cd build
4. cp -R ../source/* .

==== Additional software that's not in the official OpenOffice.org sources ====

Now that you have the sources it's time to get the software that is not in the official OOo Source Code Tree.

* The perl module Archive::Zip
* Apache Ant - optional - not needed
* gpc
* pkg-config
* gnu_copy
* cups headers (for those building on Mac OS X 10.3. Panther)
* gtk2 - optional - not needed
* X11

To install Archive::Zip use the following commands in Terminal.app:

1. perl -MCPAN -eshell
2. install Archive::Zip

If this is your first installation of a module using CPAN you're asked to configure the CPAN environment. If you're not 100% sure what to answer simply accept the default answers.

Note: In some cases using CPAN with Mac OS X is a bit problematic. In this case simply follow the instructions given here on this website http://sial.org/howto/perl/life-with-cpan/macosx/ to solve the problem.

You can grep Apache Ant 1.6.5 here: http://ant.apache.org/bindownload.cgi
Attention: Direct Link to the download site. Before the download starts you need to choose a mirror. The size of Apache Ant is about 6.4MB.

After the download put Apache Ant into the following directory: <your path>/680_mxx/apache-ant-1.6.5

GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>

Attention: Direct Link to the download but it's only a few hundred KB.

Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

Since OS X comes with no pkg-config, or to be more specific it's simply not complete in OS X, you have to install it via fink (http://fink.sourceforge.net), MacPorts (http://www.macports.org) or the gentoo port system (http://www.metadistribution.org/macos/).

Begining with m101 for Mac OS X gnu_copy is needed to copy files within the build process of OOo. Please use your porting mechanism to install gnu_copy.
For Darwinports the package name is coreutils, for fink it's fileutils.

If you need cups headers (on Mac OS X 10.3., building reports "cups.h missing"), then download them from http://ftp.cusoo.org/MacOSX/Utilities/PowerPC/cups_Panther/cups.tar.gz and put the headers to "/usr/include/cups".

If you want to compile OpenOffice.org with gtk2 support you have to install gtk2 via your porting_mechanism
Note: The most current versions of gkt2 and pkg-config are in about 90% of all cases only available as sources that you need to compile and not as binaries. Please consider this while preparing your mac.

Additional Note for fink users: You need to install both packages gtk2 and gtk2-devel using fink install </package name>

Yes, there are other porting mechanisms out there such as the one of NetBSD or you can get precompiled versions of gtk, gnu_copy and pkg-config via pages like osxgnu but the author of these build instructions has no experiences with these so no recommendation for them here.

Note: If you need help with installing or maintaining packages please contact the project that provides the porting_mechanism.

It's also possible to compile pkg-config, gnu_copy as part of the gnu-coreutils and gtk2 without fink or Darwinports. Be aware that in this case you need to resolve the various dependencies yourself. So we recommend using one of the porting mechanisms.

Because OS X does not install X11 by default and up to now you haven't installed one, now may be the time do so.
There are various X for Mac OS X out there e.g. Apple's X11, XDarwin.org's XDarwin or simply use your porting_mechanism to install either X.org 6.8.x or Xfree86 >=4.3.
For help with your X11 please contact the provider of the package or your porting mechanism project

===Preparing to Build===

====Adding gpc to OOo sources====

1. uncompress <path to gpc>/gpc231.tar.Z
2. tar xvf <path to gpc>/gpc231.tar
3. cp <path to gpc>/gpc.[hc] <ooo source directory>/build/external/gpc/
4. rmdir gpc231

====Applying Patches====

To apply a patch
cd
into the direcotory for the module which needs to be patched and do a:
patch -p0 <path/to/the patch>

Most of the patches use the naming scheme
modul_(subdirectory_subdirectory_etc)_filetopatch.patch.

To find all current patches do a search for issues in component subcomponent MacOSX.

You can grab the patches necessary to avoid the freetype crash from my idisk public folder

Due to the fact that not all the patches are from one author it's sometimes necessary to change to the subdirectory/ies or not. In this case the patch knows which subdirectories to jump over.
====Additional steps for Mac OS X 10.4.x aka Tiger Users====

OpenOffice.org1.9.xxx milestones and OpenOffice.org 2.0.x stable both now compile with gcc 4.0. Remember that you have to use XCode2.1 gcc 4.0
If you're using Mac OS X 10.4 aka Tiger and you want to use gcc 3.3 instead of the default gcc 4.0 you can do so by using the following commands within your shell.

1. Open up a new Terminal
2. sudo gcc_select 3.3

Do not use XCode 2.2.1 due to [http://qa.openoffice.org/issues/show_bug.cgi?id=69314 Issue 69314]

===Building OpenOffice.org===
Now that we've got it all the source, it's time to execute the build!

1. Open up a new Terminal.
2. Configure for your build
3. cd <path to ooo>/680_mXXX/build/config_office
4. ./configure --with-x --with-lang="de fr en-US"
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home/
--with-gnu-cp=<path to your version of gnu_copy> --disable-build-mozilla

Instead of using --with-freetype2=... you can also use --with-system-freetype
Attention: Darwinports gnu_copy is named gcp to avoid conflicts with Mac OS X cp

If you want to build with gtk-support please add --with-gtk2 to your configure script.

5. If configure fails it will output an error message saying what's missing or
what else causes it's breakage.
Be sure to also check the warnings configure outputs at the end of the configuration process.
Please report any breakage here with the error message output to dev@porting.openoffice.org
6. cd ..
7. ./bootstrap
8. Set up your shell build enviroment:
* for bash do:
PPC: source MacosxPPCEnv.Set.sh
Intel: source MacosxX86Env.Set.sh
* for tcsh do:
PPC: source MacosxPPCEnv.Set
Intel: source MacosxX86Env.Set
9. dmake
10. Report any and all build failures to mac@porting.openoffice.org mail list
11. cd instsetoo_native/unxmacxp.pro/OpenOffice/install
Within this directory you will find a folder for each language that
you build OpenOffice.org for. Those folders contain the installation disk images.

====Additional Informations for Darwinports Users====
When using Darwinports be sure to use ./configure without freetype since it leads to OpenOffice.org crashing with a version mismatch error when using Darwinport's freetype. You will find the additional patches needed to build freetype within OpenOffice.org in the subdirectory freetype2_patches of the patch archive.
====Using Mozilla within OpenOffice.org====

If you decided to use Mozilla packages to get special functions OpenOffice.org provides you, as I did in the example configure script, you have two choices to get them:

First:

You let OpenOffice.org compile them. Be aware that this adds additional tim to your compiling time.

If you decide to let OpenOffice.org compile Mozilla remove --disable-build-mozilla from the
./configure script and OpenOffice.org will compile Mozilla within the moz directory.

1. Before building Mozilla be sure to download Mozilla Sources. You can get them e.g. here:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.5/source/
2. cp mozilla-source-1.7.5.tar.gz <your path>/680_mXXX/moz/download
3. cd <your path>/680_mXXX/moz
4. cd config_office
5. Use the same ./configure script out of but this time remove --disable-build-mozilla
6. Continue with Step 5 of the "Building OpenOffice.org" paragraph

OpenOffice.org should now compile mozilla within its build process.

Second:

You grab the Mozilla packages for PPC here:
http://florian-heckl.de/ooo/MACOSXGCCPinc.zip
http://florian-heckl.de/ooo/MACOSXGCCPlib.zip
http://florian-heckl.de/ooo/MACOSXGCCPruntime.zip
and put them into <ooo build directory>/680_mXXX/moz/zipped
OpenOffice.org should detect and use them.

For Intel please use the ones from http://eric.bachard.free.fr/mac/moz/zipped/ these libraries appear to be universal binaries, can someone building on PPC (with Tiger) please check at some point?

===Building the whole OpenOffice.org suite or just a single Project with Debug Information===

To build the whole OpenOffice.org Suite with debug informations add
--enable-debug
to the configure command.

To rebuild a complete project with debug information, remove all object files by removing the unxmacxp.pro directory. Then run dmake with the debug option set to true:

cd $SRC_ROOT/(module-name)
$SRC_ROOT/(module-name)> rm -rf unxmacxp.pro
$SRC_ROOT/(module-name)> build debug=true
$SRC_ROOT/(module-name)> deliver

[[Category:Porting]]
[[Category:MacOSX]]

Mac OS X Build Instructions (X11)

2007-01-23T11:13:41Z

Maveric: /* Additional software that's not in the official OpenOffice.org sources */

The current build instructions also at: http://porting.openoffice.org/mac/build_680_X11.html. Those are being moved to this page at OOo Wiki.

For historical reasons, there is also [[Mac OS X Build Instructions of SRC_m71]]

Note: supported compilers for Mac can be found in [[Compiler versions used by port maintainers and release engineers]]

Other [[:Category:MacOSX|Mac OS X related Wiki pages]].

=== Building OpenOffice.org X11 on Darwin PPC===

Authors: Eric Hoch

Revised 2006-01-15

=== Introduction===

These build instructions are based upon milestone 680_m140 and higher.

Due to the nature of a port in progress this document cannot give a general overview of all the current patches necessary to build a specific milestone. To get this informations we recommend you to subscribe to our porting mailing list dev@porting.openoffice.org.

There you'll get all the latest informations about patches and everything else related to and needed to port OpenOffice.org to the Mac.

=== Special Thanks===
Before we begin let me thank all the people without whom those build instructions would make no sense, the coders that help bringing OOo 2.0 to Mac OS X.
The coders and supporters behind the Mac port are:

Eric Bachard
Thorsten Behrens
Etsushi Kato
Florian Heckl
Pavel Janik
Nakata Maho
James McKenzie
Tino Rachui
Stephan Schäfer
Eric Hoch

=== Requirements ===

* The fastest machine you can find. It'd be good if it had memory, too.
* Mac OS X 10.3.5 or Mac OS X 10.4.x including all the latest available Security Updates for
your version of Mac OS X
* on Mac OS X 10.3.x: XCode 1.5 plus November 2004 gcc 3.3 Update for
* on Mac OS X 10.4.x: XCode 2.1
Note: You can get both applications after a free registration at http://connect.apple.com
* JDK 1.4.2 plus latest SDK Updates (with full JDK SDK for the headers)
* an installed X-Server. We recommend Apple's X11 but you can also use the ones of X.org or Xfree86
* A minimum of 4 to 5GB for a standard build.
Note: Usage of disk space depends upon the number of localizations you build for.
More localizations means more disk space needed.
A minimum of 18GB for a full debug build.
* If you can afford it we recommend you to backup clean sources and work with a second set of sources.
With a second set of clean sources you can easily go back to clean sources if a module doesn't build,
a patch doesn't solve the problem, you have to revert a patch or for any other reason there may be.
In the meantime cvs sources could have been edited and you need to recompile more modules then just
one and that's probably not what you want...

===Determine the shell you use for compilation===

The default shell of a cleanly installed Mac OS X 10.3.x/Mac OS X 10.4.x is bash.
If you did an update to 10.3.x or 10.4.x from early versions of Mac OS X while keeping your personal settings you may still use the tcsh shell, the default shell of Mac OS X 10.0 to 10.2.x.

Where necessary this read-me distinguishes between bash and tcsh.

To determine the shell you currently use open Terminal.app and type the following command:

ps -p $$

The output shows you which shell you're currently using.

-/bin/bash or -bash means you are using bash

-/bin/tcsh or -tcsh means you are using the c-shell

===Getting OpenOffice.org and External Sources===

====Getting OpenOffice.org Source from CVS====

Once you have X properly installed, it's time to get the OpenOffice.org sources and other external sources. If you've built OpenOffice.org from previous sources and have applied other patches, you will need to start from scratch with a fresh CVS version of the sources.

Download the CVS distribution for SRC680_mXXX (replace XXX by the current milestonenumber):

1. Open a new Terminal (/Applications/Utilities/Terminal)
2. mkdir 680_mXXX/source
3. cd 680_mXXX/source
4. Now set the CVSROOT
* for bash do:
export CVSROOT=:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
* for tcsh do:
setenv CVSROOT :pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
5. cvs login
6. Enter the password anoncvs
7. cvs -z3 co -r SRC680_mXXX OpenOffice2
for later milestones simply replace the XXX with the most current milestonenumber
8. go get some coffee, or a beer, since it'll take a while to get it all

Note that if your computer is behind a firewall and you're trying to get the sources from the CVS server, you may need to find a proper way to get it to tunnel through the firewall. The protocol runs on port 2401, and some firewalls will not allow communication on this port.

Attention: We recommend a broadband connection and a not too small amount of volume or time left within your contract since the sources are about 300MB and the checkout could take up to an hour or longer depending on the server load.

For further informations on this topic see get the source

To get a second copy of the sources use the following commands within your 680_mXXX directory:

1. cd
2. mkdir build
3. cd build
4. cp -R ../source/* .

==== Additional software that's not in the official OpenOffice.org sources ====

Now that you have the sources it's time to get the software that is not in the official OOo Source Code Tree.

* The perl module Archive::Zip
* Apache Ant - optional - not needed
* gpc
* pkg-config
* gnu_copy
* cups headers (for those building on Mac OS X 10.3. Panther)
* gtk2 - optional - not needed
* X11

To install Archive::Zip use the following commands in Terminal.app:

1. perl -MCPAN -eshell
2. install Archive::Zip

If this is your first installation of a module using CPAN you're asked to configure the CPAN environment. If you're not 100% sure what to answer simply accept the default answers.

Note: In some cases using CPAN with Mac OS X is a bit problematic. In this case simply follow the instructions given here on this website http://sial.org/howto/perl/life-with-cpan/macosx/ to solve the problem.

You can grep Apache Ant 1.6.5 here: http://ant.apache.org/bindownload.cgi
Attention: Direct Link to the download site. Before the download starts you need to choose a mirror. The size of Apache Ant is about 6.4MB.

After the download put Apache Ant into the following directory: <your path>/680_mxx/apache-ant-1.6.5

GPC is available here: ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc231.tar.Z>

Attention: Direct Link to the download but it's only a few hundred KB.

Note: You can alternatively use the libart_lgpl library instead of GPC. This requires an additional configure flag (--enable-libart) and a precompiled libart library installed in a standard location, such as /usr/lib.

Since OS X comes with no pkg-config, or to be more specific it's simply not complete in OS X, you have to install it via fink (http://fink.sourceforge.net), MacPorts (http://www.macports.org) or the gentoo port system (http://www.metadistribution.org/macos/).

Begining with m101 for Mac OS X gnu_copy is needed to copy files within the build process of OOo. Please use your porting mechanism to install gnu_copy.
For Darwinports the package name is coreutils, for fink it's fileutils.

If you need cups headers (on Mac OS X 10.3., building reports "cups.h missing"), then download them from http://ftp.cusoo.org/MacOSX/Utilities/PowerPC/cups_Panther/cups.tar.gz and put the headers to "/usr/include/cups".

If you want to compile OpenOffice.org with gtk2 support you have to install gtk2 via your porting_mechanism
Note: The most current versions of gkt2 and pkg-config are in about 90% of all cases only available as sources that you need to compile and not as binaries. Please consider this while preparing your mac.

Additional Note for fink users: You need to install both packages gtk2 and gtk2-devel using fink install </package name>

Yes, there are other porting mechanisms out there such as the one of NetBSD or you can get precompiled versions of gtk, gnu_copy and pkg-config via pages like osxgnu but the author of these build instructions has no experiences with these so no recommendation for them here.

Note: If you need help with installing or maintaining packages please contact the project that provides the porting_mechanism.

It's also possible to compile pkg-config, gnu_copy as part of the gnu-coreutils and gtk2 without fink or Darwinports. Be aware that in this case you need to resolve the various dependencies yourself. So we recommend using one of the porting mechanisms.

Because OS X does not install X11 by default and up to now you haven't installed one, now may be the time do so.
There are various X for Mac OS X out there e.g. Apple's X11, XDarwin.org's XDarwin or simply use your porting_mechanism to install either X.org 6.8.x or Xfree86 >=4.3.
For help with your X11 please contact the provider of the package or your porting mechanism project

===Preparing to Build===

====Adding gpc to OOo sources====

1. uncompress <path to gpc>/gpc231.tar.Z
2. tar xvf <path to gpc>/gpc231.tar
3. cp <path to gpc>/gpc.[hc] <ooo source directory>/build/external/gpc/
4. rmdir gpc231

====Applying Patches====

To apply a patch
cd
into the direcotory for the module which needs to be patched and do a:
patch -p0 <path/to/the patch>

Most of the patches use the naming scheme
modul_(subdirectory_subdirectory_etc)_filetopatch.patch.

To find all current patches do a search for issues in component subcomponent MacOSX.

You can grab the patches necessary to avoid the freetype crash from my idisk public folder

Due to the fact that not all the patches are from one author it's sometimes necessary to change to the subdirectory/ies or not. In this case the patch knows which subdirectories to jump over.
====Additional steps for Mac OS X 10.4.x aka Tiger Users====

OpenOffice.org1.9.xxx milestones and OpenOffice.org 2.0.x stable both now compile with gcc 4.0. Remember that you have to use XCode2.1 gcc 4.0
If you're using Mac OS X 10.4 aka Tiger and you want to use gcc 3.3 instead of the default gcc 4.0 you can do so by using the following commands within your shell.

1. Open up a new Terminal
2. sudo gcc_select 3.3

Do not use XCode 2.2.1 due to [http://qa.openoffice.org/issues/show_bug.cgi?id=69314 Issue 69314]

===Building OpenOffice.org===
Now that we've got it all the source, it's time to execute the build!

1. Open up a new Terminal.
2. Configure for your build
3. cd <path to ooo>/680_mXXX/build/config_office
4. ./configure --with-x --with-lang="de fr en-US"
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home/
--with-ant-home=<path to 680_mxx>/apache-ant-1.6.5/ --with-epm=internal
--enable-mozab --enable-pasf --with-gtk2 --with-gnu-cp=<path to your version of gnu_copy>
--enable-fontconfig

Instead of using --with-freetype2=... you can also use --with-system-freetype
Attention: Darwinports gnu_copy is named gcp to avoid conflicts with Mac OS X cp

5. If configure fails it will output an error message saying what's missing or
what else causes it's breakage.
Be sure to also check the warnings configure outputs at the end of the configuration process.
Please report any breakage here with the error message output to dev@porting.openoffice.org
6. cd ..
7. ./bootstrap
8. Set up your shell build enviroment:
* for bash do:
PPC: source MacosxPPCEnv.Set.sh
Intel: source MacosxIntelEnv.Set.sh
* for tcsh do:
PPC: source MacosxPPCEnv.Set
Intel: source MacosxIntelEnv.Set
9. dmake
10. Report any and all build failures to mac@porting.openoffice.org mail list
11. cd instsetoo_native/unxmacxp.pro/OpenOffice/install
Within this directory you will find a folder for each language that
you build OpenOffice.org for. Those folders contain the installation disk images.

====Additional Informations for Darwinports Users====
When using Darwinports be sure to use ./configure without freetype since it leads to OpenOffice.org crashing with a version mismatch error when using Darwinport's freetype. You will find the additional patches needed to build freetype within OpenOffice.org in the subdirectory freetype2_patches of the patch archive.
====Using Mozilla within OpenOffice.org====

If you decided to use Mozilla packages to get special functions OpenOffice.org provides you, as I did in the example configure script, you have two choices to get them:

First:

You let OpenOffice.org compile them. Be aware that this adds additional tim to your compiling time.

If you decide to let OpenOffice.org compile Mozilla simply add
--enable-build-mozilla
to the ./configure script and OpenOffice.org will compile Mozilla within the moz directory.

1. Before building Mozilla be sure to download Mozilla Sources. You can get them e.g. here:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.5/source/
2. cp mozilla-source-1.7.5.tar.gz <your path>/680_mXXX/moz/download
3. cd <your path>/680_mXXX/moz
4. cd config_office
5. Use the same ./configure script out of step4 in paragraph "Buiding OpenOffice.org" and add
--enable-build-mozilla
6. Continue with Step 5 of the "Building OpenOffice.org" paragraph

OpenOffice.org should now compile mozilla within its build process.

Second:

You grab the Mozilla packages for PPC here:
http://florian-heckl.de/ooo/MACOSXGCCPinc.zip
http://florian-heckl.de/ooo/MACOSXGCCPlib.zip
http://florian-heckl.de/ooo/MACOSXGCCPruntime.zip
and put them into <ooo build directory>/680_mXXX/moz/zipped
OpenOffice.org should detect and use them.

For Intel please use the ones from http://eric.bachard.free.fr/mac/moz/zipped/ these libraries appear to be universal binaries, can someone building on PPC (with Tiger) please check at some point?

===Building the whole OpenOffice.org suite or just a single Project with Debug Information===

To build the whole OpenOffice.org Suite with debug informations add
--enable-debug
to the configure command.

To rebuild a complete project with debug information, remove all object files by removing the unxmacxp.pro directory. Then run dmake with the debug option set to true:

cd $SRC_ROOT/(module-name)
$SRC_ROOT/(module-name)> rm -rf unxmacxp.pro
$SRC_ROOT/(module-name)> build debug=true
$SRC_ROOT/(module-name)> deliver

[[Category:Porting]]
[[Category:MacOSX]]

DE/Buchprojekt

2006-07-16T20:41:00Z

Maveric:

[[Category:de.openoffice.org]]
== de.ooo-Buchprojekt (Gliederung) ==

Im bisherigen Verlauf der Diskussion auf [de-dev], die ich mit dem post:
http://de.openoffice.org/servlets/ReadMsg?list=dev&msgNo=25894
eingeleitet hatte, ergab sich bisher (angeregt von Uwe) die Meinung, wir sollten zunächst eine Gliederung für die Broschüren entwerfen und alles Weitere darauf aufbauend besprechen, sobald die Gliederung geklärt ist.
Deshalb hier meine erste Vorstellung zu einer Gliederung, die vielleicht als Grundlage der Diskussion tauglich ist. '''Am Ende der Diskussion sollte/muss dann eine Gliederung stehen, welche für das weitere Vorgehen Gültigkeit behält.'''

Folgende Vorbemerkungen:

(a)
Ich schlage vor für die Zukunft, zur einfacheren Unterscheidung, für die Broschüren die Arbeitstitel:

*"Programm-Broschüre" (für die Größere)
*"Community-Broschüre" (für die Kleinere)

zu verwenden.

(b)
Wir müssen uns bewusst sein, dass es Randbedingungen gibt, die objektiv gegeben und nicht beeinflussbar sind. Insbesondere meine ich hier den Seitenumfang der Broschüren, dessen Zustandekommen ich bereits in der Diskussion auf [de-dev] erläutert hatte.
Weil dieser Seitenumfang selbst für die halbwegs umfassende Erläuterung auch nur eines Moduls ungeeignet ist und darüber hinaus ohnehin noch etliche nicht modulspezifische Dinge (z.B. Installation) enthalten sein müssen, müssen wir uns unbedingt auf Kernaussagen beschränken.

(c)
Organisatorisch schlage ich vor, dass wir über die bisher bereits besprochenen Bereiche:

Koordination des Buchprojekts, insbesondere auch technische Koordination mit Galileo:
-->Jörg

Koordination der Inhalte der Broschüren:
-->Jacqueline

Endkorrektur/'Qualitätssicherung' seitens de.ooo:
-->Wolfgang

hinaus uns mit der Einigung auf die Gesamtgliederung der Broschüren auch gleich auf Verantwortliche für die (Detail)Koordination der Hauptkapitel einigen.
Mir scheint das sehr zweckmäßig, weil es kaum möglich sein wird, jedes Detail am Anfang zu berücksichtigen, und es auch ziemlich egal ist, ob wir letzlich für Writer 2 Seiten mehr oder weniger verwenden und dafür für entwas Anderes entsprechend mehr oder weniger, aber die Einhaltung der 'Eckdaten' muß gewährleitet sein.
Als Hauptkapitel _in diesem Sinne_ bitte ich (bezogen auf untenstehende Gliederung) zu verstehen:
Programm-Broschüre:
Kapitel 1, 2, 3, 5
Community-Broschüre:
Kapitel 3, 4

== Gliederung Community-Broschüre ==

Status: Vorschlag von Jörg

Stand: 01.05.2006

'''1. Wie entstand OOo? (2 Seiten)'''

'''2. Was ist, was will OOo? (10 Seiten)'''

'''3. Wie kann ich mithelfen? (33 Seiten)'''

3.1. das Projekt de.ooo

3.1.1. was tut de.ooo?

3.1.2. QA

3.1.3. Issuezilla

3.1.4. weitere wichtige Aufgaben

3.1.5. Wen ansprechen?

'''4. Wie OOo sonst unterstützen? (7)'''

4.1. Was können sie tun? (2 Seiten)

4.2. der Verein (1 Seite)

4.3. Sponsoring (1 Seite)

4.4. OOo nutzen (3)

4.4.1. Zusammenarbeit mit anderen Anwendungen (1 Seite)

4.4.2. OOo als Grundlage eigener Entwicklungn (2 Seiten)

'''5. FAQ (5 Seiten)'''

'''6. Informationsquellen (3 Seiten)'''

''Erläuterungen:''

Das für uns als de.ooo ganz entscheidend wichtige Kapitel wird das dritte sein, hier hatten sich auch bereits einige kompetente Schreiber angeboten.
In längerfristiger Sicht sind aber die Inhalte von 4.4. für uns als Projekt ganz entscheidend, Thomas (Krumbein) hatte bereits im Umfeld der CeBIT angedeutet, dass bezüglich 4.4.1 noch in diesem Jahr einiges zu erwarten ist. Nicht minder wichtig ist aber auch 4.4.2, denn hier gibt es noch Schwächen, es wäre beispielsweise ein Stück Normalität, wenn es endlich einmal eine Shareware gäbe, die auf OOo aufsetzt. Ich denke hier an die Sharewareautoren, die engagiert Makros-Sammlungen für MSO veröffentlichen, aber leider die Chancen, die OOo bietet noch nicht erkannt haben.
Kapitel 2 sollte wichtige Zusammenhänge verständlich für Außenstehende erläutern und insbesondere auf häufige Fehlinterpretationen bzgl. des Projektes eingehen. Hier würde ich mich gerne als Autor einbringen.

== Gliederung Programm-Broschüre ==

Stand: 15.07.2006

'''Hinweise zum Gebrauch der [http://projects.ooodev.org/~s0001u0002/sonstiges/OOo_Buchprojekt.ott Vorlage]:''' Bitte lest euch die enthaltenen Anmerkungen zur Verwendung der Formatvorlagen und insbesondere zu den Grafiken aufmerksam durch. Achtet auf auf die richtige Nummerierung der Abschnitte und der verknüpften Grafiken. Das erleichtert uns später das Zusammenführen der Teilkapitel.

'''Hinweise für die Korrekturleser:''' Um Mehrfacharbeit zu vermeiden, vermerkt bitte in unten stehender Tabelle in der Spalte "Status", wenn ihr gerade ein Kapitel Korrektur lest.

'''Vorläufige Gliederung:'''

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Kapitel
! width="240" | Beschreibung
! ca. Seiten
! Verfasser
! Status
! width="360" | Bemerkungen
|-
| '''0''' || '''[[DE:Buchprojekt/Programm-Broschuere_Kap0|Inhaltsverzeichnis]]''' || '''1 Seite''' || jrahemipour / joesch || ||
|-
| '''1.''' || '''[http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel1/Vorwort.odt Vorwort / Einleitung]''' || '''2 Seiten''' || jrahemipour / markomlm || Wolfgang hats gelesen, Korrekturen hat jrahemipour eingearbeitet || <b>Freigegeben</b>
|-
| '''2.''' || '''OpenOffice.org – Ein Überblick''' || '''[23 Seiten]''' || || ||
|-
| 2.1 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel2/Abschnitt2_1.odt Writer] || 4 Seiten || jrahemipour || von andreschnabel gegengelesen || <b>Freigegeben</b>
|-
| 2.2 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel2/Abschnitt2_2.odt Calc] || 4 Seiten ||volkerme || von jrahemipour und andreschnabel gegengelesen|| <b>Freigegeben</b>
|-
| 2.3 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel2/Abschnitt2_3.odt Impress] || 2 Seiten || mkirchner || von jrahemipour und andreschnabel gegengelesen || <b>Freigegeben</b>
|-
| 2.4 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel2/Abschnitt2_4.odt Draw] || 3 Seiten || Edgar || Korrekturgelesen von Wolfgang und jrahemipour ||<b>Freigegeben</b>
|-
| 2.5 ||[http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel2/Abschnitt2_5.odt Base] || 3 Seiten || mechtilde ||von Regina gegengelesen - zur Korrekturlesung bei andreschnabel - Korrekturen eingefügt, fertig|| <b>Freigegeben</b>
|-
| 2.6 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel2/Abschnitt2_6.odt Math] || 3 Seiten || nuernbergerj || Korrektur gelesen von volkerme und jrahemipour || <b>Freigegeben</b>
|-
| 2.7 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel2/Abschnitt2_7.odt Übergreifende Funktionen] || 3 Seiten || andreschnabel || korrigiert von Wolfgang und jrahemipour || <b>Freigegeben</b>
|-
| '''3.''' || '''Installation''' || '''[20 Seiten]''' || markomlm / joesch || ||
|-
| gesamt || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel3/Kap3_Installation.odt Installation gesamt] || 20 Seiten || markomlm / joesch / u.A. || von jrahemipour gegengelesen -> zwei Anmerkungen zur Debian-Installation - alle Änderungen von Jacqueline übernommen plus Änderungen von Marko und Mechtilde eingearbeitet (16.07. 11:45)- das Dokument muß IMHO nochmals Korrektur gelesen werden, zumindest Linux joesch||habe Deb-Abschnitt mit den Änderungen von Marko und Jacqueline nochmal neu zusammengestellt und als Kap3_InstallationDeb.odt auf dem Server abgelegt. Mechtilde Mindestanforderungen Arbeitsspeicher für Mac OS X hinzugefügt. Eric||
|-
| 3.1 || Systemvoraussetzungen|| || siehe gesamt || ||
|-
| 3.2 || Windows || || siehe gesamt|| ||
|-
| 3.3 || Linux || || siehe gesamt|| ||
|-
| 3.4 || MacOS || || siehe gesamt|| ||
|-
| 3.5 || Gemeinsames || || siehe gesamt|| ||
|-
| 3.6 || FAQ / häufige Probleme (bei der Installation) || || siehe gesamt|| ||
|-
| 3.7 || Erster Programmstart || || siehe gesamt|| ||
|-
| '''4.''' || '''Einrichtungshilfen und Werkzeuge''' || '''[20 Seiten]''' || || ||
|-
| 4.1 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel4/Abschnitt4_1.odt Gemeinsame Elemente der Arbeitsbereiche] || 3 Seiten || tpaukert, hfischer || bereits von kfischer gegengelesen, korrektur gelesen von andreschnabel ||
|-
| 4.2 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel4/Abschnitt4_2.odt Arbeitsbereich einrichten] || 4 Seiten || tpaukert || von hfischer überarbeitet, von volkerme gelesen und ergänzt; diese Version verworfen, neu geschrieben; gegengelesen von kfischer ||
|-
| 4.3 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel4/Abschnitt4_3.odt Besondere Werkzeuge] || 5 Seiten || tpaukert || Zur inhaltlichen Korrektur frei; bei hfischer zur Korrektur || z.B. Navigator, Ex-Stylist
|-
| 4.4 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel4/Abschnitt4_4.odt Dokumentenaustausch] || 4 Seiten || jrahemipour || korrekturgelesen von Wolfgang || <b>Freigegeben</b>
|-
| 4.5 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel4/Abschnitt4_5.odt FAQ] || 4 Seiten || volkerme || Zur Korrektur frei || Überschneidungen mit anderen Kapitel sind raus. Freigabe?
|-
| '''5.''' || '''Fachartikel zu OpenOffice.org''' || '''[26 Seiten]''' || || ||
|-
| 5.1 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel5/51_Mal_hoch_mal_quer.odt Mal hoch mal quer]|| 2 Seiten || Sabine Heimsch || korrekturgelesen von Wolfgang; nochmal zur Korrektur bei hfischer || Nummerierung ist jetzt okay, Wolfgang
|-
| 5.2 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel5/5_2_DINA4Dilemma.odt Das DIN A4 Dilemma] || 4 Seiten ||Regina Henschel || Wolfgang und jrahemipour haben korrekturgelesen || <b>Freigegeben</b>
|-
| 5.3 || Erstellung eines Bestellformulars in Calc zur Verwendung im Außendienst || 3 Seiten || Sabine Heimsch || ||Das Formular ist fertig, der Text zu 80%, aber die Formatvorlagen passen noch nicht. Soll das Kapitel noch fertig gestellt werden?
|-
| 5.4 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel5/5_4_dublettensuche_in_Calc.odt Dublettensuche in Calc] || 2 Seiten || petertietler || Dokument in Vorlage gesetzt und korrekturgelesen, Wolfgang ||
|-
| 5.5 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel5/5_5animiertegrafiken_am_grafikfest01.odt Animierte Grafiken in Impress erstellen] || 5 Seiten || andreasma || Korrekturgelesen von Wolfgang, Inhalt und Deutsch okay ||
|-
| 5.6 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel5/5_6DatenImportExport.odt Daten Import und Export] || 3 Seiten || regina ||von mechtilde gegengelesen ||
|-
| 5.7 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel5/57_Calc_joesch.odt Werte und Zahlenformate in Calc] || 3 Seiten ||joesch ||nochmal korrekturgelesen von Wolfgang am 16.7.06 um 20 Uhr ||
|-
| 5.8 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel5/5_8_Beitrag_Wolle.odt Eine technische Zeichnung mit DRAW] || 4 Seiten|| Wolfgang Uhlig|| korrekturgelesen von andreschnabel, Änderungen direkt eingearbeitet ||
|-
| 5.9 || Fachartikel 9 || || || ||
|-
| '''6.''' || '''[http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel6/Kapitel6.odt OpenOffice.org für Umsteiger] ''' || '''6 Seiten''' || Franz Grieser || Einige Anmerkungen von jrahemipour, die Wolfgang unterstützt. Auch von mir eine Anmerkung, sonst okay, Nochmals gelesen von volkerme - zwei inhaltliche Anmerkungen eingefügt joesch||
|-
| '''7.''' || '''OOo und Ergänzungen''' || '''8 Seiten''' || || ||
|-
| 7.1 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel7/Abschnitt7_1.odt wie und wo wird OOo angeboten] || 2 Seiten || floeff || von jrahemipour gegengelesen || <b>Freigegeben</b>
|-
| 7.2 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel7/7_2_Erweiterungen-in-OOo.odt wesentliche Erweiterungen/Zusätze] || 2 Seiten || joesch || von Wolfgang korrigiert || <b>Freigegeben</b>
|-
| 7.3 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel7/7_3_Makros_installieren.odt Makros installieren]|| 4 Seiten || joesch || Wolfgang hat korrekturgelesen || Liefert dem Nutzer Infos, wie er insbesondere mit Makros zurechtkommt. Hintergrund ist, dass es inzwischen derer viele gibt, aber wegen unterschiedlicher Benutzung/Installation diese für den Normal-User schwer erfolgreich zu benutzen sind und für reine 'Arbeitsmakros' niemand gezwungen sein sollte, sich erst in Basic einzuarbeiten. In diesem Rahmen kann man auch verstärkt auf Dinge verweisen, die die PrOOo-Box mitbringt
|-
| '''8.''' || '''Wo gibt es Hilfe''' || '''[12 Seiten]''' || || || Kommentierte Linksammlung
|-
| 8.1 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel8/abschnitt8_1.odt Anwender-Hilfe] || 4 Seiten || andreschnabel || k.gelesen von Wolfgang, volkerme, jrahemipour || <b>Freigegeben</b>
|-
| 8.2 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel8/abschnitt8_2.odt Dokumentation und Infos im Netz] || 5 Seiten || hfischer || korrekturgelesen von Wolfgang ||
|-
| 8.3 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel8/abschnitt8_3.odt Literatur zu OOo] || 2 Seiten || nielsjende|| k.gelesen Wolfgang, Liste strukturiert || Der Punkt scheint mir durchaus erwähnenswert, zumal wir hier die OOo-Bibliothek ein wenig zentraler erwähnen können (für uns nützlich wegen der Spendenzusage von Galileo, siehe meinen einleitenden post auf dev)
|-
| 8.4 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel8/Abschnitt8_4.odt Dienstleistungen] || 1 Seite || floeff || von jrahemipour gegengelesen || <b>Freigegeben</b>
|-
| '''9.''' || '''Übersichten''' || '''[4 Seiten]''' || || ||
|-
| 9.1 || [http://projects.ooodev.org/buchprojekt/programm_broschuere/Kapitel9/Abschnitt9_1.odt Tastenkürzel] || 4 Seiten || Vera Unverzagt || k-gelesen v. Wolfgang: in Ordnung, nochmal gelesen von volkerme und jrahemipour || <b>Freigegeben</b>
|-
| 9.2 || Übersichten für Math|| || || <b>entfällt</b> ||
|-
| 9. || ...|| || || ||
|-
| '''10.''' || '''Sonstiges''' || '''[2 Seiten]''' || || ||
|-
| 10.1 || Autorenübersicht || || joesch / jrahemipour || || Auflistung aller Autoren mit Verweis auf Kapitel, Danksagung an alle Mitwirkenden
|}

== Aufstellung der Projektbeteiligten ==

Stand: 01.05.2006

Folgende Community-Mitglieder haben ihre Mithilfe zugesagt:

(Sorry, es ist im Thread auf [de-dev] alles etwas unübersichtlich, weshalb ich ggf. die Zusagen für bestimmte Dinge aus den mails (auch PM) heraus etwas interpretiert habe, stimmt das mit Euren Absichten nicht überein ist das natürlich nicht bindend.)

*Marko

-Installationshandbuch

-Dokumente von oooauthors

*Michael

-Beitrag für Community-Broschüre und/oder Korektur

*Volker

-Hilfe für Webseite an

-sonstige Hilfe

*Florian

-Hilfe für Installationsteil

-technische Hilfe (Server)

*Uwe

-Mac

-QA

*Vera

-Korrekturlesen

-ggf. Sonstiges

*Jacqueline

-Koordination Programm-Broschüre (Community-Broschüre ?)

-eigene Text-Beiträge

*Wolfgang

-Endkontrolle

-einen eigenen Textbeitrag

*André

-Textbeiträge zum Bereich "Testen"

-QA

-Sonstiges

*Eric

-Korrekturlesen

-Mac

-QA

*Edgar

-Textbeiträge

*Franz

-Textbeiträge

*Andreas

-Textbeiträge (u.a. Animierte Bilder / GIFs mit Impress erstellen)

*Jörg

-Projektkoordination mit Galileo

-technische Koordination (Server etc.) mit Florian und Volker (Webseite(n))

-Koordination der Community-Broschüre?

-Textbeiträge