OpenOffice.org-2.0.2

[Randy McMurchy]

Version increment to 2.0.1

[martyman99999@…]

Glory be. I appear to have gotten this to build. One compile problem and three makefile problems.

I never did get 2.0.0 to come up. It threw a CorruptedFilterConfigurationException right away. I now understand that in 2.0.0 the build failed to do something and failed to report the error. In 2.0.2 the build failed to do something and did report the error. Which I was then able to solve.

More after I revisit and get proper patches and solve the makefile things the right way, and do a little more thorough functional checkout.

• Marty Jack

[bdubbs@…]

Excellect. Keep us posted on the details so we dont have to reinvent the wheel. We appreciate teh input a lot.

[martyman99999@…]

Discussion of what I fixed and why, build cookbook updates

[martyman99999@…]

My configuration, for reference

[martyman99999@…]

Patch, maybe in a form you can download

[martyman99999@…]

I'll continue to test and if you all have the inclination, please do. I'll look into finishing up that one item and also getting the patches submitted to the developers. It looks like I don't know how to upload the patch in a way that can be downloaded so if someone could straighten that out and tell me how to do it the right way, please ...

[bdubbs@…]

I updated (replaced) the patch, but have a question. There are several places in the patch that refer to Firefox. Do these changes need to be made for mozilla/seamonkey?

Looking at the rest of the patch, it seems pretty dumb that a developer used a keyword, enum, as a variable!

[martyman99999@…]

The patch is written so that if you are using either system Mozilla or system Firefox it will work. I don't have Seamonkey and so don't know how it lays out its pkgconfig file. If you were to look in /usr/lib/pkgconfig and tell me what you see maybe we can adjust that as well (but of course they may claim it isn't supported since Seamonkey just came out).

What seems a little odd to me is how Java 1.5 and OpenOffice have each been out for over a year and there are still compile issues. It has to be that they are still using an older version for their own builds.

I have since learned that --disable-odk doesn't have any effect on the output of the build that we care about. If you take the OpenOffice_SDK path down from instsetoo_native rather than the OpenOffice path that's where that part goes, so we don't install it anyway. So maybe the best answer is "don't do that" to --disable-odk. It still should be that selecting a configuration options shouldn't break the build, but it does lower the priority.

[bdubbs@…]

I'm not sure which you want:

seamonkey-gtkmozembed.pc seamonkey-js.pc seamonkey-nspr.pc seamonkey-nss.pc seamonkey-plugin.pc seamonkey-xpcom.pc

They all have: prefix=/usr exec_prefix=/usr libdir=/usr/lib/seamonkey-1.0 includedir=/usr/include/seamonkey-1.0

xpcom.pc also has:

idldir=/usr/share/idl/seamonkey-1.0

[martyman99999@…]

It would be the seamonkey-plugin.pc that it would want to reference.

If you say --with-system-mozilla it wants mozilla-plugin.pc If you say --with-system-mozilla --with-firefox it wants firefox-plugin.pc

If you have no mozilla-plugin.pc to go with your seamonkey-plugin.pc then there would need to be something done. To do it right would take a --with-seamonkey and code similar to what I did for --with-firefox. It's up to you if you want to depart that much from the shipped sources and have to redevelop it every time they ship. One thing you could do for testing is symlink seamonkey-plugin.pc to also be mozilla-plugin.pc and see how that works.

[bdubbs@…]

We could create a symlink, but I do have mozilla installed too:

$ diff seamonkey-plugin.pc mozilla-plugin.pc 3,4c3,4 < libdir=/usr/lib/seamonkey-1.0 < includedir=/usr/include/seamonkey-1.0 ---

libdir=/usr/lib/mozilla-1.7.12 includedir=/usr/include/mozilla-1.7.12

8,9c8,9 < Version: 1.0 < Requires: seamonkey-xpcom = 1.0 ---

Version: 1.7.12 Requires: mozilla-xpcom = 1.7.12

[martyman99999@…]

If that's the case, you should be able to build. My guess is a more extensive amount of work would have to be done in the OpenOffice product to support Seamonkey, so time will tell whether Sun er OpenOffice.org does it. Let's keep this on the to investigate whether it works during checkout list.

[martyman99999@…]

Printing doesn't work out of the box. The directories /opt/openoffice-2.0.2/share/psprint/driver and .../fontmetric are not populated. Apparently they are not built even if you asked for them due to this configure issue. I didn't ask for them thinking that the system installed fonts and PPDs would be used. Guess not.

​http://qa.openoffice.org/issues/show_bug.cgi?id=62068

I populated these directories from a previous install from RPM on the host system and printing works. Would have to look into how to get this done properly during the build.

[martyman99999@…]

A copy of psprint_config/configuration/afm/*.afm to /opt/openoffice-2.0.2/share/psprint/fontmetric and psprint_config/configuration/ppds/*.PS to /opt/openoffice-2.0.2/share/psprint/driver will do what is needed.

[DJ Lucas]

Completed