MorphOS API and Its Organization

Grzegorz Kraszewski

An Application Programmer Interface of an operating system consists of thousands of functions usually. MorphOS is no exception here. Its kernel is not monolithic however. The API is functionally (and physically) divided into libraries. Only a few largest libraries contain more than 50 functions. A core set of most important libraries is contained in the system boot image. The rest is placed on the system partition in MOSSYS:Libs (libraries delivered with the system) and SYS:Libs (third party libraries) directories. Disk based libraries are loaded on demand. All these libraries are shared, it means all processes using a library execute the same code loaded to memory once.

Libraries Overview

MorphOS comes with over 100 different libraries. Not all of them are listed below, just the most common ones. Browse the system autodocs in the SDK for more.

• exec.library, the master one. This is the system core, responsible for processes scheduling, control and creation, communication between processes, memory management, managing other libraries and overall system control. This is the only library which is always opened and cannot be closed.

• dos.library, responsible for file and console input/output. Provides interface to advanced filesystem functions (like scanning directories for example). Cooperates with exec.library in process creation. Delivers basic system time services.

• graphics.library, is responsible for low-level graphics functions like drawing pixels and other primitives, copying rectangular blocks of display, scrolling etc. Many programs do not use it directly.

• intuition.library, delivers an intermediate level graphics interface objects like screens and windows. Interfaces to user input devices (mouse and keyboard to name a few). Provides very basic user controls (gadgets). Provides also BOOPSI (Basic Object Oriented System for Intuition), a language independent object oriented programming framework, used commonly by other components.

• muimaster.library, the main interface to MUI (Magic User Interface), which is the MorphOS high level GUI toolkit. Provides complete, object oriented framework (based on BOOPSI) for GUI driven applications.

• locale.library, is responsible for system and applications internationalization. This simple yet powerful subsystem allows for supporting multiple language versions of program with single executable, also provides localization data such as date format, local currency, timezone, number grouping and more.

• bsdsocket.library is an interface for TCP/IP networking, compatible with BSD sockets. What is unusal with this library, it is neither built into kernel, nor placed on disk. The TCP/IP stack creates it in memory dynamically.

How to Use a Library in an Application

In typical cases it is pretty automatic. The only thing which has to be done is including the main library header file, which is <proto/[libname].h>, for example <proto/exec.h>, <proto/muimaster.h> and so on. Library opening and closing is handled automatically by the startup code provided by either libnix or ixemul.library. Then one can just use functions from the library.

A few big libraries have separate subdirectories in the system include tree. Examples of such libraries are exec.library, dos.library or graphics.library. Header files in these directories contain definitions of constants, data structures, attributes etc. used by the library, divided by functionality. Including of these headers depends on functions used in the application, for example to use exec.library memory allocation functions one has to include <exec/memory.h> header.

Some libraries prefer to have one single header file in libraries directory. Examples are <libraries/locale.h> or <libraries/mui.h> (the latest is some deviation from the naming rule). This single header may be automatically included from proto file or not.

There are a few cases, where automatic library handling does not work, or cannot be used.

• Third party libraries. Most of them are not included in the autoopen feature.
• Custom startup code (linking with −nostartfiles).
• Opening libraries in a subprocess.
• Dynamic on-demand library opening.

In these cases libraries have to be handled manually.

Manual Library Opening and Closing

While not as comfortable as automatic handling, manual opening and closing of libraries is not very complicated. A library base variable has to be declared, then two functions from exec.library: OpenLibrary() and CloseLibrary() have to be used.