Timothy Cameron wrote:

Hello Christophe

On 12/01/05, you wrote:

...

Hello,

I started collecting all the tools & libs already available to this wiki page:

http://amigaopenoffice.org/index.php?option=com_wikidoc&task=viewcontent&doc...

...

Kind regards

This is a good start (BTW, Davey, good job on the site/wiki!), but as this stands, it's difficult to tell: 1. Is this a clear cut dependency of OOo? Or just a possible useful tool? (Important IMHO) 2. Has it been tested to work? If so, on which platforms? A1/OS4, 68k only/3.X? Again, important, as some further work on some of the items listed may be needed. I actually think the mentioned page should be part of a larger 'OO Build Environment' page, which once finished, should document: 1. OOo dependencies for the AOS4 build environment (specific setup) 2. OOo dependencies for any other platforms supported (cross-compilation, OS3.9 if that's actually supported, etc) 3. SCM and defect tracking configuration 4. OOo source tree overview/conventions (can link to other docs) 5. Amiga OO specific changes or additional directories for base build environment (in other words, what is either being ported, as not everything should need to be, and what's being added) There's a bit more, but you get the point...if each of the tools had a uniform status and OSes for each, as they were tested and verified to either need more work or be good to use/completed, whomever was responsible could add the notation into the wiki page stating so.. Thanks, Scott

Hi, Scott W wrote:

while useful in it's own right, should be clearly marked as either a legacy doc (for example, glibc is not going to be used for AOS OOo port AFAIK....umm, and it isn't 'command line parsing', although it's possible they use GNU getopt functionality _from_ glibc..)

I assume they use getopt_long, which isn't part of the standard C library... clib2 has getopt...

, it shoudl clearly state these are the _LINUX_ dependencies rather than AOS', or be marked as: 'Linux': <dependency AOS: <replacement, equivalent, or porting status>

Good idea... Regards, -- Thomas Frieden <ThomasF@hyperion-entertainment.biz> Hyperion Entertainment - Naur dan i-deryg lhuin

Mark bond wrote:

Thomas Frieden wrote:

...

Hi,

Scott W wrote:

...

while useful in it's own right, should be clearly marked as either a legacy doc (for example, glibc is not going to be used for AOS OOo port AFAIK....umm, and it isn't 'command line parsing', although it's possible they use GNU getopt functionality _from_ glibc..)

I assume they use getopt_long, which isn't part of the standard C library... clib2 has getopt...

...

, it shoudl clearly state these are the _LINUX_ dependencies rather than AOS', or be marked as: 'Linux': <dependency AOS: <replacement, equivalent, or porting status>

Good idea...

It already does, in the paragraph at the top of the page it clearly states that these dependencies are for Linux (until someone made an AOS section at the bottom which appears to be almost a copy of the Linux version).

Mark

Yes, that would be me, _after_ sending the original comment. It wasn't meant to be an exact replacement, it was meant to be a checklist stating what would be used on AOS OOo, with replacements or comments about each being supported or not. I think it's worth leaving the original OO/Linux/other platform requirements as they are for comparison, and also to see what we're missing at a glance, as well as evolve into a specific set of build tools and dependencies, so people just popping in don't go insane wonder 'where's glibc for AOS' and the like. As mentioned, as soon as I have my uA1, if it's not already done, I'd be happy to go through each dependency and update the status, at least with respect to AOS4. If someone has a better suggestion on how to track 'what OO wants versus what we've got,' I'm all for it....but we've got to start somewhere, even if some of the content is a placeholder until more investigation can be done. Scott

Op 13-jan-05 om 08:37 heeft Ole-Egil Hvitmyren het volgende geschreven:

...

68k - 060 bin http://ftp.plig.org/pub/aminet/util/shell/csh550a_060.lha

src http://ftp.plig.org/pub/aminet/util/shell/csh550src.lha

The 68k & 68k - 060 both work fine on AOS4.0 Pre - 2, so I`ve included the 060 link, ixemul is NOT used at all.

Have you tried any test cases on it, or is this 100% guaranteed to be up to spec?

We also need a bourne compatible shell (/bin/sh) for the buildscripts in some of the dependencies. Just thought I'd mention it.

None of these things have been tested yet, for the bourne shell we could use 'sh' from GG: if/when the ixemil.lib & kernel update are available ---- Ochal Christophe Verantwoordelijke Technische Dienst Fem Computer Systems NV Dendermondsesteenweg 7 9300 Aalst Tel: 053/771816 Fax: 053/214628 Email: co@fem.be

Hello Henning On 12/01/2005, you wrote:

Christophe Ochal wrote:

...

Hello,

I started collecting all the tools & libs already available to this wiki page: http://amigaopenoffice.org/index.php?option=com_wikidoc&task=viewcontent&doc...

Kind regards

I have just build gettext-runtime-1.13.1, OOo does not use gettext, but some of its dependencies might. When I get the time, will I update it to the newest version.

Cool, keep us informed ;)

gettext-tools does use fork(), but it is only needed we we would change some of the po files. And can work with IXemul (at least on classic with gg).

Ok Regards -- Amon_Re Christophe Ochal Hoge Buizemont 168 9500 Geraardsbergen, Belgium Mobile: 0032 (0)479/46 45 74 http://www.kefren.be http://www.metalfest.be