[Oberon] Oberon program compilation, linking and execution on Windows or Linux.

Chris Burrows chris at cfbsoftware.com
Fri Jan 29 23:44:31 CET 2016


> -----Original Message-----
> From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of
> Srinivas Nayak
> Sent: Saturday, 30 January 2016 3:49 AM
> To: ETH Oberon and related systems
> Subject: [Oberon] Oberon program compilation, linking and execution
> on Windows or Linux.
> 
> Normally a C program when compiled, produces object file.
> Object file contains machine level code and symbol table.
> Object files (along with library object files) are linked using a
> linker to generate an executable file.
> Finally loader takes care of loading the shared libraries and
> executing the program.
> 
> How these things happen for Oberon language programs on Windows or
> Linux?
> Any document describes this in detail (mostly what happens after
> finishing typing a Oberon Program to program execution start)?
> 

Command execution and dynamic loading of native code on the Oberon Operating
System (both standalone and hosted on Windows, Unix, Linux etc.) is much
more granular and flexible than what you get with pre-linked executables
generated by the majority of conventional native code-generating development
systems. In Oberon all you have to do is compile the module (and possibly
other modules that IMPORT it if the interface has changed) to produce the
native code object file. The operating system takes care of the rest.

Read Sections 2.2.6 "Dynamic Loading", and 6.1 "Linking and Loading" in the
Project Oberon book. You can download a copy (e.g. Book Chapters 1-9) from
www.projectoberon.com

Regards,
Chris Burrows
CFB Software
http://www.astrobe.com






More information about the Oberon mailing list