User`s guide

KwikNet System Construction

DAK

111

3.5 Linking the Application

To add KwikNet to your application, you must include the KwikNet Library module

KNnnnIP.A in your link specification. Note that library file extensions may be .A or .LIB

or some other extension dictated by the toolset which you are using.

You must also include the object module for your device driver, say DDRIVER.O, and your

KwikNet board support module, say KN_BOARD.O, in your link specification. Note that

object file extensions may be

.O or .OBJ or some other extension dictated by the toolset

which you are using.

The device driver object module(s) and the board support object module should be

included together with all of your other application specific object modules. The

KwikNet

Library should precede the AMX or RT/OS libraries in the link sequence.

Although every effort has been made to ensure that each module in the KwikNet Library

contains only forward references to other modules in the library, the goal has proved

impossible to attain. Hence, some library modules do include backward references. This

characteristic requires that the libraries be searched recursively until all resolvable

references have been satisfied. Most linkers will meet this requirement. If yours does

not, you will be forced to include the KwikNet Library more than once in your link

specification.

If you are using KwikNet with AMX, there is little difference in linking an AMX

application with or without KwikNet. Instructions for linking an AMX system are

provided in the toolset specific chapters of the AMX Tool Guide.