Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - If you are building NeoOffice Aqua Beta...
If you are building NeoOffice Aqua Beta...
 
   NeoOffice Forum Index -> NeoOffice Development
View previous topic :: View next topic  
Author Message
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Fri Jul 14, 2006 10:41 am    Post subject: If you are building NeoOffice Aqua Beta...

...note that after the next anoncvs update there will be a massive number of changes. None of these changes affect the OOo portion of the build, but I have added many new files (and a new module) in the NeoOffice portion of the build.

So, be sure to "cvs update -d" and watch for those files with an "M" or "C" status. Delete those and "cvs update -d" again. Also, after you cvs update be sure to rebuild all Neo modules that have updated files. Not all modules have changes, but a handful do.

Patrick
Back to top
Samwise
Captain Naiobi


Joined: Apr 25, 2006
Posts: 2315
Location: Montpellier, France

PostPosted: Fri Jul 14, 2006 10:48 am    Post subject:

Thanks a lot.
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Tue Jul 25, 2006 12:10 pm    Post subject:

In this afternoon's anoncvs sync (Pacfic time), I have made two build changes. Hopefully these will be the last build changes before the Aqua Beta EAP starts. Assuming you already have a Neo 2.0 Aqua Beta build, I recommend that you do the following steps:

1. rm -Rf both the build.neo_svtools_patch file and the entire svtools folder - this is necessary because I had to remove one file and add another in this module.

2. cvs update -d your workspace

3. Delete and build.neo_*_patch files for any modules that cvs has updated changes to

4. Invoke make

At this point, Ed and I will only be making very minor, low-risk bug fixes so any changes for the remainder of the week should be limited to only vcl and maybe svtools.

Patrick


Last edited by pluby on Tue Jul 25, 2006 12:55 pm; edited 1 time in total
Back to top
Samwise
Captain Naiobi


Joined: Apr 25, 2006
Posts: 2315
Location: Montpellier, France

PostPosted: Tue Jul 25, 2006 12:31 pm    Post subject:

Thanks again.
Back to top
Worthless Person
Guest





PostPosted: Tue Jul 25, 2006 6:57 pm    Post subject:

pluby wrote:
In this afternoon's anoncvs sync (Pacfic time), I have made two build changes. Hopefully these will be the last build changes before the Aqua Beta EAP starts. Assuming you already have a Neo 2.0 Aqua Beta build, I recommend that you do the following steps:

1. rm -Rf both the build.neo_svtools_patch file and the entire svtools folder - this is necessary because I had to remove one file and add another in this module.

2. cvs update -d your workspace

3. Delete and build.neo_*_patch files for any modules that cvs has updated changes to

4. Invoke make

At this point, Ed and I will only be making very minor, low-risk bug fixes so any changes for the remainder of the week should be limited to only vcl and maybe svtools.

Patrick


What is the CVS tag for the 2.0 Beta?

Thanks,
Worthless
Back to top
toonetown
Keymaker


Joined: Apr 21, 2006
Posts: 95
Location: Utah, USA

PostPosted: Tue Jul 25, 2006 7:05 pm    Post subject:

Worthless Person wrote:
What is the CVS tag for the 2.0 Beta?


I just built from HEAD, and it's pretty "aquafied"...

-Nathan
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Tue Jul 25, 2006 7:47 pm    Post subject:

Worthless Person wrote:
What is the CVS tag for the 2.0 Beta?


There isn't one yet as we are still working on last minute fixes. So, just use HEAD as the branch.

Patrick
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Fri Jul 28, 2006 6:15 pm    Post subject:

After a blizzard of debugging, Ed and I have fixed all of the known Aqua drawing bugs and so I have frozen the code for the NeoOffice 2.0 Aqua Beta release. If you want to build the code, I have tagged it with the NeoOffice-2_0_Aqua_Beta tag.

Patrick
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Fri Jul 28, 2006 7:48 pm    Post subject:

Oops. I had to rerun the anoncvs sync. That is now done and the Neo 2.0 Aqua Beta code is available from anoncvs.

Patrick
Back to top
Guest
Guest





PostPosted: Sat Jul 29, 2006 12:10 pm    Post subject:

Just a little question: Will Aqua Beta still be based on OOo 2.0.3 or will it be based on the current OOo 2.0.4?
Back to top
Guest






PostPosted: Sat Jul 29, 2006 12:22 pm    Post subject:

Guest wrote:
Just a little question: Will Aqua Beta still be based on OOo 2.0.3 or will it be based on the current OOo 2.0.4?


HAHAHA, I was one version number to high.... of course I meant:

Will Aqua Beta still be based on OOo 2.0.2 or will it be based on the current OOo 2.0.3?
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sat Jul 29, 2006 1:08 pm    Post subject:

Anonymous wrote:
Will Aqua Beta still be based on OOo 2.0.2 or will it be based on the current OOo 2.0.3?


Aqua Beta uses OOo 2.0.3 which is the latest release at this time available for OOo's official platforms: Windows, Linux, and Solaris.

BTW, the updated features page is here:

http://www.planamesa.com/neojava/en/earlyaccessfeatures.php

Patrick
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sat Jul 29, 2006 1:11 pm    Post subject:

Well, wouldn't you know. After I tagged the build, Ed found a crashing bug so I retagged a few files.

If you have already checked out the tag yesterday or earlier today *and* your build is still in the OOo phase of the build, you only need to cvs update -d your build and the changed files (in vcl, fpicker, and svtools) will get built properly without having to stop your build.

Patrick
Back to top
OPENSTEP
The One
The One


Joined: May 25, 2003
Posts: 4752
Location: Santa Barbara, CA

PostPosted: Sat Jul 29, 2006 3:04 pm    Post subject:

Special thanks to Patrick for being so responsive, and thanks to our great infrastructure for allowing it to happen! The crasher was bad since it could lead to an irrecoverable binary where after the app crashed it would crash again on next launch.

Take this as proof that either:

- I suck since I introduced the bug in the first place
- I rule since I found it before release.

ed

/sucks
//should've known better than to do last minute bugfixing
///does this make me megamaid?
Back to top
LemonAid
The Anomaly


Joined: Nov 21, 2005
Posts: 1285
Location: Witless Protection Program

PostPosted: Sat Jul 29, 2006 4:57 pm    Post subject:

pluby wrote:
BTW, the updated features page is here:
http://www.planamesa.com/neojava/en/earlyaccessfeatures.php

Patrick

Should this mention native File Picker? I would think that is different from "Integrated with Finder and Mail".

It's a GREAT feature and probably should have it's own bullet.

Philip ( T H R e e days Wink )
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Development All times are GMT - 7 Hours
Goto page 1, 2  Next
Page 1 of 2

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.