Building new releases of Neo/J from releases of OOo

Guest

Hi all,

I have a random (probably nonsensical) question: What are the primary difficulties in taking a developer snapshot of OOo and turning it into a snapshot release of Neo/J? Does this process entail hand-translating the C source code into Java? And if so, is there any path to automating this process, or at least a significant part?

I'm wondering about this because my primary computer is an OS X box, but the number of bugfixes between the OOo 1.1.x stable releases and the latest beta (which is 1.9m60 at the moment, I think) is enormous. This includes a number of what for me are show-stopping bugs (particularly in the Powerpoint/Impress module), to the point where I keep a copy of the latest developer release on my Win2K and Linux boxes at all times. Even the X11-based release for OS X is based on 1.1.2.

I remember seeing in a post somewhere in these forums that Patrick fixes many bugs in the process of rolling out each release of Neo/J -- I assume this is in addition to all the bugfixes incorporated into the OOo release on which it was based -- but is there any way at all to generate an OS X version from the once-every-three-weeks-or-so developer snapshots? (Of course, I realize any such thing would be extremely pre-alpha quality and accompanied by all sorts of disclaimers, but that's OK for me...)

Perhaps this question is better directed to the OOo-on-OSX forums?

In any case, thanks for all your hard work on Neo/J (I use it as my primary office app on a daily basis!).

Cheers,

Dave

pluby · The Architect Joined: Jun 16, 2003 Posts: 11949

ovvldc

pluby · The Architect Joined: Jun 16, 2003 Posts: 11949

Boukman · Pure-blooded Human Joined: Nov 16, 2004 Posts: 31

I was wondering what it takes to build NeoJ and hopefully play a little with the code. Are the build instructions on the NeoJ website still working?

Is there any way you can "download" the whole code beforehand? I've been toying with the idea of building NeoJ for a while, but 2 things were keeping me from doing it: 1) my HD was full and 2) I have a "slow" 128 kbps internet connection.

As for #1, I upgraded the HD in my PB to a 60 Gig, so I now have plenty of space, and as for #2, I might be able to either find a wifi "hot spot", or to "borrow" some bandwith from my company.

Can someone point me in the right direction? Thanks!

pluby · The Architect Joined: Jun 16, 2003 Posts: 11949

Yes, the build instructions are still current although I have heard reports that OOo won't build if you have installed the latest XCode tools on Panther. Other than that, the build should work as long as you follow the instructions exactly. However, don't be surprised if the OOo code doesn't build. Even though we are checking out a stable branch from OOo, changes may have been made to that branch since I or Ed last checked it out.

As for downloading the source, I don't think anyone has posted a tar.gz of that branch on the OOo website. No matter how you cut it, the OOo codebase is absolutely huge so you may want check out the Neo/J code (this should be very fast) and then start the Neo/J build (which checks out OOo) and just let it run in the background overnight. Even with my 384KB/s DSL connection, it still takes a few hours for OOo to checkout.

BTW, if the build breaks, we can't provide much help and you are on your own but you can search the dev@porting.openoffice.org mailing list archives to find potentially helpful ideas at http://porting.openoffice.org/servlets/SearchList?listName=dev.

Patrick

Patrick

Boukman · Pure-blooded Human Joined: Nov 16, 2004 Posts: 31

Patrick, I have found that Ximian does make tarballs of the OOo source (which can be found here), so now I was wondering 1) what branch should I download (1.1.2 or 1.1.3?) and 2) what changes do I need to make to the build process.

Thank you in advance!

OPENSTEP · Posted: Sat Nov 27, 2004 9:01 pm Post subject:

You also may want to take a look at the makefile for OO_CVSROOT. Though aside from OOo's anoncvs (which is usually down) I think there are few of us who have OOo CVS access.

ed

OPENSTEP · Posted: Sat Nov 27, 2004 9:03 pm Post subject:

Also of note is that OOo 2.0/680 does not successfully compile on Mac OS X X11. Neo/J assumes that there's a stable OOo foundation that can be used for its basis; without a compiling OOo Mac OS X X11, there can be no Neo/J Sad

ed

fridrich · Agent Joined: Sep 14, 2004 Posts: 10

Boukman · Pure-blooded Human Joined: Nov 16, 2004 Posts: 31

Hi all!

Thanks fridrich for your answer, however, it came in just a tad too late! I started building NeoJ with CVS already on Sunday!

I unfortunately have to report that I'm stuck now since the build process didn't complete. It looks like it was pretty far along though. Here's what it looks like on my terminal:

cd "dic" ; sh -e -c 'for i in `curl -L -l "http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries" | grep "\.zip<" | grep -v -- "-pack\.zip" | sed "s#<\/[aA]>.*\\$##" | sed "s#^.*>##"` ; do curl -L -O "http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries/$i" ; done'

Then there's a bunch of transfers completion, with the last transfer failing like this:

% Total % Received % Xferd Average Speed Time Curr.
Dload Upload Total Current Left Speed
50 1529k 50 773k 0 0 1221 0 0:21:22 0:10:48 0:10:33 1622
curl: (18) transfer closed with 774064 bytes remaining to read
make: *** [build.oo_download_dics] Error 18

So it looks like I'm at the point where the dictionaries are being downloaded from OOo ftp. I'll have a look at the makefile a bit later to try to figure at which point I am and if I can resume the process somehow, but if anyone has good suggestions, I'm willing to hear them!