hnl_dk, tonyw & Siegel:
Perhaps we should organise ourselves wrt. extracting a list of dependencies for OOo?
A quick suggestion from my side is:
1) Take a couple of days to familiarise ourselves with the source tree. (Until tuesday?)
2) Divide the source into parts investigated by one person each.
3) Redo step 2 but with different persons for the source parts so every part gets at least two people examining it.
4) Merge our results and present them to the team.
How does that sound?
-Peter aka. Archprogrammer
Reality is for people who cannot face ScienceFiction. Only lefthanded people are in their right minds.
Hello Peter
Peter Bengtsson wrote at 14.01.2005 17:00:51:
hnl_dk, tonyw & Siegel:
Perhaps we should organise ourselves wrt. extracting a list of dependencies for OOo?
A quick suggestion from my side is:
- Take a couple of days to familiarise ourselves with the
source tree. (Until tuesday?)
Depends on how long it takes to update the cvstree, I'm still in progress of updating...man this is a REAL HUGE baby :)
Divide the source into parts investigated by one person each.
Redo step 2 but with different persons for the source parts
so every part gets at least two people examining it.
- Merge our results and present them to the team.
How does that sound?
Sounds good to me. However before I investigate the code I would like to have first a fully working self-build OO suite on my Linux box, just to be sure that everything is correct and in place. Hopefully the compile run does not take years to complete :)
Btw: http://tools.openoffice.org seems to be a vital resource for the building process.
Regards,
Sascha 'SieGeL' Pfalz wrote:
Hello Peter
Peter Bengtsson wrote at 14.01.2005 17:00:51:
hnl_dk, tonyw & Siegel:
Perhaps we should organise ourselves wrt. extracting a list of dependencies for OOo?
A quick suggestion from my side is:
- Take a couple of days to familiarise ourselves with the
source tree. (Until tuesday?)
Depends on how long it takes to update the cvstree, I'm still in progress of updating...man this is a REAL HUGE baby :)
I am at the moment installing GNU/Linux on the same disk as AmigaOS4... Could you please write the URL for the sources, as I didn't get it the other day.
Divide the source into parts investigated by one person each.
Redo step 2 but with different persons for the source parts
so every part gets at least two people examining it.
- Merge our results and present them to the team.
How does that sound?
Sounds good to me. However before I investigate the code I would like to have first a fully working self-build OO suite on my Linux box, just to be sure that everything is correct and in place. Hopefully the compile run does not take years to complete :)
IIRC did I read some place that it would take a bit more than a day... depending on how fast the system is :-o
Btw: http://tools.openoffice.org seems to be a vital resource for the building process.
very usefull :-D
Regards,
Hello Henning
Henning Nielsen Lund wrote at 16.01.2005 00:45:59:
[..]
Depends on how long it takes to update the cvstree, I'm still in progress of updating...man this is a REAL HUGE baby :)
I am at the moment installing GNU/Linux on the same disk as AmigaOS4... Could you please write the URL for the sources, as I didn't get it the other day.
Yep no problem: http://84.234.219.218/openoffice/
[..]
Sounds good to me. However before I investigate the code I would like to have first a fully working self-build OO suite on my Linux box, just to be sure that everything is correct and in place. Hopefully the compile run does not take years to complete :)
IIRC did I read some place that it would take a bit more than a day... depending on how fast the system is :-o
Well its a P3-550 with 512MB RAM...if this really take that long I will eventually switch to Windows/Cygwin environment, an Athlon XP 3000+ should crack this down much faster IMO :)
Btw: http://tools.openoffice.org seems to be a vital resource for the building process.
very usefull :-D
Yeah it gave me a fairly good start what actually all the directories mean inside the openoffice folder, and there are really plenty of them...i would say to get a list of dependencies we should focus mainly on the dmake makefiles, from what I have read the complete source is used for ALL platforms and only the makefiles are adapted to the target systems. The configure run seems to write down the appropiate files in an output tree, which is then used for compiling.
More details on that when I can finally start the build. Now going to bed.
Regards,
Sascha 'SieGeL' Pfalz wrote:
Hello Henning
Henning Nielsen Lund wrote at 16.01.2005 00:45:59:
[..]
Depends on how long it takes to update the cvstree, I'm still in progress of updating...man this is a REAL HUGE baby :)
I am at the moment installing GNU/Linux on the same disk as AmigaOS4... Could you please write the URL for the sources, as I didn't get it the other day.
Yep no problem: http://84.234.219.218/openoffice/
thanks :-)
[..]
Sounds good to me. However before I investigate the code I would like to have first a fully working self-build OO suite on my Linux box, just to be sure that everything is correct and in place. Hopefully the compile run does not take years to complete :)
IIRC did I read some place that it would take a bit more than a day... depending on how fast the system is :-o
Well its a P3-550 with 512MB RAM...if this really take that long I will eventually switch to Windows/Cygwin environment, an Athlon XP 3000+ should crack this down much faster IMO :)
You can see some info about build times here: http://porting.openoffice.org/freebsd/benchmark.html
Btw: http://tools.openoffice.org seems to be a vital resource for the building process.
very usefull :-D
Yeah it gave me a fairly good start what actually all the directories mean inside the openoffice folder, and there are really plenty of them...i would say to get a list of dependencies we should focus mainly on the dmake makefiles, from what I have read the complete source is used for ALL platforms and only the makefiles are adapted to the target systems. The configure run seems to write down the appropiate files in an output tree, which is then used for compiling.
More details on that when I can finally start the build. Now going to bed.
me too ;-) Good night :-)
Regards,
Sascha 'SieGeL' Pfalz wrote:
Hello Henning
Henning Nielsen Lund wrote at 16.01.2005 00:45:59:
[snip]
IIRC did I read some place that it would take a bit more than a day... depending on how fast the system is :-o
Well its a P3-550 with 512MB RAM...if this really take that long I will eventually switch to Windows/Cygwin environment, an Athlon XP 3000+ should crack this down much faster IMO :)
Building OOo from source was taking me somewhere over 12 hours on a dual P3 SCSI system (FreeBSD). I _think_ compile times for 'reasonable' x86 CPUs (Athlon 2GHZ equivalent or Pentium 2GHZ or higher) single CPU was still on the order of 8-24 hours IIRC. NOT a 'small compile' ;-)
Which Os you're building under, as well as amount of RAM, and more or at least as importantly, what else is running on your system during the build, will obviously affect this...
Scott
Btw: http://tools.openoffice.org seems to be a vital resource for the building process.
very usefull :-D
Yeah it gave me a fairly good start what actually all the directories mean inside the openoffice folder, and there are really plenty of them...i would say to get a list of dependencies we should focus mainly on the dmake makefiles, from what I have read the complete source is used for ALL platforms and only the makefiles are adapted to the target systems. The configure run seems to write down the appropiate files in an output tree, which is then used for compiling.
More details on that when I can finally start the build. Now going to bed.
Regards,
Hi Scott,
On 16/01/2005, you wrote:
Building OOo from source was taking me somewhere over 12 hours on a dual P3 SCSI system (FreeBSD). I _think_ compile times for 'reasonable' x86 CPUs (Athlon 2GHZ equivalent or Pentium 2GHZ or higher) single CPU was still on the order of 8-24 hours IIRC. NOT a 'small compile' ;-)
At this stage, perhaps just the configure phase is enough to get a picture of what we need, both on the build and on the target platform(s).
cheers
Hello Scott
Scott W wrote at 16.01.2005 03:09:03:
Sascha 'SieGeL' Pfalz wrote:
Hello Henning
Henning Nielsen Lund wrote at 16.01.2005 00:45:59:
[snip]
IIRC did I read some place that it would take a bit more than a day... depending on how fast the system is :-o
Well its a P3-550 with 512MB RAM...if this really take that long I will eventually switch to Windows/Cygwin environment, an Athlon XP 3000+ should crack this down much faster IMO :)
Building OOo from source was taking me somewhere over 12 hours on a dual P3 SCSI system (FreeBSD). I _think_ compile times for 'reasonable' x86 CPUs (Athlon 2GHZ equivalent or Pentium 2GHZ or higher) single CPU was still on the order of 8-24 hours IIRC. NOT a 'small compile' ;-)
Urgs for sure :)
Which Os you're building under, as well as amount of RAM, and more or at least as importantly, what else is running on your system during the build, will obviously affect this...
Well this is a SuSE 9.1 system which runs a fair amount of services already including Oracle. Anyway I plan to run the compile only once to see if all is working, no need to repeat that again and again :)
Regards,
Sascha 'SieGeL' Pfalz wrote:
I am at the moment installing GNU/Linux on the same disk as AmigaOS4... Could you please write the URL for the sources, as I didn't get it the other day.
Yep no problem: http://84.234.219.218/openoffice/
[..]
If anyone wants a copy of this I can send em a cd of it (it'll be out of date by the time you get it, but may be usefull for those with a lack of bandwidth), not too many though, it can get expensive.
Mark
Mark bond wrote:
Sascha 'SieGeL' Pfalz wrote:
I am at the moment installing GNU/Linux on the same disk as AmigaOS4... Could you please write the URL for the sources, as I didn't get it the other day.
Yep no problem: http://84.234.219.218/openoffice/
[..]
If anyone wants a copy of this I can send em a cd of it (it'll be out of date by the time you get it, but may be usefull for those with a lack of bandwidth), not too many though, it can get expensive.
wow what an offer :-D
I did get it yesterday, but thanks for the offer :-)
Mark
-
Henning Nielsen Lund -
Mark bond -
Peter Bengtsson -
Sascha 'SieGeL' Pfalz -
Scott W -
Tony Wyatt