As we have seen throughout this book, porting is a complex but largely procedural process. Like this book, the process can be conveniently split into three parts:

• Knowledge of the platform you are porting to

• Knowledge of the functions and libraries supported by the target platform

• Knowledge of the tools, techniques, and processes used to write application software

Knowing about the platform you are porting to is critical. You need to identify the abilities of the platform, what tools are available that could make your life easier, and the layout of the new operating system so you can configure the application. On the BeOS, it is largely UNIX, or more correctly POSIX, in nature, and that makes porting most application software easier. Many packages have already been ported to UNIX/POSIX platforms, and so not only the layout but also many of the tools available will be familiar to you.

The most important thing to remember on the BeOS is that the layout, although similar, is very different from most UNIX variants, especially when it comes to the installation directories. It is also worth taking the time to find the tools, especially editors, that you are accustomed to using. Although the BeOS comes with most of the desired tools, some, such as your favorite editor, will need to be sourced from the various archives.

The second part of the porting process is the most complex and the most time consuming. The process follows a simple sequence:

1. Configure the application for the...