Introduction

Note: This is a particularly complex section, covering a lot of intertwined concepts. You should read it straight through at least once before attempting anything on your own. It may help to read it multiple times, as certain concepts are mentioned long before they are fully explained.

A native module is a ferite module that contains native code to interface with the surrounding system. This can be of two main forms, a mix of both native code and ferite script [which is how the base modules for ferite are written] or they can be completely made up of native code.

The first type of native modules are written in ferite-c files, which are denoted by the .fec extension. When they are fully built, they can create either C libraries or shared objects that contain the native C code. In most cases, the .fec file is still necessary, as it may contain non-native code. These modules are partially auto-generated by using the builder command line tool [which comes with ferite] and are discussed from the next section onwards.

Modules that do not require the ferite-c file at runtime are dicussed later, after the builder tool and accessing the internals of ferite has been dicussed. This is due to the fact that they are harder to write and require knowledge of the ferite internals.