Apache OpenOffice Wiki - User contributions [en]

Extensions Integration into Installation Set

2007-10-03T09:36:58Z

Pagalmes: /* A few questions */

How to integrate an extension into OpenOffice.org / StarOffice installation sets.

== Global rules for extensions ==

All extensions that need to be registered during installation process have to be installed into the directory “share/extension/install” in the Office installation. "Installed" means in this context only "copied" or "unpacked" from the installation set and does not include the registration process in the Office product. The scripts (Unix) and CustomActions (Windows), that register the extensions using the tool "unopkg", look only in the directory “share/extension/install” for oxt files.

All extensions have to be included into an own module in scp project. Therefore they are packed into their own RPM (Linux) or Solaris package (Solaris) and can be selected and deselected during the installation process on all platforms. The module defined in scp should not contain any additional content.

=== A few questions ===

==== QUESTIONS paragraph 1 ====

- "Extensions need to be copied or unpacked", that means that we can put the zip, oxt... or the unzipped version of the extension?

- What format are accepted (OXT, ZIP, .uno.pkg)? That means are old extensions supported?

- Can those instructions be used to add customization to the OOo msi package or are those instructions only valid if you add the extension to the build tree and compile OOo with the extension?

- Talking about the customization of the OOo MSI, under Windows and Unix, do we need to create a custom action or a script, or does the OOo process manages that?

- If we need to create the custom action, which command line do we need to use (unopkg add --shared <extension name>)?

- Will the extension be installed on the OOo install (unopkg add --shared <extension name>) or in the profile with the option?

==== QUESTIONS paragraph 2 ====

- What is that SCP project you are talking about? You are talking about including the extension to the build tree and compile OOo with the extension?

- Do we need to create SCP files also for Windows? In that second paragraph, you only deal with RPM (Linux) or Solaris package (Solaris).

- What do you mean by "additional content"?

== Changes in scp projects ==

In scp projects you have to add a file (the extension) and a module. This can be easily explained with the following example of the extension

File gid_File_Oxt_Myextension
TXT_FILE_BODY;
Styles = (PACKED);
Dir = gid_Dir_Share_Extension_Install;
Name = "myExtension.oxt";
End

It is important to use “gid_Dir_Share_Extension_Install”. Only with this directory global id the extensions are installed into the correct directory.

Additionally a module has to be defined in scp projects:

Module gid_Module_Optional_Myextension
Name = "My extension”;
Description = "Description of my extension";
ParentID = gid_Module_Optional;
Default = YES;
Files = (gid_File_Oxt_Myextension);
End

Of course “Name” and “Description” have to be localized.
That is all in the scp projects. This has to be done for all platforms. The additional tasks are platform dependent.

== Platform dependent tasks ==

=== Windows ===

Congratulations, you have done it already. There are two CustomActions executed
at the end of the installation and at the start of the deinstallation. The
CustomAction at the end of the installation registers all extensions, that are
located in "share/extension/install". The CustomAction for the uninstallation process deregisters all extensions located in "share/extension/install". Therefore your new extension is automatically registered or deregistered without any further action.

=== Unix ===

For the Unix platforms it is required, that a RPM or Solaris package is created from the content of the new module that you defined in scp projects. Therefore you have to define a new package, which currently happens in the project instsetoo_native. The file "instsetoo_native/inc_openoffice/unix/packagelist.txt" is a list of all packages of OpenOffice.org.

The new package has a dependency to the package core02, which contains the
unopkg executable. Additionally this new package must include as "script" the
script file "shellscripts_extensions.txt", that contains three scripts required for
RPM installation.
Example:

Start
module = "gid_Module_Optional_Myextension"
script = "shellscripts_extensions.txt"
solarispackagename = "%WITHOUTDOTUNIXPRODUCTNAME-myextension"
solarisrequires = "%WITHOUTDOTUNIXPRODUCTNAME-core02"
packagename = "%UNIXPRODUCTNAME-myextension"
linuxreplaces = "%WITHOUTDOTUNIXPRODUCTNAME-myextension"
freebsdrequires = "%UNIXPRODUCTNAME-core02"
requires = "%UNIXPRODUCTNAME-core02"
copyright = "1999-2006 by OpenOffice.org"
vendor = "OpenOffice.org"
description = "MY extension for %PRODUCTNAME %PRODUCTVERSION"
destpath = "/opt/%UNIXPRODUCTNAME%PRODUCTVERSION"
End

That's it. Now the installation set contains a new package, that includes your extension. For Linux and Solaris there are different procedures, in which the extension is registered in the Office suite:

=== Linux ===

The RPMs including extensions have several scripts included, in which unopkg is called. This is required in "preinstall", "postinstall" and "preremove". Therefore the extension is registered after the rpm installation and deregistered if the rpm is removed.

=== Solaris ===

Still under construction, but a solution will be available soon. The Solaris solution differs from the Linux solution, because unopkg must not be called directly in the scripts included in the package.

[[Category:Extensions]]

Extensions Integration into Installation Set

2007-10-03T09:35:21Z

Pagalmes: /* Global rules for extensions */

How to integrate an extension into OpenOffice.org / StarOffice installation sets.

== Global rules for extensions ==

All extensions that need to be registered during installation process have to be installed into the directory “share/extension/install” in the Office installation. "Installed" means in this context only "copied" or "unpacked" from the installation set and does not include the registration process in the Office product. The scripts (Unix) and CustomActions (Windows), that register the extensions using the tool "unopkg", look only in the directory “share/extension/install” for oxt files.

All extensions have to be included into an own module in scp project. Therefore they are packed into their own RPM (Linux) or Solaris package (Solaris) and can be selected and deselected during the installation process on all platforms. The module defined in scp should not contain any additional content.

=== A few questions ===

==== QUESTIONS paragraph 1 ====

- "Extensions need to be copied or unpacked", that means that we can put the zip, oxt... or the unzipped version of the extension?
- What format are accepted (OXT, ZIP, .uno.pkg)? That means are old extensions supported?

- Can those instructions be used to add customization to the OOo msi package or are those instructions only valid if you add the extension to the build tree and compile OOo with the extension?
- Talking about the customization of the OOo MSI, under Windows and Unix, do we need to create a custom action or a script, or does the OOo process manages that?
- If we need to create the custom action, which command line do we need to use (unopkg add --shared <extension name>)?
- Will the extension be installed on the OOo install (unopkg add --shared <extension name>) or in the profile with the option?

==== QUESTIONS paragraph 2 ====

- What is that SCP project you are talking about? You are talking about including the extension to the build tree and compile OOo with the extension?
- Do we need to create SCP files also for Windows? In that second paragraph, you only deal with RPM (Linux) or Solaris package (Solaris).
- What do you mean by "additional content"?

== Changes in scp projects ==

In scp projects you have to add a file (the extension) and a module. This can be easily explained with the following example of the extension

File gid_File_Oxt_Myextension
TXT_FILE_BODY;
Styles = (PACKED);
Dir = gid_Dir_Share_Extension_Install;
Name = "myExtension.oxt";
End

It is important to use “gid_Dir_Share_Extension_Install”. Only with this directory global id the extensions are installed into the correct directory.

Additionally a module has to be defined in scp projects:

Module gid_Module_Optional_Myextension
Name = "My extension”;
Description = "Description of my extension";
ParentID = gid_Module_Optional;
Default = YES;
Files = (gid_File_Oxt_Myextension);
End

Of course “Name” and “Description” have to be localized.
That is all in the scp projects. This has to be done for all platforms. The additional tasks are platform dependent.

== Platform dependent tasks ==

=== Windows ===

Congratulations, you have done it already. There are two CustomActions executed
at the end of the installation and at the start of the deinstallation. The
CustomAction at the end of the installation registers all extensions, that are
located in "share/extension/install". The CustomAction for the uninstallation process deregisters all extensions located in "share/extension/install". Therefore your new extension is automatically registered or deregistered without any further action.

=== Unix ===

For the Unix platforms it is required, that a RPM or Solaris package is created from the content of the new module that you defined in scp projects. Therefore you have to define a new package, which currently happens in the project instsetoo_native. The file "instsetoo_native/inc_openoffice/unix/packagelist.txt" is a list of all packages of OpenOffice.org.

The new package has a dependency to the package core02, which contains the
unopkg executable. Additionally this new package must include as "script" the
script file "shellscripts_extensions.txt", that contains three scripts required for
RPM installation.
Example:

Start
module = "gid_Module_Optional_Myextension"
script = "shellscripts_extensions.txt"
solarispackagename = "%WITHOUTDOTUNIXPRODUCTNAME-myextension"
solarisrequires = "%WITHOUTDOTUNIXPRODUCTNAME-core02"
packagename = "%UNIXPRODUCTNAME-myextension"
linuxreplaces = "%WITHOUTDOTUNIXPRODUCTNAME-myextension"
freebsdrequires = "%UNIXPRODUCTNAME-core02"
requires = "%UNIXPRODUCTNAME-core02"
copyright = "1999-2006 by OpenOffice.org"
vendor = "OpenOffice.org"
description = "MY extension for %PRODUCTNAME %PRODUCTVERSION"
destpath = "/opt/%UNIXPRODUCTNAME%PRODUCTVERSION"
End

That's it. Now the installation set contains a new package, that includes your extension. For Linux and Solaris there are different procedures, in which the extension is registered in the Office suite:

=== Linux ===

The RPMs including extensions have several scripts included, in which unopkg is called. This is required in "preinstall", "postinstall" and "preremove". Therefore the extension is registered after the rpm installation and deregistered if the rpm is removed.

=== Solaris ===

Still under construction, but a solution will be available soon. The Solaris solution differs from the Linux solution, because unopkg must not be called directly in the scripts included in the package.

[[Category:Extensions]]

Extensions Integration into Installation Set

2007-10-03T09:33:08Z

Pagalmes: /* Global rules for extensions */

How to integrate an extension into OpenOffice.org / StarOffice installation sets.

== Global rules for extensions ==

All extensions that need to be registered during installation process have to be installed into the directory “share/extension/install” in the Office installation. "Installed" means in this context only "copied" or "unpacked" from the installation set and does not include the registration process in the Office product. The scripts (Unix) and CustomActions (Windows), that register the extensions using the tool "unopkg", look only in the directory “share/extension/install” for oxt files.

All extensions have to be included into an own module in scp project. Therefore they are packed into their own RPM (Linux) or Solaris package (Solaris) and can be selected and deselected during the installation process on all platforms. The module defined in scp should not contain any additional content.

QUESTIONS paragraph 1

- "Extensions need to be copied or unpacked", that means that we can put the zip, oxt... or the unzipped version of the extension?
- What format are accepted (OXT, ZIP, .uno.pkg)? That means are old extensions supported?

- Can those instructions be used to add customization to the OOo msi package or are those instructions only valid if you add the extension to the build tree and compile OOo with the extension?
- Talking about the customization of the OOo MSI, under Windows and Unix, do we need to create a custom action or a script, or does the OOo process manages that?
- If we need to create the custom action, which command line do we need to use (unopkg add --shared <extension name>)?
- Will the extension be installed on the OOo install (unopkg add --shared <extension name>) or in the profile with the option?

QUESTIONS paragraph 2

- What is that SCP project you are talking about? You are talking about including the extension to the build tree and compile OOo with the extension?
- Do we need to create SCP files also for Windows? In that second paragraph, you only deal with RPM (Linux) or Solaris package (Solaris).
- What do you mean by "additional content"?

== Changes in scp projects ==

In scp projects you have to add a file (the extension) and a module. This can be easily explained with the following example of the extension

File gid_File_Oxt_Myextension
TXT_FILE_BODY;
Styles = (PACKED);
Dir = gid_Dir_Share_Extension_Install;
Name = "myExtension.oxt";
End

It is important to use “gid_Dir_Share_Extension_Install”. Only with this directory global id the extensions are installed into the correct directory.

Additionally a module has to be defined in scp projects:

Module gid_Module_Optional_Myextension
Name = "My extension”;
Description = "Description of my extension";
ParentID = gid_Module_Optional;
Default = YES;
Files = (gid_File_Oxt_Myextension);
End

Of course “Name” and “Description” have to be localized.
That is all in the scp projects. This has to be done for all platforms. The additional tasks are platform dependent.

== Platform dependent tasks ==

=== Windows ===

Congratulations, you have done it already. There are two CustomActions executed
at the end of the installation and at the start of the deinstallation. The
CustomAction at the end of the installation registers all extensions, that are
located in "share/extension/install". The CustomAction for the uninstallation process deregisters all extensions located in "share/extension/install". Therefore your new extension is automatically registered or deregistered without any further action.

=== Unix ===

For the Unix platforms it is required, that a RPM or Solaris package is created from the content of the new module that you defined in scp projects. Therefore you have to define a new package, which currently happens in the project instsetoo_native. The file "instsetoo_native/inc_openoffice/unix/packagelist.txt" is a list of all packages of OpenOffice.org.

The new package has a dependency to the package core02, which contains the
unopkg executable. Additionally this new package must include as "script" the
script file "shellscripts_extensions.txt", that contains three scripts required for
RPM installation.
Example:

Start
module = "gid_Module_Optional_Myextension"
script = "shellscripts_extensions.txt"
solarispackagename = "%WITHOUTDOTUNIXPRODUCTNAME-myextension"
solarisrequires = "%WITHOUTDOTUNIXPRODUCTNAME-core02"
packagename = "%UNIXPRODUCTNAME-myextension"
linuxreplaces = "%WITHOUTDOTUNIXPRODUCTNAME-myextension"
freebsdrequires = "%UNIXPRODUCTNAME-core02"
requires = "%UNIXPRODUCTNAME-core02"
copyright = "1999-2006 by OpenOffice.org"
vendor = "OpenOffice.org"
description = "MY extension for %PRODUCTNAME %PRODUCTVERSION"
destpath = "/opt/%UNIXPRODUCTNAME%PRODUCTVERSION"
End

That's it. Now the installation set contains a new package, that includes your extension. For Linux and Solaris there are different procedures, in which the extension is registered in the Office suite:

=== Linux ===

The RPMs including extensions have several scripts included, in which unopkg is called. This is required in "preinstall", "postinstall" and "preremove". Therefore the extension is registered after the rpm installation and deregistered if the rpm is removed.

=== Solaris ===

Still under construction, but a solution will be available soon. The Solaris solution differs from the Linux solution, because unopkg must not be called directly in the scripts included in the package.

[[Category:Extensions]]

FR/FeaturesCalc

2007-07-30T12:24:53Z

Pagalmes: /* DataPilot */

= Sort =
* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=sort&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Chart-Unconfirmed&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query All sort Issues]

* Sorting should default to selected column : [http://distribution.openoffice.org/issues/show_bug.cgi?id=7277 7277]
* Data sorting by using more than 3 items (columns) : [http://distribution.openoffice.org/issues/show_bug.cgi?id=10933 10933] and [http://distribution.openoffice.org/issues/show_bug.cgi?id=22884 22884]
* Sort by number groups : [http://distribution.openoffice.org/issues/show_bug.cgi?id=22419 22419]
* Title lines are sorted as data : [http://distribution.openoffice.org/issues/show_bug.cgi?id=22758 22758] and [http://distribution.openoffice.org/issues/show_bug.cgi?id=54748 54748]
* Cell notes do not move when cells are sorted : [http://distribution.openoffice.org/issues/show_bug.cgi?id=59745 59745]
* Ability to sort subtotals : [http://distribution.openoffice.org/issues/show_bug.cgi?id=70873 70873]

= DataPilot =

* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=datapilot&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Chart-Unconfirmed&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query All DataPilot issues]
* Change datapilot source range [http://qa.openoffice.org/issues/show_bug.cgi?id=23658 23658]
* Allow more than 8 data fields : [http://distribution.openoffice.org/issues/show_bug.cgi?id=5759 5759]
* Cell Styles not changeable to datapilot generated cells : [http://distribution.openoffice.org/issues/show_bug.cgi?id=11103 11103] and [http://distribution.openoffice.org/issues/show_bug.cgi?id=53234 53234]
* Allow to change labels : [http://distribution.openoffice.org/issues/show_bug.cgi?id=22029 22029]
* Copies of Datapilot are non-functional : [http://distribution.openoffice.org/issues/show_bug.cgi?id=27611 27611]
* Keep formatting associated with items : [http://distribution.openoffice.org/issues/show_bug.cgi?id=32303 32303]
* Consolidation areas as source : [http://distribution.openoffice.org/issues/show_bug.cgi?id=32306 32306]
* Display of empty results and errors : [http://distribution.openoffice.org/issues/show_bug.cgi?id=32308 32308]
* Double-click in Datapilot cell should provide calculation data of that cell : [http://distribution.openoffice.org/issues/show_bug.cgi?id=57030 57030]
* Sorting by dataField : [http://distribution.openoffice.org/issues/show_bug.cgi?id=72304 72304]

= Merge cells =
* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=merge&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Chart-Unconfirmed&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query All Merge Cells issues]

* Ability to merge cells already merged : [http://distribution.openoffice.org/issues/show_bug.cgi?id=2131 2131]
* Copying across fromulas from one merged cell to another : [http://distribution.openoffice.org/issues/show_bug.cgi?id=7500 7500]
* Allow deleting from merged ranges : [http://distribution.openoffice.org/issues/show_bug.cgi?id=8363 8363]
* Merge Contain Cells : [http://distribution.openoffice.org/issues/show_bug.cgi?id=40686 40686]
* Validity/Input Help Does NOT Work With Merged Cells : [http://distribution.openoffice.org/issues/show_bug.cgi?id=43818 43818]
* Calc - "column optimal width" does not work on merged cells : [http://distribution.openoffice.org/issues/show_bug.cgi?id=50193 50193]
* Merged cells do not drag-fill properly : [http://distribution.openoffice.org/issues/show_bug.cgi?id=66028 66028]
* Recording changes should not disable merge cell : [http://distribution.openoffice.org/issues/show_bug.cgi?id=68742 68742]
* Unexpected behavior when extending merged cells : [http://distribution.openoffice.org/issues/show_bug.cgi?id=72178 72178]

= AutoFilter =
* [http://distribution.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=TASK&issue_type=PATCH&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=autofilter&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time All AutoFilter issues]

* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=filter&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Chart-Unconfirmed&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query All Filter issues]
* Autofilter works just on one sheet (only one auto-range per document) : [http://distribution.openoffice.org/issues/show_bug.cgi?id=12666 12666]
* Add wildcards to the standard autofilter : [http://distribution.openoffice.org/issues/show_bug.cgi?id=17993 17993]
* Up standard autofilter fields from 3 to 4 : [http://distribution.openoffice.org/issues/show_bug.cgi?id=17995 17995]
* Basing autofiltering on the result set, not all rows : [http://distribution.openoffice.org/issues/show_bug.cgi?id=27745 27745]
* Show resulting number of rows in status bar when using autofilter : [http://distribution.openoffice.org/issues/show_bug.cgi?id=28268 28268]
* Behavior with cut/copy/paste/fill cells and autofilter : [http://distribution.openoffice.org/issues/show_bug.cgi?id=33851 33851]
* Empty / Non Empty options for Autofilter meny : [http://distribution.openoffice.org/issues/show_bug.cgi?id=35578 35578]
* No option to permit autofilter in protected sheets when exporting as XLS : [http://distribution.openoffice.org/issues/show_bug.cgi?id=57708 57708]
* Autofilter does not recognize added entries : [http://distribution.openoffice.org/issues/show_bug.cgi?id=59229 59229]
* AutoFilter: Not intuitive : [http://distribution.openoffice.org/issues/show_bug.cgi?id=76277 76277]

= Multiple sheets =
* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=multi+sheet&short_desc_type=allwords&long_desc=&long_desc_type=allwords&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&namedcmd=Calc-2.3&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query All issues content "Multi + Sheet"]
* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=sheet&short_desc_type=allwords&long_desc=&long_desc_type=allwords&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 All Sheet issues]
* Cannot insert lines on multiple sheets : [http://qa.openoffice.org/issues/show_bug.cgi?id=23263 23263]
* Add/delete rows/columns across selected sheets : [http://qa.openoffice.org/issues/show_bug.cgi?id=7088 7088]
* Add "Deselect all sheet" to context menu of worksheet tab menu : [http://qa.openoffice.org/issues/show_bug.cgi?id=7921 7921]
* Multi-sheet paste special with shift down broken : [http://qa.openoffice.org/issues/show_bug.cgi?id=17044 17044] or [http://qa.openoffice.org/issues/show_bug.cgi?id=29849 29849]
* Range Selection Lost When Switching Between Sheet Tabs : [http://qa.openoffice.org/issues/show_bug.cgi?id=25643 25643]
* Selection of multiple sheets using short-cut keys: selection works but not deselection : [http://qa.openoffice.org/issues/show_bug.cgi?id=38546 38546]
* Allow to send a single sheet from multi sheet document as email : [http://qa.openoffice.org/issues/show_bug.cgi?id=71751 71751]

= Print =
* [http://distribution.openoffice.org/issues/buglist.cgi?resort=1&Submit%20query=Submit%20query;issue_type=ENHANCEMENT;issue_type=FEATURE;component=Spreadsheet;issue_status=UNCONFIRMED;issue_status=NEW;issue_status=STARTED;issue_status=REOPENED;issue_status=RESOLVED;email1=;emailtype1=exact;emailassigned_to1=1;email2=;emailtype2=exact;emailreporter2=1;issueidtype=include;issue_id=;changedin=;votes=;chfieldfrom=;chfieldto=Now;chfieldvalue=;short_desc=print;short_desc_type=allwords;long_desc=;long_desc_type=allwords;issue_file_loc=;issue_file_loc_type=substring;status_whiteboard=;status_whiteboard_type=substring;keywords=;keywords_type=anytokens;field0-0-0=noop;type0-0-0=noop;value0-0-0=;namedcmd=Chart-Unconfirmed;newqueryname=&order=issues.votes%20desc%2C%20issues.issue_status%2C%20issues.priority%2C%20issues.issue_id All issues contain "print" sort by votes]

* In Calc defined print ranges/areas do not get copied if one creates a copy of a sheet : [http://distribution.openoffice.org/issues/show_bug.cgi?id=3560 3560]
* Print Selection only works for selected cells, not other selected objects : [http://distribution.openoffice.org/issues/show_bug.cgi?id=3992 3992]
* Printing a sheet on a specified number of pages : [http://distribution.openoffice.org/issues/show_bug.cgi?id=11336 11336]
* Allows to set the page margins in the "Print Preview" dialog by dragging margin indicator lines : [http://distribution.openoffice.org/issues/show_bug.cgi?id=11395 11395]
* Ability to print individual objects : [http://distribution.openoffice.org/issues/show_bug.cgi?id=14900 14900]
* Page-preview under print : [http://distribution.openoffice.org/issues/show_bug.cgi?id=17787 17787]
* Printing in more than one column : [http://distribution.openoffice.org/issues/show_bug.cgi?id=19124 19124]
* Page preview for Selection : [http://distribution.openoffice.org/issues/show_bug.cgi?id=22762 22762]
* Make printing named ranges easier : [http://distribution.openoffice.org/issues/show_bug.cgi?id=24830 24830]
* Unable to select different collumns to print : [http://distribution.openoffice.org/issues/show_bug.cgi?id=24886 24886]
* Moving a page break in page break preview makes only _one_ print range : [http://distribution.openoffice.org/issues/show_bug.cgi?id=27245 27245]
* Current sheet pagenumbers should be shown in print dialog : [http://distribution.openoffice.org/issues/show_bug.cgi?id=27440 27440]
* Print Preview Scale adjustment stays with page # not affected tab : [http://distribution.openoffice.org/issues/show_bug.cgi?id=27473 27473]
* Keeping merged ranges together when printing : [http://distribution.openoffice.org/issues/show_bug.cgi?id=28433 28433]
* Go to page missing in Print Preview : [http://distribution.openoffice.org/issues/show_bug.cgi?id=44032 44032]
* Print active sheet as default : [http://distribution.openoffice.org/issues/show_bug.cgi?id=45046 45046]
* Print notes on same page : [http://distribution.openoffice.org/issues/show_bug.cgi?id=45493 45493]
* Add NOPRINTROW and NOPRINTCOL functions : [http://distribution.openoffice.org/issues/show_bug.cgi?id=54039 54039]
* Adjusting Columns in Print Preview : [http://distribution.openoffice.org/issues/show_bug.cgi?id=58735 58735]
* Need selection of 'current sheet' for printing : [http://distribution.openoffice.org/issues/show_bug.cgi?id=59697 59697]
* Monochrome printing from OOo Calc : [http://distribution.openoffice.org/issues/show_bug.cgi?id=66845 66845]

== Duplicate issues ==
* Various printing default settings (to make things a bit slicker) : [http://distribution.openoffice.org/issues/show_bug.cgi?id=10530 10530]
* Printing does't take the range of cells selected : [http://distribution.openoffice.org/issues/show_bug.cgi?id=43047 43047]

* Backgrounds print irregardless of printer settings : [http://distribution.openoffice.org/issues/show_bug.cgi?id=39244 39244]
* Add possibility to switch on/off printing of cell background color : [http://distribution.openoffice.org/issues/show_bug.cgi?id=53426 53426]

= Formating =
* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=format&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Chart-Unconfirmed&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query All issues contain "format"]
* More border types (dashed, dotted, etc) : [http://qa.openoffice.org/issues/show_bug.cgi?id=8275 8275]

= Formula =
* [http://distribution.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=formula&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Chart-Unconfirmed&newqueryname=&order=Reuse+same+sort+as+last+time All issues contain "formula" sort by votes]

= Shortcut or Keystroke =
* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=keystroke&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&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 Issues contain Keystroke]
* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=Shortcut&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&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 Issues contain Shortcut]

* Provide keyboard shortcuts for Edit->Fill as default : [http://distribution.openoffice.org/issues/show_bug.cgi?id=63727 63727]
* Wish: predefine shortcuts for CALC->MENU:edit->MENU:fill options : [http://distribution.openoffice.org/issues/show_bug.cgi?id=75881 75881]
* Fill Commands behavior not compatible with Excel : [http://distribution.openoffice.org/issues/show_bug.cgi?id=44649 44649]

* Ctrl ; does not add Current Date : [http://distribution.openoffice.org/issues/show_bug.cgi?id=1704 1704]
* Double click on register should show rename dialog : [http://distribution.openoffice.org/issues/show_bug.cgi?id=4517 4517]
* Add short cut [END+Arrow Keys], for easier range selection : [http://distribution.openoffice.org/issues/show_bug.cgi?id=6490 6490]
* Pressing the "delete" button on a selected cell should not necessarily bring up the "Delete Contents" : [http://distribution.openoffice.org/issues/show_bug.cgi?id=9392 9392]
* Moving/Copying -Single- Cell using click-n-drag : [http://distribution.openoffice.org/issues/show_bug.cgi?id=10865 10865]
* Enhanced formula input : [http://distribution.openoffice.org/issues/show_bug.cgi?id=20496 20496]
* Automatic Insert (shift down or shift right) of cells, columns, or rows when cut, or copied, and pasted : [http://distribution.openoffice.org/issues/show_bug.cgi?id=21280 21280]
* Extending row/column selection in calc, easier with shift - : [http://distribution.openoffice.org/issues/show_bug.cgi?id=21869 21869]
* Enter key, as a shortcut, to paste something from the clipboard : [http://distribution.openoffice.org/issues/show_bug.cgi?id=28535 28535]
* Request keyboard shortcut "Alt + =" for AutoSum : [http://distribution.openoffice.org/issues/show_bug.cgi?id=45563 45563]
* Need [ctrl]-["] to copy contents of cell above active cell : [http://distribution.openoffice.org/issues/show_bug.cgi?id=56938 56938]
* Alt-key should display AutoFilter List : [http://distribution.openoffice.org/issues/show_bug.cgi?id=74145 74145]
* Keyboard shortcuts for inserting/deleting rows/cols : [http://distribution.openoffice.org/issues/show_bug.cgi?id=76971 76971]

* Keystroke F5 for repeat the last action (Menu Edit / Repeat)

= Links =
* [[Calc_Usability_Activities]]
* [http://distribution.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&component=Spreadsheet&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Chart-Unconfirmed&newqueryname=&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query List ENHANCEMENT and FEATURE issues for Spreadsheet (Calc)] - [http://distribution.openoffice.org/issues/buglist.cgi?resort=1&issue_type=ENHANCEMENT;issue_type=FEATURE;component=Spreadsheet;issue_status=UNCONFIRMED;issue_status=NEW;issue_status=STARTED;issue_status=REOPENED;issue_status=RESOLVED;email1=;emailtype1=exact;emailassigned_to1=1;email2=;emailtype2=exact;emailreporter2=1;issueidtype=include;issue_id=;changedin=;votes=;chfieldfrom=;chfieldto=Now;chfieldvalue=;short_desc=;short_desc_type=allwords;long_desc=;long_desc_type=allwords;issue_file_loc=;issue_file_loc_type=substring;status_whiteboard=;status_whiteboard_type=substring;keywords=;keywords_type=anytokens;field0-0-0=noop;type0-0-0=noop;value0-0-0=;namedcmd=Chart-Unconfirmed;newqueryname=;Submit%20query=Submit%20query&order=issues.votes%20desc%2C%20issues.issue_id Sort by votes]
* http://fr.openoffice.org/Marketing/matexpo/Documents/Faiblesses_de_Calc.sxw

DomainDeveloper

2007-01-05T09:18:20Z

Pagalmes: /* Developers */

A mapping of names to OOo accounts.

Abbrev.:

* PL : Project Lead
* CL : Project Co-Lead
* CC : Community Council Member
* ESC : Engineering Steering Committee Member
* CVS : has write access to the OOo CVS repository

----

=== Developers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name || CVS || @openoffice.org || [[IRC Communication]] || Notes || Affiliation
|-
| || || || || ||
|-
| Volker Ahrendt|| X || va||||||Sun Microsystems
|-
| Kai Ahrens|| X || ka || Kai_Ahrens ||PL Graphic Applications||Sun Microsystems
|-
| Gene Anaya|| || ganaya||||||
|-
| Joost Andrae|| X || ja||ja||CL qa, release testing en-US builds and releasing builds||Sun Microsystems
|-
| Eric Bachard|| X || ericb||ericb2|| CL porting Mac OSX/Linux PPC port ||French OO.o project
|-
| Kai Backman|| || kaib ||KaiB||||
|-
| Sascha Ballach|| X || sab||||||
|-
| Jayant Balraj Madavi|| || jayant_madavi||aZEN_JM||Connectivity / Database||Novell, Inc.
|-
| Jörg Barfurth|| X || jb||JoergB||Configuration Util||Sun Microsystems
|-
| Mathias Bauer|| X || mba||||PL Framework, XML||Sun Microsystems
|-
| Thorsten Behrens|| X || thb||thorsten||vcl/impress/toolkit visionary||Sun Microsystems
|-
| Thomas Benisch|| X || tbe||||Scripting framework||Sun Microsystems
|-
| Stefan Bergmann|| X || sb||||CL UDK, tools&UCB hacker||Sun Microsystems
|-
| Andreas Bille|| X || abi||||||Sun Microsystems
|-
| Éric Bischoff|| X || ebischoff||ebischoff||KDE A/B driver||Bureau Cornavin
|-
| Nick Blievers|| X || nick||||IRIX||
|-
| Daniel Boelzle|| X || dbo||||UNO core/bridges/packages||Sun Microsystems
|-
| Oliver Bolte|| X || obo||||RE||Sun Microsystems
|-
| Rafaella Braconi|| || coni||||CL l10n, globalization program manager||Sun Microsystems
|-
| Michael Brauer|| X || mib||||PL XML||Sun Microsystems
|-
| Oliver Braun|| X || obr||obr||System Integration/Accessibility Hacker||Sun Microsystems
|-
| Andreas Bregas|| X || ab||||StarBasic||Sun Microsystems
|-
| Jörg Brunsmann|| || jbrunsmann||||UDK||
|-
| Jörg Budischewski|| || jbu||PyUNO hacker||||Sun Microsystems
|-
| Peter Burow|| X || pb||UI||||Sun Microsystems
|-
| Aidan Butler|| || aidan||||XML filters||
|-
| Giuseppe Castagno || X || beppec56 || beppec56_ or beppe_c || PDF output
|-
| [[User:ScottCarr|Scott Carr]] || X || kcarr||kcarr||PL Documentation||Progbits
|-
| Colin Charles|| || drbyte||bytee||Malaysian native-lang project||bytebot.net
|-
| Behrend Cornelius|| X || bc||||Wizards||Sun Microsystems
|-
| Michael Cziebalski|| || mci||||||
|-
| [[User:pdefilippis|Pierre de Filippis]]|| X || pdefilippis||aliscafo||Mac OSX native porting||
|-
| Andrew Dent|| X ||ace_dent||ace_dent||ui/custom_images||
|-
| Naren Devaiah|| || ||ndev||Performance||Intel Corporation
|-
| Nitin Dongre|| || ||nitin_BITS||||Novell, Inc.(intern)
|-
| Radek Doulik|| || radekdoulik||rodo_||Canvas hacker||Novell, Inc.
|-
| Carsten Driesner|| X || cd||||Framework||Sun Microsystems
|-
| Herbert Duerr|| X || hdu||hdu_hh||GSL||Sun Microsystems
|-
| Oliver Düsterhoff|| X || od||Writer||||Sun Microsystems
|-
| Bernd Eilers|| X || bei||rfc821||EIS||Sun Microsystems
|-
| René Engelhard|| X || rene||_rene_||config_office, Debian packager||Debian
|-
| Andre Fischer|| X || af||||Impress||Sun Microsystems
|-
| Uwe Fischer || || ufi || || || Sun Microsystems
|-
| Ken Foskey|| || waratah||waratah||config_office/dmake man||slug.org.au
|-
| Duncan Foster|| || dfoster||||||
|-
| David Fraser|| || davidfraser||davidfraser||South African translations, multilingual builds||translate.org.za
|-
| Nils Fuhrmann|| || nf||||Localization||Sun Microsystems
|-
| Martin Gallwey|| X || mtg||marty_||XML/Writer/packaging||
|-
| Pierre-Andre Galmes || || pagalmes || pagalmes || Chart2 ||StarXpert
|-
| Tony Galmiche|| X || tonygalmiche||||CL FR native-lang project||
|-
| Sunil Gandhi|| || ||tyro||||NOSIP
|-
| Sophie Gautier|| X || sgauti|| sophi ||PL FR native-lang project, CC ||.
|-
| Vladimir Glazounov|| X || vg||||RE||Sun Microsystems
|-
| Laurent Godard || X || laurentgodard || lgodard || CC, PL Extensions, Fr Native-lang Project || inDesko/Nuxeo
|-
| Jody Goldberg|| X || jodygoldberg||jody||[[Calc]] spreadsheet-ness||Novell, Inc.
|-
| Dirk Grobler|| X || dg||||Database Access||Sun Microsystems
|-
| Bettina Haberer|| || bh||||RFEOwner||Sun Microsystems
|-
| Ingrid Halama|| X || iha||||Chart||Sun Microsystems
|-
| Chris Halls|| X || haggai||haggai||Debian packager&misc. hacker||Credativ Ltd., Debian
|-
| Gregor Hartmann|| X || gh|| Lachs ||Testtool||Sun Microsystems
|-
| Bustamam Harun|| || bustamam||||Malaysian stuff||
|-
| Kevin Hendricks|| X || khendricks||||PL Lingucomponent, PowerPC||
|-
| Con Hennessy|| || cphennessy||cph2 or cph_||hacker & former council person||OpenApp
|-
| Ivo Hinkelmann|| X || ihi||ivo||l10n tooling/general/RE||Sun Microsystems
|-
| Eric Hoch|| X || maveric||mav_eric||Mac Porting||
|-
| [[User:Lutz_Hoeger|Lutz Hoeger]]|| || lho||lutzh||[[User Experience]]||Sun Microsystems
|-
| Jan Holešovský|| X || kendy||kendy||KDE integration||Novell, Inc.
|-
| Martin Hollmichel|| X || mh||Ratte/Nesshof||Build Maestro, PL External, Tools, Porting, CC||Sun Microsystems
|-
| Karl Hong|| X || khong||||i18n, CJK expert||Sun Microsystems
|-
| Matthias Huetsch|| X || mhu||||Performance/strategy, PL UCB, CC, ESC||Sun Microsystems
|-
| Michael Hönnig|| X || mi||||PL API||
|-
| [[User:icobgr|Hristo Hristov]] || || icobgr || icobgr || PL Bulgarian native-lang project ||
|-
| Sven Jacobi|| X || sj||||Escherwizard||Sun Microsystems
|-
| Jörg Jahnke|| || jj||||Internal tooling||Sun Microsystems
|-
| Christian Jansen|| || cj ||||Menu and Toolbar?||Sun Microsystems
|-
| Ocke Janssen|| X || oj||Base||||Sun Microsystems
|-
| Pavel Janík|| X || pjanik||paveljanik||PL Czech native-lang project, CL l10n, CC, ESC, l10n builds||
|-
| Berry Jia|| X || berryjia||||||Sun Microsystems
|-
| Pascal Junck|| || pjunck||||||Sun Microsystems
|-
| Peter Junge|| X || pj|| peter13j|| OOo community contact for my Chinese Employer, QA||Beijing Redflag CH2000
|-
| Christian Junker|| || Cyb||christianju||API||Trees For Life
|-
| Hirano Kazunari|| || khirano||||Japanese||
|-
| Dhananjay Keskar|| X || dkeskar ||dkeskar||Performance,Buildbot,cat-herder||Intel Corporation
|-
| Robert Kinsella|| || rkinsella||||||Sun Microsystems
|-
| Volodymyr Khrystynych|| || volody||||XML Filter||
|-
| Matthias Klose|| || doko||doko||Ubuntu, gcc, python packager||Canonical, Inc.
|-
| Laszlo Kovacs|| || lkovacs||||Documentation||
|-
| Martin Kretzschmar|| X || mkretzschmar||martink||Gnome / Debian||Student
|-
| Will Lachance|| || wlach||wlach_||Word Perfect File Filters||Net Integration Technologies, Inc.
|-
| Thomas Lange|| X || tl||||||Sun Microsystems
|-
| Lars Langhans|| X || lla||||||Sun Microsystems
|-
| Hans-Joachim Lankenau|| X || hjs||ause||dmake makefile expert, RE||Sun Microsystems
|-
| Németh László|| X || nemeth||||PL lingucomponent||
|-
| Jakob Lechner|| X || jakob_lechner||||Writer||Fabalabs
|-
| Michael Leibowitz|| X || mikeleib ||mikeleib||performance||Intel Corporation
|-
| Wind Li|| X || windly||||Address books||
|-
| Ping Liao|| || pliao||||||
|-
| Tor Lillqvist|| X || tml||tml_||||Novell, Inc.
|-
| Joachim Lingner|| X || jl||||Java, CLI||Sun Microsystems
|-
| Christian Lippka|| X || cl||ChristianL||Graphic Applications||Sun Microsystems
|-
| Mindy Liu|| || mindyliu||||||
|-
| Dieter Loeschky|| X || ||||Localization||Sun Microsystems
|-
| Philipp Lohmann|| X || pl||pl_hh||VCL/X11 (GSL) hacker||Sun Microsystems
|-
| Jackson Low|| X || xxjack12xx||||Porting||
|-
| Patrick Luby|| || pluby||||Mac||
|-
| Prasad Madhav || X || pmadhav || pmadhav || Buildbot || Intern@Intel
|-
| Babak Mahbod|| || bmahbod||||||
|-
| Martin Maher|| || mmaher||||Writer & Filter chap||
|-
| Nakata Maho|| X || maho||_maho_||PL QA, FreeBSD guy||Independent
|-
| John Marmion|| X || jmarmion||||||
|-
| Andreas Martens|| X || ama||||PL Writer||Sun Microsystems
|-
| [[User:smsm1|Shaun McDonald]] || X || smsm1 || shaunmcdonald || Mac Port, buildbot MacPort1 || Student
|-
| Caolán McNamara|| X || cmc||caolan||CL Writer & Filter man||RedHat, Inc.
|-
| Michael Meeks|| X || mmeeks||michael_||ugly hack-er, ESC||Novell, Inc.
|-
| Frank Meies|| X || fme||||Writer||Sun Microsystems
|-
| Federico Mena-Quintero|| || federicomena||federico||perfectionist||Novell, Inc.
|-
| Michael Mi|| || mmi||||||
|-
| Björn Milcke|| X || bm||bm_||Chart||Sun Microsystems
|-
| Petr Mladek|| || pmladek||pmladek||SUSE RPMs, ooo-build releases||Novell, Inc.
|-
| Cyrille Moureaux|| X || cyrillem||Cyrille||||Sun Microsystems
|-
| [[User:Mmp|Matthias Müller-Prove]]|| || mmp|| mprove|| [[User Experience]] Engineer, http://ui.openoffice.org || Sun Microsystems
|-
| Niklas Nebel|| X || nn||||PL [[Calc]]||Sun Microsystems
|-
| Christoph Neumann|| X || cn||||API tests||Sun Microsystems
|-
| NicelKM|| X || mnicel||nicel||||Novell, Inc.
|-
| Bertram Nolte|| || bnolte||||||
|-
| Tomas O'Connor|| || toconnor||||Scripting Framework||
|-
| Lars Oppermann|| X || lo||||||Sun Microsystems
|-
| Rodrigo Parra Novo|| X || rodarvus||rodarvus||Gnumeric/Abiword OpenDocument Format support and port to Maemo||INdT (Instituto Nokia de Tecnologia)
|-
| Edward Peterlin|| X || OPENSTEP||||Mac||
|-
| Frank Peters|| X || fpe||||Documentation||Sun Microsystems
|-
| Christof Pintaske|| X || cp||||||Sun Microsystems
|-
| Ron Piterman|| || rpiterman||||||
|-
| Noel Power|| || npower||noelp||VBA Interop, Scripting||Novell, Inc.
|-
| Nikolai Pretzell|| X || np || ||Autodoc, code quality||Sun Microsystems
|-
| Volker Quetschke|| X || vq||vq||W32-tcsh/bash build environment and dmake Hacker, ESC||Gravity Waves
|-
| Tino Rachui|| X || tra||tinor||GSL/Unix Hacker||Sun Microsystems
|-
| [[User:Kr|Kay Ramme]]|| X || kr||||PL UDK||Sun Microsystems
|-
| [[User:ErAck|Eike Rathke]]|| X || er||erAck||CL [[Calc]], engine; CL i18n; stricken with number formatter||Sun Microsystems
|-
| Michael Rauch|| X || mrauch||||NetBSD||
|-
| Jens-Heiner Rechtien|| X || hr||blauwal||RE; OOo SCM (CVS, CWS tooling); Porting; Compilers||Sun Microsystems
|-
| Daniel Rentz|| X || dr||||[[Calc]] Excel filter, UI||Sun Microsystems
|-
| Florian Reuter|| X || flr||||Writer filters||Novell, Inc.
|-
| Georg Richter|| X || grichter||georg||Base, native MySQL driver||MySQL AB
|-
| G. Roderick Singleton|| || grsingleton||grsingleton||Documentation||pathtech.org
|-
| Hennes Rohling|| X || hro||||GSL & Util||Sun Microsystems
|-
| Bibek Sahu|| || Bibek||bibek||Impress pieces||Trees For Life
|-
| Andreas Schlüns|| X || as||||Framework||Sun Microsystems
|-
| Ingo Schmidt|| X || is||||(Native) Installation||Sun Microsystems
|-
| [[User:Jsc|Jürgen Schmidt]]|| X || jsc||jsc||PL API, CL Extensions, UNO, SDK||Sun Microsystems
|-
| Stephan Schäfer|| X || ssa||ssa||VCL||Sun Microsystems
|-
| Frank Schönheit|| X || fs||FrankS||Database Access, Forms||Sun Microsystems
|-
| Julian Seward || || sewardj || || valgrind ||
|-
| Darragh Sherwin|| || dsherwin||darragh||E-Legislation / E-GovSystems||Propylon
|-
| Raul Siddhartha|| || rsiddhartha||raul||GTK File Selector||Novell, Inc.
|-
| Sarah Smith|| || ssmith||||||
|-
| [[User:mox|Mox Soini]] || X || mox || Moxed || Mac Porting ||
|-
| Rajesh Sola|| || rajeshsola||sola||misc.||NOSIP
|-
| Kai Sommerfeld|| X || kso||||manager & hacker||Sun Microsystems
|-
| Oliver Specht|| X || os||||PL UI||Sun Microsystems
|-
| Jörg Spindler|| || jspindler||||||
|-
| Fridrich Štrba|| X || fridrich_strba||Fridrich||Word Perfect Hacker||
|-
| Ulf Stroehler|| || us||||||Sun Microsystems
|-
| Muthu Subramanian|| || muthusuba||muthusuba||misc.||
|-
| Louis Suárez-Potts|| || louis||louis||Community Manager||Collab.net
|-
| Claus Sørensen|| || cs||c26n,cHBs,chbs||Danish Localization and Project Management Tool(oopm)||ProFOSS
|-
| Stefan Taxhet|| X || st||stx12||CC, interpersonal problem fixer||Sun Microsystems
|-
| Armin Theissen|| || armin||||||
|-
| Caio Tiago Oliveira|| X || asrail||asrail||CL QA, release testing pt-BR builds||Independent
|-
| Jan Tietjens|| || tietjens||||||
|-
| Rüdiger Timm|| X || rt|| rtimm ||RE||Sun Microsystems
|-
| Malte Timmermann|| X || mt||||||Sun Microsystems
|-
| Gerhard Tonn|| || tonn||||s390||
|-
| Willem van Dorp|| || willem.vandorp||||||
|-
| Tom Verbeek|| X || tv||||Wizards, Art team||Sun Microsystems
|-
| Sander Vesik|| || svesik||||||
|-
| Daniel Vogelheim|| X || dvo||||XML||
|-
| Mikhail Voitenko|| X || mav||Framework||||Sun Microsystems
|-
| Robert Vojta|| X || rvojta||rvojta||VBA Interop||
|-
| Dirk Völzke|| X || dv||||Installation||Sun Microsystems
|-
| [[User:Sparcmoz|Jim Watson]]|| X || sparcmoz|| sparcmoz||GNU Linux sparc porter||clug.org.au
|-
| Armin Weiss|| X || aw||||||Sun Microsystems
|-
| Dan Williams|| X || fa||dcbw||Mac et. al. hacker||RedHat, Inc.
|-
| Stephan Wunderlich|| X || sw||||||
|-
| Kohei Yoshida|| X || kohei||kohei_||[[Calc]] hacker, Calc optimization solver developer||SlickEdit, Inc.
|-
| George Zahopoulos|| X || georgez||||||
|-
| Kurt Zenker|| X || kz||smoketester||RE||Sun Microsystems
|-
| Claudio F Filho|| || filhocf||filhocf||Brazilian portuguese Localization||BrOffice.org
|-
| Xiaoyang Yu|| || || ||Disk block reordering||Intel Corporation
|-
| Antonio Xu|| X || antoxu || antoxu || Async dialogs, PRC improvements || Intel Corporation
|-
| Rail Aliev || X || rail || rail || Ru and Tr NL Co-lead || Infra-Resource
|-
| Jeremy Zheng|| X || zhiming || Jeremy || Async dialogs, PRC improvements || Intel Corporation
|-
| [[User:Schmidtm|Matthias Schmidt]] || || schmidtm || schmidtm || Mac OSX Aqua Port || Sun Microsystems
|-
| Yuri Dario || || ydario || Paperino || OS/2 Port || Serenity Systems intl
|-
| Wei Zhao || || weiz || || Chinese Localization || Beijing Redflag CH2000
|-
| Liu Tao || || liutao || || PyUNO, Async dialogs|| Beijing Redflag CH2000
|-
| JiangChuang || || jiangc || || || Beijing Redflag CH2000
|-
| Lv Xugang || || lvxg || || || Beijing Redflag CH2000
|-
| Chen Jinhong || || chainchen || || || Beijing Redflag CH2000
|-
| Li Yuan || || liyuan || || PyUNO, Async dialogs || Beijing Redflag CH2000
|-
| Wu Yan || || youngwoo || || || Beijing Redflag CH2000
|-

|}

=== QA Engineers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name ||CVS||@openoffice.org || [[IRC Communication]] || Interested modules || Notes || Affiliation
|-
| Stefan Baltzer||||sba||||writer||||Sun Microsystems
|-
| Thorsten Bosbach||X||tbo||||framework, qa/qatesttool||QA Framework / Automation||Sun Microsystems
|-
| Oliver Craemer||X||oc||||[[Calc]]||QA Calc / Automation||Sun Microsystems
|-
| Helge Delfs||X||hde||||writer, qa/qatesttool||QA Writer / Automation||Sun Microsystems
|-
| Fredrik Haegg||X||fha||||draw, impress, qa/qatesttool||QA Graphics / Automation||Sun Microsystems
|-
| Hasan Ilter||||hi||||writer, printing, pdf export||||Sun Microsystems
|-
| Michael Rüß||||mru||||writer, word im/export||||Sun Microsystems
|-
| Éric Savary||||es||||writer, accessibility||||Sun Microsystems
|-
| [[User:jsi|Joerg Sievers]]||X||jsi||jogi||qa/qatesttool, [[Calc]]||Automation / QA Calc||Sun Microsystems
|-
| Joerg Skottke||X||jsk||skotti||framework, qa/qatesttool||QA Framework / Automation||Sun Microsystems
|-
| Marc Neumann||X||msc||||database, qa/qatesttool||QA Base / Automation||Sun Microsystems
|-
| Chris Lukasiak||||clu||||database||||Sun Microsystems
|-
| Frank Stecher||||fst||||[[Calc]]||||Sun Microsystems
|-
| Jack Warchold|||| jw||||writer, import/export filters||||Sun Microsystems
|-
| Uwe Luebbers||||ul||||framework||||Sun Microsystems
|-
| Thorsten Martens||||tm||||framework||||Sun Microsystems
|-
| Olaf Felka|||| of||||framework, installation||||Sun Microsystems
|-
| Thomas Klarhoefer||||kla||||chart||||Sun Microsystems
|-
| Wolfram Garten|||| wg||||draw, impress||||Sun Microsystems
|-
| Christian Guenther||||cgu||||draw, impress||||Sun Microsystems
|-
| [[User:Thorsten_Ziehm|Thorsten Ziehm]]||||| thorstenziehm||||||QA lead||Sun Microsystems
|-
|}

We are tracking pending JCAs in the document [[Pending JCAs]].

== Related Pages ==
* [[User Experience Community]]
* A map of OOo developers around the world is available at http://www.frappr.com/ooodev, please add yourself to the map if you're involved in OOo development. It's just fun to see who's where :-)

[[Category:Development]]

BetterDatabaseDrivers

2006-10-25T13:21:49Z

Pagalmes: /* Idea 4: have a "drivers inheritance tree" */

Better and simpler infrastructure for database drivers

This is for the moment just a brainstorming page. This is too unformal at the time being to be converted to a real "issue" in issuezilla or a specification.

== Idea 1: have a "drivers loader" ==

Summary: currently, most database drivers are divided in two libraries:
- a small part that verifies that the conditions are met to load a given driver
- a big part that will in turn dl'open the needed libraries and do the real job
The idea would be to merge all the small "loader" parts

Pros: efficiency, reduce number of libraries

Cons: against modularity

== Idea 2: have "evaluation trees" in addition to current SQL syntactic tree ==

Summary: currently, the drivers that have to analyse the SQL syntax use the SQL parser, which does all the dirty work of checking grammar and tokenizing, but they are on their own when it comes to running the request. Perharps the runtime in-memory trees for selections and sorting of the kab driver could be reused.

Pros: simplify code for drivers like the evolution driver

Cons: uncertain feasability, because the way that you run a request might depend to some extent upon the underlying database.

== Idea 3: have a "generic driver" ==

Summary: currently, there's a lot of drivers which duplicate a lot of code. It could be done in several steps, starting with a basic infrastructure for the simplest drivers which mainly differ in the code to access the concrete table data, and ending with drivers that are different in many aspects.

Imagine, for instancem a driver which is completely implemented except the table data access. Now some component could instantiate this driver, and pass it an XTableProvider and an XTableDataProvider (or so) interface, which allow to enumerate existing tables, and retrieving their data. This would, in a first step, allow get rid of today's drivers for Calc, flat text files, and the KDE address book. Additionally, it would tremendously ease the writing of new drivers which just need readonly access to flat tables.

In a next step, this driver could be extended with update capabilities. So, it would allow to be parametrized with some kind of XTableDataUpdate interface. This step would allow to get rid of the dBase driver, too.

Step 3 is to implement support for some XSort/XFilter (or so), which passes the responsibility for filtering/sorting the table data to the concrete backend, instead of doing this client-side in the generic driver. Step 3 would allow us to get rid of the Evolution Address Book and the Mozilla/Thunderbird/LDAP drivers.

Further steps would be more difficult, since from there on, drivers differ in much more aspects. We would need to abstract from those aspects, and hide the differences behind some generic interfaces. It might well turn out that this is not worth it anymore, since the abstraction API might become as complex as the SDBC(X) API already is, so there would be no point in creating it.

Pros : remove code redundancy
Cons : major rewrite

== Idea 4: have a "drivers inheritance tree" ==

Summary: basically the same as idea 2, but with drivers inheriting one from the other, rathing than inventing new shared UNO interfaces. The inheritance tree could look as follows:

database driver
!
+--- SQL driver ---+--- MySQL
! +--- PostGreSQL
! +--- HSQLDB
! +--- Adabas
! +--- ODBC
! +--- JDBC
! +--- ado
!
+--- API driver ---+--- File driver ---+--- Flat
! +--- Calc
! +--- dBase
! +--- XML FIles
!
+--- Mozilla
+--- Thunderbird
+--- Evolution
+--- KDE

Pros: ease of writing new drivers
Cons: Major rewrite too

Actually, this is kind of complementary to the previous idea. That is, implementing the one would probably remove the need for other.

Also, there are people saying you should favour composition over inheritance, and I lately tend to agree to them :). That is, instead of building a complex inheritance hierarchy, it might be more elegant and future-proof to create a number of components which can be plugged together.

Building OpenOffice.org

2006-08-11T12:51:37Z

Pagalmes: /* Building a CWS */

[[Category:Development]]
These are the instructions on how to build "vanilla" OpenOffice.org. Vanilla means: without tools like ooobuild that wrap the build-process. If you're using ooobuild, have a look at [[Building_with_ooobuild]] instead.

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]].

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

While not dependencies, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds.

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxIntelEnv.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxIntelEnv.Set
rehash
</pre>

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.

= Building a [[CWS]] =
In order to build a cws, you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build
== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variabnle, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set maxprocess=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources<br/>(use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>unxlngi#.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, just copy the zips you created to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving diskscpace by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

Building OpenOffice.org

2006-08-11T12:50:53Z

Pagalmes: /* Building a CWS */

[[Category:Development]]
These are the instructions on how to build "vanilla" OpenOffice.org. Vanilla means: without tools like ooobuild that wrap the build-process. If you're using ooobuild, have a look at [[Building_with_ooobuild]] instead.

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]].

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

While not dependencies, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds.

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxIntelEnv.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxIntelEnv.Set
rehash
</pre>

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.

= Building a [[CWS]] =
In order to build a cws, you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build
== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variabnle, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set maxprocess=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources<br/>(use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>unxlngi#.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, just copy the zips you created to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving diskscpace by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

Chart2

2006-08-04T11:19:43Z

Pagalmes: /* print, assert and debug helpers */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m172 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m172 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m172 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cws called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m172/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

===== Smoke tests =====

Once everything compiled, you should launch the "smoke tests". Those are
tests to verify that the basic functions of OpenOffice.org work. To
launch the smoke tests, issue the following command lines :

<pre>
cd smoketestoo_native/
setenv TEMP "/home/pagalmes/workspace/chart2_m172_exec"
dmake noremove
</pre>

Note : sometimes those tests will fail but you can just ignore them.

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file chart2/source/tools/InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

=== Coding ===

the essentials

==== print, assert and debug helpers ====

When you start developping, you will certainly need to trace your program.
For this, debuggers are really useful, but what is often used is to inserted
functions like printf() that will send messages. How do those things work in
OpenOffice.org ? Well there are quite a few ways to echo strings.

===== the standard functions =====

The first one is to use the classical "printf" and "fprintf" functions :

<code>[cpp,N]

#include <stdio.h>

int foo()
{
printf( "Foo\n" );
fprintf( stderr, "foo\n" );
}
</code>

For the ones loving C++, the second way is to use the iostreams :

<code>[cpp,N]

#include <iostream>

int foo()
{
std::cerr << "coucou" << std::endl;
std::cout << "coucou" << std::endl;
}
</code>

As two ways of doing things is not enought, you will find a few macros.
There are two kinds of such macros, the OSL macros and the DGB macros.

===== The OSL functions =====

The OSL_ things are intended to be used permanently, not for debugging
only. I.e., when you would cassert() you should OSL_ASSERT() (or ENSURE).

* OSL_TRACE( "text" )
* OSL_ENSURE( condition, "text" )
* OSL_ASSERT( condition )

"For printf debugging you can also use OSL_TRACE( "Bla" ); On Linux, this
prints to stdout (or stderr), so you should see it on the console, as
long as the file was compiled with debug=t.

OSL_ASSERT( condition ) and OSL_ENSURE( condition, "text" ) also print to
stderr on Linux, but they pop up a window on Windows )"

Here are some examples and how to use those three functions :

====== OSL_TRACE example ======

<code>[cpp,N]
#ifndef _OSL_DIAGNOSE_H_
#include <osl/diagnose.h>
#endif

[...]

int foo()
{
OSL_TRACE( "My first trace" );
}
</code>

And the result should look like :

<code>
$ ./myfoo
Thread: 1 :My first trace
</code>

====== OSL_ENSURE example ======

<code>[cpp,N]

#ifndef _OSL_DIAGNOSE_H_
#include <osl/diagnose.h>
#endif

[...]

int foo()
{
// Will not be displayed.
OSL_ENSURE( true, "here I truly gooooo!!" );

// Will be displayed.
OSL_ENSURE( false, "here I gooooo!!" );

//
#if OSL_DEBUG_LEVEL > 2
OSL_ENSURE( true, "here I gooooo if level is set to 3!" );
#endif

}
</code>

And the result should look like :

<code>
$ ./myfoo
Error: File /home/pagalmes/workspace/chart2_m172/src680-m172/chart2/source/controller/main/ChartController.cxx, Line 1201: here I gooooo!!
Backtrace: [0] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x4ac0e
Backtrace: [1] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x4b73b
Backtrace: [2] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x573b5
Backtrace: [3] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x43964
[...]
</code>

====== OSL_ASSERT example ======

<code>[cpp,N]
#ifndef _OSL_DIAGNOSE_H_
#include <osl/diagnose.h>
#endif

[...]

int foo()
{

bool test;
test = true;

OSL_TRACE( "test is true." );
OSL_ASSERT( test );

test = false;

OSL_TRACE( "test is false." );
OSL_ASSERT( test );

}
</code>

And the result should look like :

<code>
Thread: 1 :test is true.
Thread: 1 :test is false.
Error: File /home/pagalmes/workspace/chart2_m172/src680-m172/chart2/source/controller/main/ChartController.cxx, Line 1202
Backtrace: [0] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x452db
Backtrace: [1] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x47361
Backtrace: [2] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x56899
[...]
</code>

===== the DBG functions =====

* DBG_ASSERT()
* DBG_ERROR()

DBG_ASSERT() and DBG_ERROR() need the tools library (the tools project not
the lib in chart2). Therefore I try to avoid it if a library is not linked
against tools anyway.

I think (not sure) that the model lib is not linked against tools.

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]
[[Category:Source_directories]]

Chart2

2006-08-04T11:14:32Z

Pagalmes: /* printf, assert and debug helpers */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m172 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m172 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m172 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cws called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m172/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

===== Smoke tests =====

Once everything compiled, you should launch the "smoke tests". Those are
tests to verify that the basic functions of OpenOffice.org work. To
launch the smoke tests, issue the following command lines :

<pre>
cd smoketestoo_native/
setenv TEMP "/home/pagalmes/workspace/chart2_m172_exec"
dmake noremove
</pre>

Note : sometimes those tests will fail but you can just ignore them.

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file chart2/source/tools/InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

=== Coding ===

the essentials

==== print, assert and debug helpers ====

When you start developping, you will certainly need to trace your program.
For this, debuggers are really useful, but what is often used is to inserted
functions like printf() that will send messages. How do those things work in
OpenOffice.org ? Well there are quite a few ways to echo strings.

===== the standard functions =====

The first one is to use the classical "printf" and "fprintf" functions :

<code>[cpp,N]

#include <stdio.h>

int foo()
{
printf( "Foo\n" );
fprintf( stderr, "foo\n" );
}
</code>

For the ones loving C++, the second way is to use the iostreams :

<code>[cpp,N]

#include <iostream>

int foo()
{
std::cerr << "coucou" << std::endl;
std::cout << "coucou" << std::endl;
}
</code>

As two ways of doing things is not enought, you will find a few macros.
There are two kinds of such macros, the OSL macros and the DGB macros.

===== The OSL functions =====

The OSL_ things are intended to be used permanently, not for debugging
only. I.e., when you would cassert() you should OSL_ASSERT() (or ENSURE).

* OSL_TRACE( "text" )
* OSL_ENSURE( condition, "text" )
* OSL_ASSERT( condition )

Here are some examples and how to use those three functions :

====== OSL_TRACE example ======

<code>[cpp,N]
#ifndef _OSL_DIAGNOSE_H_
#include <osl/diagnose.h>
#endif

[...]

int foo()
{
OSL_TRACE( "My first trace" );
}
</code>

And the result should look like :

<code>
$ ./myfoo
Thread: 1 :My first trace
</code>

====== OSL_ENSURE example ======

<code>[cpp,N]

#ifndef _OSL_DIAGNOSE_H_
#include <osl/diagnose.h>
#endif

[...]

int foo()
{
// Will not be displayed.
OSL_ENSURE( true, "here I truly gooooo!!" );

// Will be displayed.
OSL_ENSURE( false, "here I gooooo!!" );

//
#if OSL_DEBUG_LEVEL > 2
OSL_ENSURE( true, "here I gooooo if level is set to 3!" );
#endif

}
</code>

And the result should look like :

<code>
$ ./myfoo
Error: File /home/pagalmes/workspace/chart2_m172/src680-m172/chart2/source/controller/main/ChartController.cxx, Line 1201: here I gooooo!!
Backtrace: [0] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x4ac0e
Backtrace: [1] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x4b73b
Backtrace: [2] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x573b5
Backtrace: [3] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x43964
[...]
</code>

====== OSL_ASSERT example ======

<code>[cpp,N]
#ifndef _OSL_DIAGNOSE_H_
#include <osl/diagnose.h>
#endif

[...]

int foo()
{

bool test;
test = true;

OSL_TRACE( "test is true." );
OSL_ASSERT( test );

test = false;

OSL_TRACE( "test is false." );
OSL_ASSERT( test );

}
</code>

And the result should look like :

<code>
Thread: 1 :test is true.
Thread: 1 :test is false.
Error: File /home/pagalmes/workspace/chart2_m172/src680-m172/chart2/source/controller/main/ChartController.cxx, Line 1202
Backtrace: [0] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x452db
Backtrace: [1] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x47361
Backtrace: [2] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x56899
[...]
</code>

For printf debugging you can also use OSL_TRACE( "Bla" ); On Linux, this prints to stdout (or stderr), so you should see it on the console, as long as the file was compiled with debug=t

OSL_ASSERT( condition ) and OSL_ENSURE( condition, "text" ) also print to stderr on Linux, but they pop up a window on Windows )

BTW, DBG_ASSERT() and DBG_ERROR() need the tools library (the tools project not the lib in chart2). Therefore I try to avoid it if a library is not linked against tools anyway. I think (not sure) that the model lib is not linked against tools.

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]
[[Category:Source_directories]]

Chart2

2006-08-04T10:38:08Z

Pagalmes: /* printf, assert and debug helpers */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m172 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m172 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m172 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cws called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m172/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

===== Smoke tests =====

Once everything compiled, you should launch the "smoke tests". Those are
tests to verify that the basic functions of OpenOffice.org work. To
launch the smoke tests, issue the following command lines :

<pre>
cd smoketestoo_native/
setenv TEMP "/home/pagalmes/workspace/chart2_m172_exec"
dmake noremove
</pre>

Note : sometimes those tests will fail but you can just ignore them.

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file chart2/source/tools/InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

=== Coding ===

the essentials

==== printf, assert and debug helpers ====

When you start developping, you will certainly need to trace your program.
For this, debuggers are really useful, but what is often used is to inserted
functions like printf() that will send messages. How do those things work in
OpenOffice.org ? Well there are quite a few ways to echo strings.

The first one is to use the classical "printf" and "fprintf" functions :

<code>[cpp,N]

#include <stdio.h>

int foo()
{
printf( "Foo\n" );
fprintf( stderr, "foo\n" );
}
</code>

For the ones loving C++, the second way is to use the iostreams :

<code>[cpp,N]

#include <iostream>

int foo()
{
std::cerr << "coucou" << std::endl;
std::cout << "coucou" << std::endl;
}
</code>

As two ways of doing things is not enought, you will find a few macros.
There are two kinds of such macros, the OSL macros and the DGB macros.

The OSL_ things are intended to be used permanently, not for debugging
only. I.e., when you would cassert() you should OSL_ASSERT() (or ENSURE).

* OSL_TRACE( "text" )
* OSL_ENSURE( condition, "text" )
* OSL_ASSERT( condition )

<code>[cpp,N]

#ifndef _OSL_DIAGNOSE_H_
#include <osl/diagnose.h>
#endif

[...]

int foo()
{
// Will not be displayed.
OSL_ENSURE( true, "here I truly gooooo!!" );

// Will be displayed.
OSL_ENSURE( false, "here I gooooo!!" );

//
#if OSL_DEBUG_LEVEL > 2
OSL_ENSURE( true, "here I gooooo if level is set to 3!" );
#endif

}
</code>

And the result should look like :

<code>
Error: File /home/pagalmes/workspace/chart2_m172/src680-m172/chart2/source/controller/main/ChartController.cxx, Line 1201: here I gooooo!!
Backtrace: [0] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x4ac0e
Backtrace: [1] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x4b73b
Backtrace: [2] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x573b5
Backtrace: [3] /home/pagalmes/workspace/chart2_m172_exec/OpenOffice/opt/openoffice.org2.0/program/libchartcontroller680li.so: ???+0x43964
</code>

For printf debugging you can also use OSL_TRACE( "Bla" ); On Linux, this prints to stdout (or stderr), so you should see it on the console, as long as the file was compiled with debug=t

OSL_ASSERT( condition ) and OSL_ENSURE( condition, "text" ) also print to stderr on Linux, but they pop up a window on Windows )

BTW, DBG_ASSERT() and DBG_ERROR() need the tools library (the tools project not the lib in chart2). Therefore I try to avoid it if a library is not linked against tools anyway. I think (not sure) that the model lib is not linked against tools.

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]
[[Category:Source_directories]]

Chart2

2006-08-04T10:10:09Z

Pagalmes: /* Developping for the new chart module */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m172 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m172 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m172 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cws called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m172/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

===== Smoke tests =====

Once everything compiled, you should launch the "smoke tests". Those are
tests to verify that the basic functions of OpenOffice.org work. To
launch the smoke tests, issue the following command lines :

<pre>
cd smoketestoo_native/
setenv TEMP "/home/pagalmes/workspace/chart2_m172_exec"
dmake noremove
</pre>

Note : sometimes those tests will fail but you can just ignore them.

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file chart2/source/tools/InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

=== Coding ===

the essentials

==== printf, assert and debug helpers ====

When you start developping, you will certainly need to trace your program.
For this, debuggers are really useful, but what is often used is to inserted
functions like printf() that will send messages. How do those things work in
OpenOffice.org ? Well there are quite a few ways to echo strings.

The first one is to use the classical "printf" and "fprintf" functions :

<code>[cpp,N]

#include <stdio.h>

int foo()
{
printf( "Foo\n" );
fprintf( stderr, "foo\n" );
}
</code>

For the ones loving C++, the second way is to use the iostreams :

<code>[cpp,N]

#include <iostream>

int foo()
{
std::cerr << "coucou" << std::endl;
std::cout << "coucou" << std::endl;
}
</code>

As two ways of doing things is not enought, you will find a few macros.
There are two kinds of such macros, the OSL macros and the DGB macros.

The OSL_ things are intended to be used permanently, not for debugging
only. I.e., when you would cassert() you should OSL_ASSERT() (or ENSURE).

* OSL_TRACE( "text" )
* OSL_ENSURE( condition, "text" )
* OSL_ASSERT( condition )

For printf debugging you can also use OSL_TRACE( "Bla" ); On Linux, this prints to stdout (or stderr), so you should see it on the console, as long as the file was compiled with debug=t

OSL_ASSERT( condition ) and OSL_ENSURE( condition, "text" ) also print to stderr on Linux, but they pop up a window on Windows )

BTW, DBG_ASSERT() and DBG_ERROR() need the tools library (the tools project not the lib in chart2). Therefore I try to avoid it if a library is not linked against tools anyway. I think (not sure) that the model lib is not linked against tools.

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]
[[Category:Source_directories]]

Chart2

2006-08-02T13:43:57Z

Pagalmes: /* Compiling the new chart module */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m172 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m172 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m172 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cws called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m172/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

===== Smoke tests =====

Once everything compiled, you should launch the "smoke tests". Those are
tests to verify that the basic functions of OpenOffice.org work. To
launch the smoke tests, issue the following command lines :

<pre>
cd smoketestoo_native/
setenv TEMP "/home/pagalmes/workspace/chart2_m172_exec"
dmake noremove
</pre>

Note : sometimes those tests will fail but you can just ignore them.

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file chart2/source/tools/InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]
[[Category:Source_directories]]

SUSE9.3 Build Instructions

2006-06-20T12:25:05Z

Pagalmes:

=== About SUSE 9.3 ===

SUSE 9.3 project is the ancestor of OpenSuse, a worldwide community program sponsored by Novell that promotes the use of Linux everywhere. The program provides anyone with free and easy access to SUSE Linux.

=== Build Instructions ===

The [[Building|build procedure]] is the same as for other Linux systems.

=== Issues during the build (this is true with m172) ===

==== uudecode ====

This is related to

*Installed the Java package from Suse 9.3
*Installed the JDK in another location
*You try to build using the JDK just downloaded

==== connectivity ====

When trying to build the connectivity project, the following error my be displayed :

<pre>
TODO : Here add the error !! (~ "needs libstdc++.so.6)
</pre>

This happens if you try to build OOo using the pre-build mozilla packages
(LINUXGCCIinc.zip, LINUXGCCIlib.zip and LINUXGCCIruntime.zip) and to compile OOo using gcc < 3.4.

Here is the situation :

* By default, Suse 9.3 uses gcc 3.3.5 and libstdc++.so.5
* The prebuild mozilla packages were build using gcc 3.4 and libstdc++.so.6

So, you can not use those pre-build packages and need to compile your own mozilla packages as it is
described on the [http://tools.openoffice.org/dev_docs/build_linux.html tools project page].

[[Category: Distribution-Specific Build Instructions]]

Building with ooobuild

2006-06-20T11:51:43Z

Pagalmes:

== Vanilla Up-stream builds ==

See the [http://tools.openoffice.org#Build tools] project for build guides for various platforms.

Also for OS/X see [[MacOSXBuildInstructions]]

For GNU/Linux Sparc, with gcc4.1 & gcj, see [[GNULinuxSparcPorting]]

== ooo-build builds ==

<center>
'''If you are looking for additional building tips for Windows check [[Windows |this]] page first.'''
</center>
----
<br>

=== configure ===

<p>
The build process is pretty complicated; you have a choice
of commands now; although running both won't actually hurt:
</p>
./autogen.sh # only for the CVS version
./configure # the packaged version

<p>
This will guess which branch snapshot you want to build; if
you have other ideas use the --with-tag option; eg.
<code>--with-tag=src680-m65</code> for a legacy branch.
</p>
<p>
If for some reason you have a 31337 multi-threaded computer,
with great slabs of RAM; you'll want to use --with-num-cpus=8
etc. NB. it's not clever to force the build to swap like a
demented pawnbroker by using an artificially high number; C++
compilation is seriously memory hungry.
</p>
<p>
In particular, building SRC680 requires a recent jdk & a
version of apache-ant. If you use a Novell system, just do:
<code>sudo rug in apache-ant</code>, alternatively download
a package from [http://www.rpmfind.net/linux/rpm2html/search.php?query=apache-ant&submit=Search+..." rpmfind.net] or failing that see [http://ant.apache.org/bindownload.cgi Ant download]
& set the ANT environment variable
appropriately before configuring.
</p>
<h4>Known ./configure parameters</h4>
<ul>
<li><h5><code>--with-system-<package name></code></h5>
<p>where <package name> is replaced by the package to use. I don't
have a particularly good understanding of its full effects beyond
the fact that it (probably) doesn't then build its own copy of the
package.</p>
<p><b>Examples:</b><br>
<code>--with-system-python</code><br>
<code>--with-system-mozilla</code><br>
<code>--with-system-gcc</code><br>
<code>--with-system-neon</code><br>
<code>--with-system-curl</code><br>
</p>
</li>
<li><h5><code>--without-system-<package name></code></h5>
<p><b>Examples:</b><br>
<code>--without-system-mozilla</code>
</p>
</li>
<li><h5><code>--with-<package or tag>[=value]</code></h5>
<p><b>Examples:</b><br>
<code>--with-lang=en-US</code><br>
<code>--with-build-version="Build 2.0.1.3"</code><br>
<code>--with-distro=Gentoo</code><br>
</p>
</li>
<li><h5><code>--without-<package or tag></code></h5>
<p><b>Examples:</b><br>
<code>--without-myspell-dicts</code><br>
<code>--without-java</code><br>
<code>--without-nas</code><br>
</p>
</li>
<li><h5><code>--enable-<package name></code></h5>
<p><b>Examples:</b><br>
<code>--enable-openldap</code><br>
</p>
</li>
<li><h5><code>--disable-<package name></code></h5>
<p><b>Examples:</b><br>
<code>--disable-openldap</code><br>
<code>--disable-qadevoo</code><br>
<code>--disable-mozilla</code><br>
<code>--disable-access</code><br>
<code>--disable-evolution2</code><br>
</p>
</li>
<li><h5><code>--mandir=<dir></code></h5></li>
</ul>

=== Requirements ===
*A recent version of automake, such as the 1.9 series.
*If you don't have a working Java VM (i.e. any runtime), you should pass <code>--with-java=no</code> to either <code>autogen.sh</code> or <code>configure</code>.
*You need the Archive/Zip module for Perl (perl-Archive-Zip on RPM-based distributions, libarchive-zip-perl on dpkg-based distributions). Alternatively, see instructions[http://ooo.ximian.com/cpan.html] for obtaining Perl modules through CPAN.
*You need the development package for Python (this would be python-devel on RPM-based distributions).
*You need curl and curl-devel.
*You need odbc_config to be present. On SUSE systems, this is in the unixODBC-devel package.
*You need libsndfile and libsndfile-devel.
*If you don't have a recent enough openldap, pass <code>--disable-openldap</code> to <code>autogen.sh</code> or <code>configure</code>.
*You need neon and neon-devel.
*You need qt3 and qt3-devel, or if you don't have the KDE development packages, pass <code>--disable-kde</code> to <code>autogen.sh</code> or <code>configure</code>.
*You need mozilla-nss-devel.
*In SuSE, you need gecko-sdk.

=== download ===

<p>
By the time you've upgraded your system to the point that it
has all the packages you need to start building OO.o (mozilla etc. etc.) you're almost at the point that you
can download the bulk of the source. To do this, after a
successful configure simply type: <code>./download</code> and wait.
</p>
<p>
If for whatever reason this fails, you can verify your download
by fetching the equivalent .md5 file & comparing it to
the result of <code>md5sum <archive></code>. The source
archives are http://go-ooo.org/packages/SRC680
- put the source in ooo-build/src.
</p>

=== make ===

<p>
This is the taxing bit - type <code>make</code> and don't forget
to press enter. Quite possibly you want to log the output, so
why not <code>make 2>&1 | tee /tmp/log</code>.
</p>
<p>
Since ooo-build wraps the actual OO.o configuration &
build process, there are a number of internal config checks that
also need to pass. For a first time build it's well worth staying
near the console while everything unpacks, and the internal
configure runs; if that completes without incident - you're
usually into the heavy-duty thumb twiddling.
</p>

== See also ==

*[[Installing]]
*[[Tinderbox Setup]]
*[[BuildSpeedup]]
*[[OpenSUSE Build Instructions]]
*[[SUSE9.3 Build Instructions]]
*[[Ubuntu Build Instructions]]
*OpenOffice.org "Tools" page [http://tools.openoffice.org/dev_docs/build_linux.html]
*[[Build Tool Requirements]]

[[Category: Development]]

SUSE9.3 Build Instructions

2006-06-19T17:31:10Z

Pagalmes:

Speedprof

2006-06-05T09:56:21Z

Pagalmes: /* patch it */

=== what is it ===

Speedprof is an LD_PRELOAD based itimer (or hard real-time, or builtin CPU timer) based snapshot profiler. It samples at regular intervals (tweakable by reading the code ;-) and then presents a rather sexy data mining view so you can wind back full stack information - what function called what and when, self & cumulative times down trace paths etc.

=== how to get it ===

Checkout 'memprof' from GNOME [http://developer.gnome.org/tools/cvs.html CVS]:

export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'
cvs login
cvs -z3 co memprof

=== patch it ===

Then if you're on a reasonably recent system you need to patch it to use new TLS / NPTL threading support instead of the older linux pthreads assumptions; [http://go-oo.org/ooo-build/patches/test/memprof-nptl.diff patch].
<pre>
patch -p0 < memprof-nptl.diff
</pre>

=== install it ===

configure
make
make install

=== how to use it ===

speedprof ./soffice.bin -writer

Of course, the most useful mode is to use the 'reset' button - ie. get OO.o going to the state you're interested in. Hit reset - do something slow - hit 'Profile' and wander the trace.

=== downsides ===

* sometimes crashes the app - but hey, sometimes the app crashes under it's own steam too - hard to know whom to blame.
* doesn't work well with old systems (know to work well on SL10.0 with the patch eg.)
* doesn't like very long C++ symbols much - makes the columns somewhat unpleasant to use, needs some app tweakage.

Chart2

2006-05-24T14:27:43Z

Pagalmes:

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cws called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file chart2/source/tools/InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-24T10:14:08Z

Pagalmes: /* The errors reported and the solutions for m166. */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file chart2/source/tools/InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

==== The errors reported and the solutions for m155. ====

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-24T10:12:41Z

Pagalmes: /* ERROR 2 : The InternalDataProvider.cxx include error */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue [http://www.openoffice.org/issues/show_bug.cgi?id=63012 63012] :

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

==== The errors reported and the solutions for m155. ====

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-24T10:11:15Z

Pagalmes: /* The errors reported and the solutions for m166. */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

==== The errors reported and the solutions for m155. ====

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-24T09:43:24Z

Pagalmes: /* the xmerge problem */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5
The issue [http://www.openoffice.org/issues/show_bug.cgi?id=59368 59368]
explains it in a more detailed way.

To solve this, you only need to apply the patch attached to the issue :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

==== The errors reported and the solutions for m155. ====

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-24T09:40:50Z

Pagalmes: /* the unoxml problem */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue [http://www.openoffice.org/issues/show_bug.cgi?id=65110 65110],
in the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : '''tools''' offuh cppuhelper LIBXML2:libxml2 NULL
ux unoxml\source\dom nmake - all ux_dom NULL
ux unoxml\source\xpath nmake - all ux_xpath ux_dom NULL
ux unoxml\source\events nmake - all ux_events ux_dom NULL
ux unoxml\source\service nmake - all ux_service ux_dom ux_xpath ux_events NULL
</pre>

Then, to rebuild, just type :

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5

The issue : http://www.openoffice.org/issues/show_bug.cgi?id=59368

In it, there is only a need to apply the patch posted there :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

==== The errors reported and the solutions for m155. ====

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-24T09:37:22Z

Pagalmes: /* ERROR 1 : unoxml, xmerge, xmlhelp, chart2 */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/
modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue http://www.openoffice.org/issues/show_bug.cgi?id=65110
In the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : tools offuh cppuhelper LIBXML2:libxml2 NULL
</pre>

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5

The issue : http://www.openoffice.org/issues/show_bug.cgi?id=59368

In it, there is only a need to apply the patch posted there :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

==== The errors reported and the solutions for m155. ====

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-24T09:33:03Z

Pagalmes: /* The bugs reported and the solutions. */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The errors reported and the solutions for m166. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : unoxml, xmerge, xmlhelp, chart2 =====

While compiling, the following error will rise :

<pre>
LINK: ../uiconfig/sglobal/statusbar/statusbar.xml -> /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/xml/uiconfig/modules/sglobal/statusbar/statusbar.xml
Use of uninitialized value in string eq at /home/pagalmes/workspace/chart2_m166/src680-m166/solenv/bin/deliver.pl line 791.
LOG: writing /home/pagalmes/workspace/chart2_m166/src680-m166/solver/680/unxlngi6.pro/inc/sw/deliver.log
Statistics:
Files copied: 137
Files unchanged/not matching: 6

4 module(s):
unoxml
xmerge
xmlhelp
chart2
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmlhelp/source/com/sun/star/help
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/xmerge/source/xmerge
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/chart2/source/tools
ERROR: error 65280 occurred while making /home/pagalmes/workspace/chart2_m166/src680-m166/unoxml/source/service

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from unoxml xmerge xmlhelp chart2"
</pre>

===== the solution =====

====== the unoxml problem ======

As explained in issue http://www.openoffice.org/issues/show_bug.cgi?id=65110
In the file unoxml/prj/build.lst the first line has to be changed to add 'tools' in it :

<pre>
ux unoxml : tools offuh cppuhelper LIBXML2:libxml2 NULL
</pre>

<pre>
cd unoxml; build; cd ../instsetoo_native; build --all
</pre>

====== the xmerge problem ======

This is only a problem if you try to compile OOo with Java 1.5

The issue : http://www.openoffice.org/issues/show_bug.cgi?id=59368

In it, there is only a need to apply the patch posted there :

<pre>
cd src680-m166
patch -p0 < [filename]
</pre>

==== The errors reported and the solutions for m155. ====

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-23T12:38:08Z

Pagalmes: /* Setting the environment */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.Set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-23T12:31:46Z

Pagalmes: /* Configuring */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
cd config_office
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-23T12:29:25Z

Pagalmes: /* Configuring */

''Chart2'' is a sub-project of the [http://graphics.openoffice.org/chart/chart.html OpenOffice.org Chart Project]. Our goal is to develop a new Chart component for (presumably) OOo 2.6.

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m166 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m166 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m166 OpenOffice
</pre>

====== Update the CWS modifications ======

Once you downloaded the "standard" sources (also called HEAD), you need to update
them because the chart module modifications are in a separated cxw called chart2mst3.
You need to update only the modified modules. To know which modules have been modified,
check the
[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 EIS page related to the chart module.]
On this page, you will find a section called "Modules & Files" which describes the
modified modules.

For each module (subdir) you will need to do :

<pre>
cd name_of_the_module
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Configuring =====

Once you downloaded all the sources, you can start configuring the build.

<pre>
./configure
</pre>

If you forgot to install some dependencies, the configure will remind you
which one are lacking. You can check the one needed on the
[http://tools.openoffice.org/ tool page]

A nice trick for configuring OOo is to create a script in which you write
all the options activated for your build. This helps if you want to see
which options where enabled during the build some days after you compiled
everything. Here is an example :

<pre>
#! /usr/bin/batch
./configure --with-jdk-home="/home/pagalmes/bin/jdk1.5.0_06/" --with-ant-home="/usr/bin/ant" --with-lang="en fr"
</pre>

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m166/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code without
facing a small number of issues. Here are the issues we already found and ways to
correct them.

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Main Chart Project Page: http://graphics.openoffice.org/chart/chart.html
* Chart Specifications: http://specs.openoffice.org/chart/index.html
* Current CWS Name: [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel: #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]
[[Category:Chart2]]

Chart2

2006-05-23T12:12:32Z

Pagalmes: /* Configuring */

Chart2

2006-05-23T10:16:30Z

Pagalmes: /* Vanilla */

Chart2

2006-05-23T10:09:19Z

Pagalmes: /* Vanilla */

Chart2

2006-05-23T09:23:51Z

Pagalmes:

Chart2

2006-05-23T09:22:22Z

Pagalmes: /* Compiling OpenOffice.org : the practice */

Chart2

2006-05-23T09:12:57Z

Pagalmes: /* Configuring */

Chart2

2006-05-23T08:51:51Z

Pagalmes: /* Update the CWS modifications */

Chart2

2006-05-23T08:47:06Z

Pagalmes: /* Update the CWS modifications */

Chart2

2006-05-23T08:27:25Z

Pagalmes: /* Vanilla */

Chart2

2006-05-23T08:24:59Z

Pagalmes: /* Download the milestone */

Chart2

2006-04-18T16:35:57Z

Pagalmes:

Charts are used for visualizing data sets from e.g. spreadsheets by two and three dimensional diagrams. There are a lot of different two- and three-dimensional chart types you can choose from. This page gathers information about the new chart implementation of OpenOffice.org. It is especially written to help new comers to the process of developping in the new OOo chart module.

If you would like to participate, if you have comments or questions related to the chart you are welcome on the graphics mailinglists: (users,dev,features,bugs,cvs)@graphics.openoffice.org. See also the section at the bottom of this page called [Some useful information].

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m152 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m152 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m152 OpenOffice'
</pre>

====== Update the CWS modifications ======

TODO :this is still to be done !!!!

mettre update les fichiers pour correspondre au cws chart2mst3

Go to the EIS page related to the chart

<pre>
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

in all modules (subdirs) as listed in the EIS page gets you the
correct branch. See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== Configuring =====

- Créer un fichier dans lequel on met toutes les options de compilation.
- Détailler les options utiles.
- Lancer le configure
- Vérifier que toutes les dépendances sont remplies.

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m152/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing - you won't need it)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]
* IRC channel : #chart2.openoffice.org (on freenode)

[[Category:Calc issues]]

Chart2

2006-04-18T16:18:30Z

Pagalmes: /* The bugs reported and the solutions. */

This page gathers information about the new chart implementation of OpenOffice.org.

HERE - ADD some more information to make it look less empty...

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m152 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m152 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m152 OpenOffice'
</pre>

====== Update the CWS modifications ======

TODO :this is still to be done !!!!

mettre update les fichiers pour correspondre au cws chart2mst3

Go to the EIS page related to the chart

<pre>
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

in all modules (subdirs) as listed in the EIS page gets you the
correct branch. See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== Configuring =====

- Créer un fichier dans lequel on met toutes les options de compilation.
- Détailler les options utiles.
- Lancer le configure
- Vérifier que toutes les dépendances sont remplies.

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m152/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing - you won't need it)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : The InternalDataProvider.cxx include error =====

This error has been reported as issue 63012 : http://www.openoffice.org/issues/show_bug.cgi?id=63012

<pre>
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
------------------------------
Making: ../../unxlngi6/slo/InternalDataProvider.obj
g++ -Wreturn-type -fmessage-length=0 -c -I. -I. -I../inc -I../../source/inc -I../../inc -I../../unx/inc -I../../unxlngi6/inc -I.
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/external
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc -I/home/pagalmes/workspace/OpenOffice/solenv/unxlngi6/inc
-I/home/pagalmes/workspace/OpenOffice/solenv/inc -I/home/pagalmes/workspace/OpenOffice/res
-I/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl -I/home/pagalmes/workspace/OpenOffice/solenv/inc/Xp31
-I/opt/j2sdk1.4.2_09/include -I/opt/j2sdk1.4.2_09/include/linux -I/opt/j2sdk1.4.2_09/include/native_threads/include -I/usr/X11R6/include
-I. -I../../res -I. -g -O0 -pipe -mtune=pentiumpro -Wno-ctor-dtor-privacy -fvisibility-inlines-hidden -g -fexceptions -fno-enforce-eh-specs
-fpic -DLINUX -DUNX -DVCL -DGCC -DC341 -DINTEL -D_STLP_DEBUG -DCVER=C341 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR
-D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -DHAVE_GCC_VISIBILITY_FEATURE -D__DMAKE -DUNIX -DCPPU_ENV=gcc3
-DGXX_INCLUDE_PATH=/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2 -DSUPD=680 -DDEBUG -DDBG_UTIL -DOSL_DEBUG_LEVEL=2
-DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DSRC680=SRC680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi6/slo/InternalDataProvider.o

/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/home/pagalmes/workspace/OpenOffice/chart2/source/tools/InternalDataProvider.cxx
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:100:
erreur: use of ‘__false_type’ is ambiguous
/usr/lib/gcc/i386-redhat-linux/4.0.2/../../../../include/c++/4.0.2/bits/cpp_type_traits.h:94:
erreur: first declared as ‘struct __false_type’ here
/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/inc/stl/stl/type_traits.h:65:
erreur: also declared as ‘struct _STLD::__false_type’ here

[...]
dmake: Error code 1, while making '../../unxlngi6/slo/InternalDataProvider.obj'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/home/pagalmes/workspace/OpenOffice/chart2/source/tools
</pre>

===== The solution =====

The following line at the beginning of the file InternalDataProvider.cxx :

<pre>
#include <valarray>
</pre>

Has to be put as the first include in the file. No solution has been found for now.

===== ERROR 3 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]

[[Category:Calc issues]]

Chart2

2006-04-11T16:16:54Z

Pagalmes: /* Developping for the new chart module */

This page gathers information about the new chart implementation of OpenOffice.org.

HERE - ADD some more information to make it look less empty...

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m152 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m152 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m152 OpenOffice'
</pre>

====== Update the CWS modifications ======

TODO :this is still to be done !!!!

mettre update les fichiers pour correspondre au cws chart2mst3

Go to the EIS page related to the chart

<pre>
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

in all modules (subdirs) as listed in the EIS page gets you the
correct branch. See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== Configuring =====

- Créer un fichier dans lequel on met toutes les options de compilation.
- Détailler les options utiles.
- Lancer le configure
- Vérifier que toutes les dépendances sont remplies.

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m152/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing - you won't need it)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

* How to build only a particular project :

* How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

* How to test the modifications done to the chart module :

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]

[[Category:Calc issues]]

Chart2

2006-04-11T16:16:17Z

Pagalmes: /* Compiling the new chart module */

This page gathers information about the new chart implementation of OpenOffice.org.

HERE - ADD some more information to make it look less empty...

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m152 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m152 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m152 OpenOffice'
</pre>

====== Update the CWS modifications ======

TODO :this is still to be done !!!!

mettre update les fichiers pour correspondre au cws chart2mst3

Go to the EIS page related to the chart

<pre>
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

in all modules (subdirs) as listed in the EIS page gets you the
correct branch. See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== Configuring =====

- Créer un fichier dans lequel on met toutes les options de compilation.
- Détailler les options utiles.
- Lancer le configure
- Vérifier que toutes les dépendances sont remplies.

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m152/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing - you won't need it)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

== Developping for the new chart module ==

The common steps.

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]

[[Category:Calc issues]]

Chart2

2006-04-11T16:15:10Z

Pagalmes: /* Update the CWS modifications */

This page gathers information about the new chart implementation of OpenOffice.org.

HERE - ADD some more information to make it look less empty...

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m152 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m152 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m152 OpenOffice'
</pre>

====== Update the CWS modifications ======

TODO :this is still to be done !!!!

mettre update les fichiers pour correspondre au cws chart2mst3

Go to the EIS page related to the chart

<pre>
cvs -z3 update -dP -r cws_src680_chart2mst3
</pre>

in all modules (subdirs) as listed in the EIS page gets you the
correct branch. See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== Configuring =====

- Créer un fichier dans lequel on met toutes les options de compilation.
- Détailler les options utiles.
- Lancer le configure
- Vérifier que toutes les dépendances sont remplies.

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m152/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing - you won't need it)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

==== Development life cycle ====

How to build only a particular project :

How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

How to test the modifications done to the chart module :

== Developping for the new chart module ==

The common steps.

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]

[[Category:Calc issues]]

Chart2

2006-04-11T16:14:46Z

Pagalmes: /* Getting the sources */

This page gathers information about the new chart implementation of OpenOffice.org.

HERE - ADD some more information to make it look less empty...

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

===== dependencies =====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

===== Getting the sources =====

====== Introduction ======

Once you have all the dependencies installed, you will need to download the sources
of OOo. When working on a specific cws (for us, the "chart2mst3" cws) you will need
to follow two steps :

* downloading the OOo sources at a specific milestone
* downloading the specific modifications for the cws from the repository

====== Download the milestone ======

For the chart module, you will need to download the m152 milestone. The milestone
needed will change from time to time, so stay tuned ;-)

To download the milestone, you have several choices.

* Download from the cvs servers
* Download a pre-packaged version
* Download from the main OOo servers

Have a look at the following page for more explanations :
http://wiki.services.openoffice.org/wiki/Getting_It

Some advices :

I would recommend that you download a pre-packaged version of m152 from the
following link :
http://go-ooo.org/packages/SRC680/

This will save you time compared to downloading the cvs version.

If you still want to download it from the cvs, you can use the following :
<pre>
cvs -z3 co -r SRC680_m152 OpenOffice'
</pre>

====== Update the CWS modifications ======

TODO :this is still to be done !!!!

mettre update les fichiers pour correspondre au cws chart2mst3

Go to the EIS page related to the chart

'cvs -z3 update -dP -r cws_src680_chart2mst3'

in all modules (subdirs) as listed in the EIS page gets you the
correct branch. See also cws-extract from oobuild, if you want/need to
work with diffs (which will get HUGE, though)

Note : cwsclone ??? What's its use ??

===== Configuring =====

- Créer un fichier dans lequel on met toutes les options de compilation.
- Détailler les options utiles.
- Lancer le configure
- Vérifier que toutes les dépendances sont remplies.

===== Building the tools (dmake...) =====

During the compiling step, the compiling process needs some tools to achieve
the build. Before compiling, you need to build those tools. For example,

* dmake
* ...

To compile the tools, just type :

<pre>
cd openOffice.org_m152/
./bootstrap
</pre>

===== Setting the environment =====

Before starting to compile OOo, you need to set all the environment variables

<pre>
tcsh
source LinuxIntelEnv.set
setenv nodep "TRUE" ; setenv NO_HIDS "TRUE" ; setenv MAXPROCESS 2
rehash
</pre>

* '''nodep''' : inhibits generation of dependency files
* '''maxprocess''' : sets the number of parallel dmakes per dir
* '''NO_HIDS''' prevents generation of HIDs (that's used for automated testing - you won't need it)

===== Compiling (finally...;-) =====

<pre>
cd instsetoo_native
build -P2 --dlv_switch -link --all
</pre>

* ''' -P2''' : fires up more than one dmake in _different_ dirs - thus, you end up with a maximum for 4 parallel compilations
* '''--dlv_switch -link''' : tells deliver not to copy files to solver, but link instead -> saves space

==== OOoBuild ====

For this section, you should read the part called "Getting started with OOo development" on the wiki :
http://wiki.services.openoffice.org/wiki/Main_Page

===== Downloading OOoBuild =====

===== Downloading the sources =====

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

===== ERROR 1 : the odk / sdk error =====

While compiling the Chart module, in the ODK project an error will rise :

<pre>
build -- version: 1.145
=============
Building project sdk_oo
=============
/home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
dmake: Error -- `/home/pagalmes/workspace/OpenOffice/solver/680/unxlngi6/bin/odk_oo.zip' not found, and can't be made
'---* RULES.MK *---'
ERROR: Error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sdk_oo/pack/unzip_odk
</pre>

===== the solution =====

Just ignore the two osdk and sdk_oo project not needed for compiling OOo :

<pre>
cd instsetoo_native/util && build--since sdk_oo
</pre>

===== ERROR 2 : the mandriva desktop error =====

While compiling, you may get the following error message :

<pre>
1 module(s):
sysui
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/mandriva
ERROR: error 65280 occurred while making /home/pagalmes/workspace/OpenOffice/sysui/desktop/redhat

Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from sysui"
</pre>

===== the solution =====

Try building the sysui project :

<pre>
cd sysui
build
</pre>

An error message should rise from this module.

<pre>
Eror message :

[...] /home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm :
no such file or directory

Error code 1, while making
'/home/pagalmes/workspace/OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration/openoffice.org-mandriva-menus-2.0.2-152.noarch.rpm'
</pre>

This problem is solved by creating the following directory :

<pre>
OpenOffice/sysui/unxlngi6.pro/bin/desktop-integration
</pre>

Note : This error has been corrected with m155

==== Development life cycle ====

How to build only a particular project :

How to rebuild everything from scratch :
(erase the ".dlp" files or smthg like that ??)

How to test the modifications done to the chart module :

== Developping for the new chart module ==

The common steps.

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]

[[Category:Calc issues]]

Chart2

2006-04-11T16:09:43Z

Pagalmes: /* Compiling OpenOffice.org : the practice */

Chart2

2006-04-11T15:05:50Z

Pagalmes: /* Compiling OpenOffice.org : the practice */

Chart2

2006-04-10T18:23:50Z

Pagalmes: /* OOoBuild */

Chart2

2006-04-10T18:17:52Z

Pagalmes: /* The bugs reported and the solutions. */

Chart2

2006-04-10T18:09:32Z

Pagalmes: /* The bugs reported and the solutions. */

Chart2

2006-03-28T22:37:27Z

Pagalmes: /* Commmon steps */