OO.o or Go-oo?

Lufbery · 02-15-2010, 06:31 PM

Hey guys,

Have you seen the build script for Go-OO on their downloads page?

If you download it and untar it, it has, among other things a script for downloading the sources and a Slackware-specific config.in file. Here's that file:

Code:

--with-vendor=\"Slackware\"
--with-gcc-speedup=ccache
--with-openclipart=/usr/share/openclipart
--with-java
--with-ant-home=/usr/lib/apache-ant
--enable-bonobo
--enable-cairo
--enable-access
--with-x
--enable-libart
--enable-libsn
--with-system-neon
--with-system-expat
--with-system-sane-header
--with-system-curl
--disable-odk
--disable-mono
--with-system-libpwd
--with-system-python
--enable-openxml
--with-system-gcc
--with-system-boost
--with-system-db
--with-system-mozilla=xulrunner
--enable-openldap
--enable-arch=x86
--with-system-libsvg
--with-system-cairo
--with-system-sndfile
--with-binsuffix=3.0
--disable-pam
--disable-pam-link

Now, the only thing to change for a x86_64 build is the "--enable-arch" line.

Otherwise, I have XULrunner installed, so that shouldn't be a problem. I'm not sure about ant, though...

I'm going to work through this a bit more, especially to see if I can get this script to work with src2pkg to create a real package when everything is done.

Meanwhile, I think it's pretty sad that Go-OO is having trouble opening .doc files. Open Office 3.1 is working great for me. It opens both .doc and .docx files without problems.

Regards,

gargamel · 02-15-2010, 07:25 PM

Quote:

Originally Posted by Lufbery

[...]

Meanwhile, I think it's pretty sad that Go-OO is having trouble opening .doc files. Open Office 3.1 is working great for me. It opens both .doc and .docx files without problems.

Regards,

As far as I understand, Go-OO is the OO.o derivative that is used by OpenSuSE. To be honest, this is one of the reasons, Slackware has replace OpenSuSE as my preferred system. Among the problems I had was font rendering in the application GUI. I never found out, how to get a crisp and clear text rendering in menus and icon bars. No problem in the document pane, though, because there I was able to optimise the rendering with the usual OO.o options.
Then I installed OO.o on OpenSuSE, and guess what? All texts were crisp and clear.

Now, when I read about this .doc/.docx import problem, it reminds me of my own experience with this OO.o fork, and why I stick with the original.

I have to say, that I liked the seamless desktop integration of Go-OO (if it really is, what they use) in OpenSuSE, but in the end I prefer something that just works, and bad font rendering is no good for my eyes --- I use OO.o a lot, and after a while it is really annoying, when you always think your glasses are insufficient...

gargamel

samac · 02-16-2010, 02:21 AM

There is a slackbuild for it on slackbuilds.org and also another on this page http://dev.opennix.com/repositories/show/slackbuilds. A nice big download, a huge compile time and a shiny new slackware-package.tgz for you to install.

samac

Lufbery · 02-16-2010, 08:18 AM

Quote:

Originally Posted by samac

There is a slackbuild for it on slackbuilds.org and also another on this page http://dev.opennix.com/repositories/show/slackbuilds. A nice big download, a huge compile time and a shiny new slackware-package.tgz for you to install.

samac

Cool!

That's good news. It looks like it builds from source too, instead of being a repackaging of binaries -- not that there's anything wrong with that.

Seriously, though, the Slackbuilds repackaging of Open Office 3.1 (and previous versions) has worked very well for me for a few years now. I don't need Go-OO -- especially if it's having trouble opening .doc files right now. But, I want to test it and see if the enhancements are really worth it.

Regards,

samac · 02-16-2010, 08:27 AM

I have go-oo 3.1.1 compiled from source and I have had no problems opening .doc files. Perhaps if there is an online .doc/.docx that people know is problematic I could test this file.

samac

H_TeXMeX_H · 02-16-2010, 08:40 AM

As for the problem opening .doc files, it seems that the binaries were build incorrectly, so building it from source will work. The binaries will be fixed and re-uploaded to the servers by the end of the week (probably).

hitest · 02-16-2010, 09:06 AM

I'm very happy with OOo 3.2 on Slackware 13.0. I'm using rworkman's package, it does the job for me.

Lufbery · 02-16-2010, 10:00 AM

Quote:

Originally Posted by H_TeXMeX_H

As for the problem opening .doc files, it seems that the binaries were build incorrectly, so building it from source will work. The binaries will be fixed and re-uploaded to the servers by the end of the week (probably).

That's good news. I'll start my build tonight and see how things go.

Lufbery · 02-16-2010, 08:03 PM

Okay, the build fails on Slackware64_13 (not multilib) with this error:

Code:

checking for java... no                                                                                   
checking the installed JDK... configure: error: JAVA not found. You need at least jdk-1.5, or gcj-4

I have Java jdk 1.6 in /usr/lib64/jdk1.6.0_16

I installed it from /extra on the Slackware64_13 DVD.

java -version gives me:

Code:

java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)

So, the build is looking for Java but not finding it. Any suggestions?

Thanks,

Old_Fogie · 02-16-2010, 10:57 PM

Quote:

Originally Posted by gargamel

AAmong the problems I had was font rendering in the application GUI. I never found out, how to get a crisp and clear text rendering in menus and icon bars.
gargamel

From my kjots file ( got it from an openoffice thread somewhere... I can't recall / find the original URL)
.
Tools -> Options -> OpenOffice.org -> Font Replacement
.
from the menu. Check the "Apply Replacement Table" check box. Replace the font
.
Andale Sans UI
.
with the desired font.

ponce · 02-17-2010, 12:40 AM

Quote:

Originally Posted by Lufbery

So, the build is looking for Java but not finding it. Any suggestions?

you can try passing this additional argument to the configure in the slackbuild

Code:

--with-jdk-home=/usr/lib${LIBDIRSUFFIX}/java

samac · 02-17-2010, 07:37 AM

I think that I had to add without-java to the slackware.in file, but still required jdk to be installed.

samac

Lufbery · 02-17-2010, 08:46 AM

Thanks Ponce and Samac.

Ponce, do I add what you posted exactly as you posted it with the variable in place?

ponce · 02-17-2010, 10:01 AM

referring to this slackbuild, you can put it between any line of the configure options, for example lines 68-69 become

Code:

./configure \
   --with-jdk-home=/usr/lib${LIBDIRSUFFIX}/java \
   --prefix=/usr \

LIBDIRSUFFIX has to be defined in the slackbuild (on mike's one is defined on line 25 for your ARCH).

cwizardone · 02-19-2010, 03:21 PM

Well, using the Go-OO 3.2 files dated 17 Feb. 2010, and H_TeXMeX_H's script (Thank you very much) I was able to download and create an installable package.
So far it has opened every .doc file I've thrown at it including one that wouldn't open in Go-OO 3.1.1. Now, if I can get the sound to work in Impress I'll be a happy camper.