| View previous topic :: View next topic |
| Author |
Message |
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
 Posted: Wed Nov 29, 2006 4:46 pm Post subject: If you are building Aqua Beta 3 from HEAD... |
|
...cd into your neojava directory and "cvs update -r NeoOffice-2_0_Aqua_Beta_3_branch". I have created the new NeoOffice-2_0_Aqua_Beta_3_branch branch so that I could continue to commit bug fixes for Aqua Beta 3 while, at the same time, I can commit my integration of Novell's VBA support and enhanced OpenSymbol font in HEAD.
Patrick |
|
| Back to top |
|
 |
jakeOSX
Ninja
Joined: Aug 12, 2003
Posts: 1373
|
| Posted: Thu Nov 30, 2006 4:39 am Post subject: |
|
and here i thought you were resting up for the holidays  |
|
| Back to top |
|
|
Samwise
Captain Naiobi
Joined: Apr 25, 2006
Posts: 2315
Location: Montpellier, France
|
| Posted: Thu Nov 30, 2006 6:46 am Post subject: |
|
| Answered my own question. Looks like it is time for me to keep two separate builds. |
|
| Back to top |
|
|
Samwise
Captain Naiobi
Joined: Apr 25, 2006
Posts: 2315
Location: Montpellier, France
|
| Posted: Thu Nov 30, 2006 9:42 am Post subject: |
|
Here's another question : why does the 10.2.8 SDK option need to be checked for compiling under Panther ?
Also, the readme hasn't been entirely updated : the Tiger section still has a link to darwinports.org (although it now redirects to macports.org, unlike darwinports.opendarwin.org), and there's a small typo two lines later : The "port" commis should probably read The "port" command is. I know, this really isn't important, but it could be corrected in the next readme. Or perhaps, since the readme is plain text, I could attach an updated readme (in cvs diff format) to a new bug in BugZilla ? |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Thu Nov 30, 2006 10:12 am Post subject: |
|
| Samwise wrote: | | Here's another question : why does the 10.2.8 SDK option need to be checked for compiling under Panther ? |
To compile the Mozilla code. OpenOffice.org has grown very dependent on the Mozilla code and to compile Mozilla on 10.3.x, their build instructions require the 10.2.8 SDK to be available. In other words, Mozilla has a very hairy build just like OpenOffice.org.
| Samwise wrote: | | Also, the readme hasn't been entirely updated : the Tiger section still has a link to darwinports.org (although it now redirects to macports.org, unlike darwinports.opendarwin.org), and there's a small typo two lines later : The "port" commis should probably read The "port" command is. I know, this really isn't important, but it could be corrected in the next readme. Or perhaps, since the readme is plain text, I could attach an updated readme (in cvs diff format) to a new bug in BugZilla ? |
I just committed the correct to HEAD. Just cvs update the README.txt file.
Patrick |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Thu Nov 30, 2006 11:15 am Post subject: |
|
FYI. If you are building HEAD, kill your build, "cvs update" in your neojava folder, and restart your build with "make build.oo_all".
I found one of my OOo patches didn't apply correctly so I fixed it.
Also, note that I say to invoke "make build.oo_all". This is because the NeoOffice custom code is still based on OOo 2.0.3 and so only the OOo portion of the build will work. My goal was to get the Mozilla and Novell code integrated into the OOo portion of our build in preparation for the upcoming OOo 2.1 release. I won't upgrade the NeoOffice custom code until after OOo 2.1 is officially released.
Patrick |
|
| Back to top |
|
|
Samwise
Captain Naiobi
Joined: Apr 25, 2006
Posts: 2315
Location: Montpellier, France
|
| Posted: Thu Nov 30, 2006 12:42 pm Post subject: |
|
| OK. So the resulting build won't be a working NeoOffice installation. I understand that you goal is to integrate the Mozilla and Novell code to the OOo portion of the build, but aside from making sure that the code will build, what will you do with this OOo 2.0.4 + Mozilla + VBA build ? |
|
| Back to top |
|
|
Samwise
Captain Naiobi
Joined: Apr 25, 2006
Posts: 2315
Location: Montpellier, France
|
| Posted: Thu Nov 30, 2006 12:51 pm Post subject: |
|
| pluby wrote: | I just committed the correct to HEAD. Just cvs update the README.txt file.
Patrick |
I'll have to wait until the next anoncvs sync though |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Thu Nov 30, 2006 1:10 pm Post subject: |
|
| Samwise wrote: | | OK. So the resulting build won't be a working NeoOffice installation. I understand that you goal is to integrate the Mozilla and Novell code to the OOo portion of the build, but aside from making sure that the code will build, what will you do with this OOo 2.0.4 + Mozilla + VBA build ? |
Not much. It basically is a transitional step to getting NeoOffice to use the OOo 2.1 code. Primarily, I wanted to verify that the Mozilla features and VBA features work properly. The VBA stuff lags behind the OOo builds so I had to use the OOo 2.0.4 for "phase 1".
BTW, if you want to test out the Mozilla or VBA support, you can run the OOo X11 that is built from a Terminal using the following commands:
1. cd into the neojava folder
2. Invoke the following command:
| Code: | | build/instsetoo_native/unxmacx[ip].pro/OpenOffice/install/en-US/staging/OpenOffice.org\ 2.0.app/Contents/MacOS/program/soffice |
Also, to use VBA commands in your OOo Basic script, you need to put the following line near the top of your script. By default, Excel files with VBA in them will automatically get this line added:
| Code: | | Option VBASupport 1 |
Patrick |
|
| Back to top |
|
|
Samwise
Captain Naiobi
Joined: Apr 25, 2006
Posts: 2315
Location: Montpellier, France
|
| Posted: Thu Nov 30, 2006 1:58 pm Post subject: |
|
I knew there had to be a way to run that build  |
|
| Back to top |
|
|
|
