Porting from Unix platforms

Introduction

This article will cover the basic steps for porting programs written for the Unix platform.

Only command line program will be covered, since porting the X window interface is a second step. If you are working on a GUI program, consider using the EverBlue Project or the WxWidgets (formerly WxWindows) project. Remind that the steps described here, probably still apply to your project.

System requirements

The most common enviroment used for porting Unix programs, is the EMX/GCC compiler&tools. It is based on gcc 2.8.1 and provides most of the required tools.

A new enviroment actually coming up, is the Innotek gcc compiler, based on gcc 3.2.2 for libc 0.5 level, on gcc 3.3.5 for the libc 0.6 release (currently in alpha test, soon in beta test). This is an enviroment currently in developement, but I consider it the preferrable way for starting.

To create an EMX basic enviroment you need to download the following files:

• Runtimes for programs compiled with emx 0.9d(04)

• Files required for developing programs with emx (part 1)
• Files required for developing programs with emx (part 2)
• The GNU C compiler, the GNU debugger, and other tools (part 1)
• The GNU C compiler, the GNU debugger, and other tools (part 2)
• Additional files for GCC required for compiling C++ programs
• libg++ 2.8.1.1a
• emxgnu.inf (emxgnu.doc in OS/2 .inf format)
• gnudiff.zip GNU diff v2.7.1 file differencer
• gnufutil.zip GNU file utilities v3.13
• gnugrep.zip GNU grep/egrep/fgrep 2.0
• gnututil.zip GNU text utilities v1.19
• gnupatch.zip GNU patch v2.5
• GNU Make 3.81rc2
• A shell (e.g. pdksh)
• GNU awk 3.0.6
• GNU sed 3.0.2

For an advanced enviroment, you need also:

• Automake
• Autoconf

For using Innotek gcc (recommended):

• Innotek gcc 3.2.2 runtime
• GCC for OS/2 Beta 4
• GCC for OS/2 Beta 4 CSD1