OSLib and ELF

[Stewart Brodie]

John Tytgat <John.Tytgat at aaug.net> wrote:

> In message <gemini.jgcgwg01ih5uo06me.tony at vanderhoff.org>
>           Tony van der Hoff <tony at vanderhoff.org> wrote:
> 
> > On 10 Apr at 22:23 John Tytgat <John.Tytgat at aaug.net> wrote in message
> > <2f8889d14e.Jo at hobbes.bass-software.com>
> > >> In message <gemini.jgadf501hxveo03mn.tony at vanderhoff.org>
> >           Tony van der Hoff <tony at vanderhoff.org> wrote:
> > 
> > > An example : one problem I have with the current cross-compile
> > > facility of OSLib is that it doesn't allow parallel build, even worse,
> > > it breaks if you try this because not all dependencies are in place.
> > > I've looked a couple of times into fixing this and my opinion is that
> > > improving this could be seriously helped if the overall build
> > > structure could be changed as well.
> > > 
> > I'm not entirely sure I understand what you mean by parallel build,
> 
> The -j make option.  Basically doing more than one build step at the same
> time.  Keeping multicore/cpu happy.  It roughly cuts build times in 2 or
> 3.

Does that *really* matter all that much?  Last time I cross-compiled OSLib,
it only took 45 seconds or so for a full build from clean but, admittedly
that was probably 7-8 years ago, but I can't believe that it's got slower in
the meantime, has it?

I don't understand why you can't use the same Makefiles for cross-compiling
and native compiling - is it not just a case of a different CC and LIB
macros?   I thought I'd submitted all those changes to the project when I
did them, which would be at least 7-8 years ago now.  Perhaps it was just
the patches that meant you could compile up defmod itself for Linux or
Solaris. Sorry, if that's so - I no longer have any RISC OS source trees :-/


-- 
Stewart Brodie