Compiling under Unix/Linux

[Tony van der Hoff]

On 9 Jan 2003, in message <80292db24b.philip at philipnet.com>,
Philip Ludlam <philip at philipnet.com> wrote:

> On 9 Jan, in message <7f8024b24b.Tony at mk-net.demon.co.uk>
>   Tony van der Hoff <tony at mk-net.demon.co.uk> wrote:
> 
[snip]
> 
> As StrongHelp is not available under Linux the process of creating a
> StrongHelp file/manual won't be easy. The simplest thing to do would
> be to create the directory structure and files that would go in it. A C
> program (to be written) could then take the root directory for this and
> create the manual from it.
> 
That's what the current tools BuildHelp and IndexHelp do - It's a long time
since we relied on StrongHelp itself. Touble is - as I admitted - they're
written for OSLib file system calls, these need translating to C.

> [snip: use native bison and rm]
> 
> >The only other tool - ReduceAOF - is probably no problem - I think it's
> >fully portable; it's a shame we don't have a proper, commented, source! 
> 
> Yes, after looking at the source I concluded that ReduceAOF was an
> appropriate name :-) 
> 
> [snip huge plans for OSLib]
> Might I add:
>  - taking out the way the source files are split into Computer, Core,
>    Macros, Toolbox, Types and User directories

Well, probably not. It's split that way to accommodate systems with less than
77 files per directory; for now this still has some legacy value. I've no
real problem doing it in the source; I don't think anyone would nowadays
build OSLib under such an archaic system, but the target headers in the deep
release lib must retain that structure. That in turn would be difficult to
maintain if the source lost its structure.

>  - having the ability to compile OSLib with gcc under RISC OS.
> 
Yes, I've never attempted it, but I was under the impression that it was OK.
In what way does it not work?

> >So, although Defmod works OK, there is quite a lot of peripheral tidying
> >up to be done, and that's why it isn't yet available. I believe it will be
> >worthwhile, if only in terms of time-saving during the build process.
> 
> Quite - I've never managed to build OSLib on my Risc PC yet - but it
> takes minutes on my Linux box :-).

A full build (including Help) takes 2 hours on a SARPC, over a 10B2 network!

-- 
Tony van der Hoff         | MailTo:tony at mk-net.demon.co.uk
                          | MailTo:avanderhoff at iee.org
Buckinghamshire, England  | http:www.mk-net.demon.co.uk