Go to the first, previous, next, last section, table of contents.


A.2 Configuring - Selecting the proper Makefile for your Compiler

MsgEd TE does not provide a configure skript. It rather provides a set of different makefiles. You "configure" the source code by simply renaming the makefile of your choice to `makefile'. You have do to this in both the `smapi' and the `msged' directory. For instance, on OS/2 with IBM C, you would use:

[C:\COMPILE\SMAPI] copy makefile.ibo makefile
[C:\COMPILE\SMAPI] copy ..\msged\makefile.ibo ..\msged\makefile

while on Unix, you would use:

~/smapi $ cp makefile.unx makefile
~/smpai $ cp ../msged/makefile.unx ../msged/makefile

The following compilers and target operating systems are supported:

Makefile     | Platform                 
-------------+-----------------------------------------
makefile.bcd | DOS with Borland C++ 3.1 or Turbo C  
makefile.bco | OS/2 with Borland C 2.0
makefile.bcw | Windows 95/NT with Borland C++ 4.0
makefile.djg | DOS/386 with DJGPP GCC 2.7.2
makefile.emo | OS/2 with EMX 0.9c GCC 2.7.2
makefile.ibo | OS/2 with IBM CSET/2 or Visual Age C++
makefile.rxw | 95/NT with RSXNT + EMX GCC 2.7.2 
makefile.unx | Any UNIX, BSD or Linux with any compiler

The following makefiles are also provided, but they are not supported, either because I do not have the appropriate compilers or because I cannot give support for some special features they are using. I try to update these makefiles along with the others, but I cannot make any promises.

Makefile     | Platform
-------------+----------------------------------------------
makefile.bsd | FreeBSD with GCC; links the SMAPI dynamically
makefile.hco | OS/2 with Metware High C 
makefile.lnx | Linux with GCC; links the SMAPI dynamically
makefile.qcd | DOS with MS Quick C      
makefile.wcd | DOS with Watcom C     
makefile.wcw | NT with Watcom C
makefile.wco | OS/2 with Watcom C
makefile.wcx | DOS/386 with Watcom C

Special note: Linux and FreeBSD users should, for the first try, use `makefile.unx' rather than `makefile.lnx' resp. `makefile.bsd'. `makefile.unx' is idiot proof: it statically links the Smapi, and it works on any Unix-like system that has any half Posix compliant "cc" available.

The files `makefile.lnx' and `makefile.bsd' should only be used if you want to link the Smapi dynamically, and if you know what that means and what you are doing

If you are annoyed by the executable generated with `makefile.unx' annouces itself as `MsgEd/UNX' rather than `MsgEd/LNX', you can edit the UNAME preprocessor define in `makefile.unx'.


Go to the first, previous, next, last section, table of contents.