Hi,
Thanks a lot for the Openoffice porting infomations.
I'm compiling Openoffice for ARM eabi,I use qemu and run debian on it.
I compiled it with debian script as debian/rules build
I found it is too slow(It compiled for 7 days and still compiling now).
I installed distcc and use "debian/rules build CC=distcc CXX=distcc" but it
seems no effect,my distcc server recieved no distcc request.
How do you compiled it with distcc? I want use it to speed up my compile.
Caolan McNamara Wrote:
On Tue, 2008-01-29 at 22:42 +0530, Midhun A wrote:
Hi,
Thanks a lot for the replies.
Though I would reccommend you build your own 2.4.0 OOH680_mX candidate
from scratch for real testing, e.g. I built the armeabi one with java
I would like to build one myself. Is there a page/link where I can
find how? Or should I try it myself? Is the page for building
OpenOffice from sources(http://tools.openoffice.org) fine to start
with? I do have cross-compiler for arm based on gcc 3.4.6.
I'd suggest to first get OOo built on a "standard" platform like i386 or
x86_64 so you have a known working platform to compare against.
Afterwards, unfortunately, OOo isn't really truly cross-buildable, but
what I would do is to install distcc client on the arm and distcc server
on the host with the PATH on the host set up to use the arm
cross-compiler and the DISTCC_HOSTS on the arm client pointing to the
server. That works at least to shift the compilation off the arm.
C.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
