Porting from Unix platforms: Difference between revisions
| Line 46: | Line 46: | ||
Since you can use GNU utilities with different enviroments, I suggest to put EMX core files into a different directory tree. So you can use the utilities and other tools with Innotek gcc without too much trouble. | Since you can use GNU utilities with different enviroments, I suggest to put EMX core files into a different directory tree. So you can use the utilities and other tools with Innotek gcc without too much trouble. | ||
== Getting the code == | == Getting the source code == | ||
First step is to get the program source code. I can't tell you where to find it, but SourgeForge is a good place for starting :-) | First step is to get the program source code. I can't tell you where to find it, but SourgeForge is a good place for starting :-) | ||
Revision as of 13:34, 20 November 2004
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:
- 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
- GNU tar
- gzip 1.2.4
For an advanced enviroment, you need also:
- Automake
- Autoconf
For using Innotek gcc (recommended), get also:
Get the above packages and install following the included instructions. I will add a scheme here sometimes. Since you can use GNU utilities with different enviroments, I suggest to put EMX core files into a different directory tree. So you can use the utilities and other tools with Innotek gcc without too much trouble.
Getting the source code
First step is to get the program source code. I can't tell you where to find it, but SourgeForge is a good place for starting :-)
Usually source code comes as a 'tarball': that means all files are packed into a single file with tar (extension .tar) and most of the times also compressed (extension .tar.gz).
Untar the tarball with 'tar xzf place_here_my_tar.gz' and you will get all the sources extracted into a subdirectory (usually a tar file doesn't write files to the current directory).
If someone worked on the same program in the past, you can review the old work and use the old patches with your version. Keep in mind that old patches cannot always be applied to current source code, so a manual review is better in such cases.