Message: previous - next
Month: January 2012

Re: [trinity-devel] How to build Koffice without components

From: "E. Liddell" <ejlddll@...>
Date: Fri, 6 Jan 2012 08:40:09 -0500
On Thu, 5 Jan 2012 13:47:13 -0800 (PST)
Darrell Anderson <humanreadable@...> wrote:

> > I haven't looked lately, but I suspect:
> > 
> > DO_NOT_COMPILE="component1 component2" \
> >     ./configure --prefix=$TRINITY_PREFIX ...
> > 
> > may work.  At least that worked in koffice-1.6.1.
> I have not posted any follow-ups, but yes, a few days ago I discovered that option. Another option seems to be to edit the subdirs text file in the sources root directory.
> Although these options work, and I have tested them to some degree, there seem to be some internal dependencies that I have not yet isolated. For example, I seem unable to build kword unless I build kspread too. I'll keep playing with those options. Perhaps eventually I can post the information to the wiki.
> I believe the Arch people at one time built all kde3 packages this way. I have been unable to find that information or specific build scripts to study. I think a few tweaks here and there are needed to take full advantage of these build options. Knowing what they might be would be nice.

Gentoo ebuilds for these are still in existence, and there is some library detail in them.
kword seems to be dependant on libkspreadcommon, which I assume to be part of kspread.
Fragment from kword-1.6.3_p20090204.ebuild which appears to detail libraries to copy from
other parts of the koffice tarball:

KMCOPYLIB="libkformula lib/kformula
        libkofficecore lib/kofficecore
        libkofficeui lib/kofficeui
        libkopainter lib/kopainter
        libkotext lib/kotext
        libkwmf lib/kwmf
        libkowmf lib/kwmf
        libkstore lib/store
        libkspreadcommon kspread"

Unfortunately, I can't translate the above information into options for make without combing
through a mass of shell script, but it might at least give you a starting point.