ok, so at http://amigaopenoffice.org/index.php?option=com_wikidoc&task=viewcontent... there's a list of some tools, with links to each. Besides thinking they're now mentioned in all 3 wiki pages ( ;-) ), I have the following questions:
1. GCC installer- this is for gcc v2.95-3.4 for AOS3. It's generally a _bad_ thing to try to compile with multiple versions of gcc, and 2.95 is pretty long in the tooth. So: a. Do we have a confirmed gcc/g++ version for: AOS3.X? AOS4/PPC? Links to either?
2. Boost library- I haven't looked at this much, just their home page briefly, but it looks like a C++ utility library for the most part. There may be some investigation needed with respect to using this in code going back to OOo ultimately. I'm also not sure if anyone's determined if this is going to buy us anything (although likely no idea yet).
3. JPEG and zlib libs- what are the min required versions for OOo?
4. tcsh and csh ports- a. are these both 68k ports, or buildable for PPC and AOS4? b. If either one is 'less complete' that the other, it's possible to have buildscripts work on one and not the other. it could be in our best interest to choose one or the other and make that the 'golden standard' for the actual build environment. Anyone?
Thanks,
Scott
Op 13-jan-05 om 08:48 heeft Scott Wegener het volgende geschreven:
ok, so at http://amigaopenoffice.org/index.php? option=com_wikidoc&task=viewcontent&docid=5&Itemid=27&sid=7&cid=7 there's a list of some tools, with links to each. Besides thinking they're now mentioned in all 3 wiki pages ( ;-) ), I have the following questions:
- GCC installer- this is for gcc v2.95-3.4 for AOS3.
It's generally a _bad_ thing to try to compile with multiple versions of gcc, and 2.95 is pretty long in the tooth. So: a. Do we have a confirmed gcc/g++ version for: AOS3.X? AOS4/PPC? Links to either?
There is supposed to be GCC 3.4 for classic systems, GCC 3.4 comes with the OS4 SDK, and is also available for linuxPPC
- Boost library- I haven't looked at this much, just their home page
briefly, but it looks like a C++ utility library for the most part. There may be some investigation needed with respect to using this in code going back to OOo ultimately. I'm also not sure if anyone's determined if this is going to buy us anything (although likely no idea yet).
Unknown at this time, it's just there "in case of"
- JPEG and zlib libs- what are the min required versions for OOo?
Don't know by heart, but it was mentioned in the wiki (at work atm)
- tcsh and csh ports-
a. are these both 68k ports, or buildable for PPC and AOS4?
They are 68k, untested afaik on OS4
b. If either one is 'less complete' that the other, it's possible to have buildscripts work on one and not the other. it could be in our best interest to choose one or the other and make that the 'golden standard' for the actual build environment. Anyone?
These need further testing, first i'd like to have a full list of dependencies (runtime & build deps)
---- Amon_Re Ochal Christophe Webmaster for: http://www.kefren.be http://www.metalfest.be http://amigadev.amigaworld.net
- JPEG and zlib libs- what are the min required versions for OOo?
Don't know by heart, but it was mentioned in the wiki (at work atm)
The jpeg library is 6b (the correct version) the zlib is 1.2.1 which is higher than the required version. I checked this before adding them on the dependencies pages.
Mark
Hi,
Ochal Christophe wrote:
- JPEG and zlib libs- what are the min required versions for OOo?
Don't know by heart, but it was mentioned in the wiki (at work atm)
No matter what, these libraries always compile out of the box with no changes in the code, so it's to be considered absolutely minor...
- tcsh and csh ports-
a. are these both 68k ports, or buildable for PPC and AOS4?
They are 68k, untested afaik on OS4
Since csh source code is available, it's a good idea to try to compile it...
Regards,
Op 13-jan-05 om 10:59 heeft Thomas Frieden het volgende geschreven:
Since csh source code is available, it's a good idea to try to compile it...
I don't have an A1 yet ;)
---- Amon_Re Ochal Christophe Webmaster for: http://www.kefren.be http://www.metalfest.be http://amigadev.amigaworld.net
Hi,
Ochal Christophe wrote:
Since csh source code is available, it's a good idea to try to compile it...
I don't have an A1 yet ;)
I'll give it a spin if I find the time today...
Regards,
Thomas Frieden wrote:
Hi,
Ochal Christophe wrote:
Since csh source code is available, it's a good idea to try to compile it...
I don't have an A1 yet ;)
I'll give it a spin if I find the time today...
Regards,
Someone could do with producing a guide on coverting SAS makefiles to gcc makefiles.
Mark
Op 13-jan-05 om 12:03 heeft Martin Merz het volgende geschreven:
Hi Amon_Re,
I don't have an A1 yet ;)
Just to make you a little jealousy: I ordered my A1 five minutes ago!
Bah, i'll probably have one next month :)
---- Ochal Christophe Verantwoordelijke Technische Dienst Fem Computer Systems NV Dendermondsesteenweg 7 9300 Aalst Tel: 053/771816 Fax: 053/214628 Email: co@fem.be
Hi Scott,
On 13/01/2005, you wrote:
[...]
- tcsh and csh ports-
a. are these both 68k ports, or buildable for PPC and AOS4? b. If either one is 'less complete' that the other, it's possible to have buildscripts work on one and not the other. it could be in our best interest to choose one or the other and make that the 'golden standard' for the actual build environment. Anyone?
I'm still reading the OOo site, and haven't downloaded anything to check. However, I expect that OOo will be like Kaffe, Ada or any other big OS project - it will depend heavily on automake, libtool and other tools that in turn depend on a Bourne-compatible shell. I've only used pdksh with GG on OS3.9, I was not able to compile bash on my system. Tools may have changed since 2003, but if we do not have sh or bash, we are in for a lot of script re-writing before we will be able to build on a target system (A1).
In order to make our port "just another" platform that can be added to the source distribution tree, we will have to port the tools eventually, rather that adapt the scripts to suit our existing tools.
If we go the route of cross-compiling first and building the native tools as required, we will have more time to port these tools.
cheers
Tony Wyatt wrote:
Hi Scott,
On 13/01/2005, you wrote:
[...]
- tcsh and csh ports- a. are these both 68k ports, or buildable
for PPC and AOS4? b. If either one is 'less complete' that the other, it's possible to have buildscripts work on one and not the other. it could be in our best interest to choose one or the other and make that the 'golden standard' for the actual build environment. Anyone?
I'm still reading the OOo site, and haven't downloaded anything to check. However, I expect that OOo will be like Kaffe, Ada or any other big OS project - it will depend heavily on automake, libtool and other tools that in turn depend on a Bourne-compatible shell. I've only used pdksh with GG on OS3.9, I was not able to compile bash on my system. Tools may have changed since 2003, but if we do not have sh or bash, we are in for a lot of script re-writing before we will be able to build on a target system (A1).
OO.org uses C shell build scripts, instead of or in addition to bourne shell build scripts. As we've discussed here countless times already.
Ole-Egil
On 2005-01-13, Tony Wyatt wrote:
<SNIP>
changed since 2003, but if we do not have sh or bash, we are in for a lot of script re-writing before we will be able to build on a target system (A1).
In order to make our port "just another" platform that can be added to the source distribution tree, we will have to port the tools eventually, rather that adapt the scripts to suit our existing tools.
Not necessarily. If we need to rewrite enough of the scripts, it might be an idea to rewrite them in something which is already available and used (e.g. Python). This could make the change a candidate for inclusion into the main trunk of OOo and not just "out port".
At least as long as we do not _add_ dependencies.
If we go the route of cross-compiling first and building the native tools as required, we will have more time to port these tools.
This might be a good idea for the OOo source tree. At the very least, we should have someone compile it under e.g. Linux or Solaris so that we have a reference-build to look at.
-Peter aka. Archprogrammer
Reality is for people who cannot face ScienceFiction. Only lefthanded people are in their right minds.
Hi,
Scott Wegener wrote:
- GCC installer- this is for gcc v2.95-3.4 for AOS3.
It's generally a _bad_ thing to try to compile with multiple versions of gcc, and 2.95 is pretty long in the tooth. So: a. Do we have a confirmed gcc/g++ version for: AOS3.X? AOS4/PPC? Links to either?
I'd like to mention that we dropped support for gcc 295.3 on OS4, and the compiler version isn't maintained anymore nor updated, so it's missing the latest additions. On OS4, there's not really any alternative to 3.4.x
Regards,
Scott Wegener wrote:
a. Do we have a confirmed gcc/g++ version for: AOS3.X? AOS4/PPC? Links to either?
Just added a link to the 68k Geek Gadgets 3.4 compiler to the wiki.
Regards,