Re: Will somebody make a OpenOffice-Port?

2005-07-20 Thread Ian Darwin

Todd T. Fries wrote:

What I sent was based on your 1.1.x port, that is where I started at 
c2k5.  I got far enough to realize we needed a rather dated mozilla 
devel laying around for it to build and opted for the more recent 
openoffice.


The first question someone working on the port will want to know is, 
how did you get the STLport to be recognized externally to 
OpenOffice?  Do you feel it to even be in the realm of possibility to 
eventually have OpenOffice only compile those components that are not 
in the native ports tree, to avoid much duplicated build time and 
patching time?


I have attached an updated STLport I prepared, but the last time I 
tried building OpenOffice against it, it seemed I could not figure out 
where the right places were to insert the pieces to get OpenOffice to 
recognize it outside the build tree...


Might be worth committing this, because it's one hurdle that anybody 
looking at OOo has to deal with. It seems to compile fine on -current.


Thanks
Ian



Re: Will somebody make a OpenOffice-Port?

2005-06-22 Thread Edd Barrett

Hi,



This url is now dead, is there not a port of OO maintained anymore?

Why is it that we must use linux emulation? FreeBSD have managed to build

a native port I believe.



Thanks



On Tue, Jan 13, 2004 at 03:00:25AM +0100, Rembrandt wrote:

 Is there somebody wich is working on an OpenOffice port?

 I read something about to make it work in the mailinglistarchiv.

 So is there a (un)official port in work somewhere couse I'm intrested to 
 test it (if it exist).

Yes it works fine on i386 with compat_linux. And there is a port for it.

You can check http://beastie.hu/anoncvs for our unoffical ports.

Or just do a 

cvs -d [EMAIL PROTECTED]:/cvs co ports/productivity/openoffice-linux

The ports is from Michael Schubert [EMAIL PROTECTED] thanks for it

Michael.



Re: Will somebody make a OpenOffice-Port?

2005-06-22 Thread Lars Hansson
On Wed, 22 Jun 2005 05:30:03 -0500 (CDT)
Edd Barrett [EMAIL PROTECTED] wrote:

 This url is now dead, is there not a port of OO maintained anymore?
It would appear not.

 Why is it that we must use linux emulation?
Because OO is inherently a behemoth to port and apparently noone
with the skills necessary has felt the urge to undertake it.

 FreeBSD have managed to build a native port I believe.
That's great for them, I guess. It's possibly that their work could be
used when porting to openbsd but I wouldnt know and I have personally
no wish to find out.

---
Lars Hansson



Re: Will somebody make a OpenOffice-Port?

2005-06-22 Thread Michael Schubert

On Jun 22, 2005, at 7:00 AM, Todd T. Fries wrote:
[snip]
Oh, um, once you d/l the src, you need to s/^M//g on all the  
Makefile's. It took me a few hours to realize the special make  
program distributed with openoffice bombs out on OpenBSD with them  
there.  Obviously this would need to be integrated into the ports  
openoffice2/Makefile, but I was working on getting it to build.  It  
builds some things, but bombs on  STLport .. I tried making a port  
of STLport and pointing OpenOffice2 to it, but that didn't work out  
either...


So, whoever wants to run with this can feel free to pick up these  
pieces and have .. fun!   I can't promise to get back to this  
anytime soon.


http://schubert.cx/etc/openoffice.php has links to (horribly  
outdated) ports of STLport and friends.


I was recently asked about tackling a native port but alas someone  
waved a lucrative job offer in front of me first. :-)


But if anyone does undertake this task feel free to hit me up for  
questions.


I did download a pre-2.0 source snapshot of OpenOffice and ran my  
1.1.x diffs against it... about 165 of ~200 patches broke, hopefully  
most of those are trivial.


--
Michael Schubert  [EMAIL PROTECTED]

Maintaining badly written code is like trying to solve a crossword
puzzle set by someone who can't spell -- Jacob Kaplan-Moss






Re: Will somebody make a OpenOffice-Port?

2005-06-22 Thread Todd T. Fries
What I sent was based on your 1.1.x port, that is where I started at 
c2k5.  I got far enough to realize we needed a rather dated mozilla 
devel laying around for it to build and opted for the more recent 
openoffice.


The first question someone working on the port will want to know is, how 
did you get the STLport to be recognized externally to OpenOffice?  Do 
you feel it to even be in the realm of possibility to eventually have 
OpenOffice only compile those components that are not in the native 
ports tree, to avoid much duplicated build time and patching time?


I have attached an updated STLport I prepared, but the last time I tried 
building OpenOffice against it, it seemed I could not figure out where 
the right places were to insert the pieces to get OpenOffice to 
recognize it outside the build tree...


Michael Schubert wrote:

On Jun 22, 2005, at 7:00 AM, Todd T. Fries wrote:
[snip]

Oh, um, once you d/l the src, you need to s/^M//g on all the  
Makefile's. It took me a few hours to realize the special make  
program distributed with openoffice bombs out on OpenBSD with them  
there.  Obviously this would need to be integrated into the ports  
openoffice2/Makefile, but I was working on getting it to build.  It  
builds some things, but bombs on  STLport .. I tried making a port  of 
STLport and pointing OpenOffice2 to it, but that didn't work out  
either...


So, whoever wants to run with this can feel free to pick up these  
pieces and have .. fun!   I can't promise to get back to this  anytime 
soon.



http://schubert.cx/etc/openoffice.php has links to (horribly  outdated) 
ports of STLport and friends.


I was recently asked about tackling a native port but alas someone  
waved a lucrative job offer in front of me first. :-)


But if anyone does undertake this task feel free to hit me up for  
questions.


I did download a pre-2.0 source snapshot of OpenOffice and ran my  1.1.x 
diffs against it... about 165 of ~200 patches broke, hopefully  most of 
those are trivial.


--
Michael Schubert  [EMAIL PROTECTED]

Maintaining badly written code is like trying to solve a crossword
puzzle set by someone who can't spell -- Jacob Kaplan-Moss







--
Todd Fries .. [EMAIL PROTECTED]

 _
| \  1.636.410.0632 (voice)
| Free Daemon Consulting, LLC \  1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com \  1.866.792.3418 (FAX)
| ..in support of free software solutions.  \  250797 (FWD)
| \
 \\

  37E7 D3EB 74D0 8D66 A68D  B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt



STLport.tgz
Description: application/tar-gz