[Oberon] A Linker.Mod for an almost self-hosted RISC Oberon

[eas lab]

OMG. Have I been sleeping ?
-> locate oot | grep V4 == ...
...
/usr/local/bin/V4/oberon-1.7.02/Source/BootLinker.Mod
/usr/local/bin/V4/oberon-1.7.02/System/BootLinker.Sym
/usr/local/bin/V4/oberon-1.7.02/System/BootLinker.Obj
/usr/local/bin/V4/oberon-1.7.02/LinuxOberon.Boot

Is this another demonstration of the power/effort-economy of <composition>?

After I've listened to it, I'll paste any key extracts.

== Chris Glur.


On 6/9/14, Bernhard Treutwein <Bernhard at wildwein.de> wrote:
>
> Am 4 Jun 2014 13:14:41 -0500 schrieb Aubrey.McIntosh at Alumni.UTexas.Net:
>
>  > The workstation versions of Oberon had a modified linker that
> produced boot files.
>  > From memory, I think this was called BootLinker.
>
> absolutely correct for the Unix versions of V4. The Bootlinker is/was a
> special
> program - a modified  linking loader - combining the modules of the
> "inner core"
> into a memory image, which could be loaded by a small C program (which also
> provided the interface to the basic libraries).
>
> See subdirectories of
> http://sourceforge.net/p/oberon/oberonv4/ci/master/tree/
>
> The Plugin-Version under Windows of later System 3 had a PELinker instead,
> which directly created Windows executables.
>
> --
>    Bernhard
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>