Build(2)

BUILD

MicroEmacs 2025 may be compiled from the source files using the command shell build scripts build.sh (UNIX Bourne Shell) or build.bat (DOS/Windows). A default compile sequence may be achieved with a simple:

build.sh 

from the command line. The build script attempts to detect the host system and available compiler and build the editor.

The build script recognizes the following options:-

-32


Build 32 bit based program.

-64


Build 64 bit based program.

-a architecture


Specifics the target CPU chip or architecture, typically one of intel, arm, aarch or apple.

-C


Build clean. Delete all of the object files.

-D <define>[=<value>]


Sets build define <define> with value "<value>" or empty string if value not given.

-d


Build a debugging version, the output is to a platform specific debug build directory rather than a release one.

-h


Display a simple help page.

-l logfile


Redirect all compilation output to the logfile, this may not work on DOS or Windows systems.

-la logfile


Append all compilation output to the end of logfile, this may not work on DOS or Windows systems.

-m makefile


Build using the specified makefile. over-riding the auto system detect. The supplied makefiles include:-

• linuxgcc.mak Linux using GNU tools
• macoscc.mak macOS using Xcode command-line tools
• winmsvc.mak Windows using MS Visual C++
• winmingw.mak Windows using MinGW and GNU tools
• cygwingcc.mak Cygwin (on Windows) using GNU tools
• msyswingcc.mak MSYS (on Windows) using GNU tools
• dosdj2.mak Microsoft DOS using djgpp version 2.

The following makefiles are also included for historical record, but will likely need significant updating to make them work with the current release:

• aix4cc.mak IBM AIX 4.x native
• aix4gcc.mak IBM AIX 4.x using GNU tools
• aix5cc.mak IBM AIX 5.x native
• aix5gcc.mak IBM AIX 5.x using GNU tools
• darwingcc.mak Apple Darwin (console and X-Windows)
• dosdj1.mak Microsoft DOS build using djgpp version 1
• freebsdcc.mak Free BSD native
• freebsdgcc.mak Free BSD using GNU tools
• hpux9cc.mak HP-UX 9.x native
• hpux9gcc.mak HP-UX 9.x using GNU tools
• hpux10cc.mak HP-UX 10.x native
• hpux10gcc.mak HP-UX 10.x using GNU tools
• hpux11cc.mak HP-UX 11.x native
• hpux11gcc.mak HP-UX 11.x using GNU tools
• irix5cc.mak Silicon Graphics IRIX 5.x native
• irix5gcc.mak Silicon Graphics IRIX 5.x using GNU tools
• irix6cc.mak Silicon Graphics IRIX 6.x native
• irix6gcc.mak Silicon Graphics IRIX 6.x using GNU tools
• openbsdgcc.mak OpenBSD using GNU tools
• openstepcc.mak Openstep 4.2 on NeXTstep (BSD 4.3)
• osf1gcc.mak OSF1 using GNU tools
• sunos5cc.mak Sun Solaris 5.6/7/8/9/10 native
• sunos5gcc.mak Sun Solaris 5.5/6/7/8/9/10 using GNU tools
• sunosx86gcc.mak Sun Solarais 2.6/7/8/9/10 (Intel) using GNU tools.
• zaurusgcc.mak Zauras palm using GNU tools

-ne


Build NanoEmacs (a cut down version aimed as a vi replacement), the output is ne.

-S


Build spotless. Deletes all of the object files and any backup files, tag files etc.

-t type


Set the build type, where type can be one of the following:

-v <variable>=<value>


Build with the given makefile <variable> override, e.g. -v OPENSSLPATH=<path-to-openssl-install>

• c Build a console only version (i.e. no window support), the output is mec.
• w Build a windows only version (i.e. no console support), the output is mew.
• cw Build a version which supports both console and windows, the output is mecw.

Makefiles

The supplied makefiles are provided in two forms:-

• *gcc.mak - GNU make, using gcc.
• *cc.mak - Native make, consistent with the compiler and platform.

The makefiles are supplied with the following targets:-

• all - Default build.
• clean - Removes intermediate files.
• spotless - Removes intermediate files and any backup files.
• me - Builds the default MicroEmacs executable.
• med - Builds a debugging version.
• mec - Builds a console only version.
• mew - Builds a windows only version.
• mecw - Builds a version which supports both console and windows.
• ne - Builds NanoEmacs executable.

WINDOWS ENVIRONMENT

The Windows environment is a little more difficult than UNIX because it does not have a good native command line environment. There are two Microsoft Developer options for building. If you have not purchased MS-DEV then use the FREE Borland compiler which runs on the command line.

MinGW Build

A collection of freely available and freely distributable Windows specific header files and import libraries combined with GNU toolsets that allow one to produce native Windows programs that do not rely on any 3rd-party C runtime DLLs. Available from http://www.mingw.org, mingw allows a Microsoft Windows version MicroEmacs to bu built and maintained.

MS-Dev GUI Build

MicroEmacs is supplied with a MS-Dev 6.x project for building. This has only been set up for debugging and has limited build options, it will also produce a large executable image. The MS-Windows images shipped by JASSPA are built using the command line build environment which is detailed in a later section.

MS-Dev Command Line Build

The command line build with MS-Dev is a little messy to set up, in the following sections we discuss MS-Dev 6.x under Windows 2000. There will be differences with different operating systems versions, different install paths and different versions of the MS-Dev toolkit. Use the following information as an outline ONLY, JASSPA will not take responsibility for the configuration of the command line environment, if in doubt then use the GUI builder.

To run nmake(1) from a DOS box then the MS-Dev compiler tools must be available in the command path. The MS-Dev kit V6.x is supplied with the necessary file to set up the path which is called VCVARS32.BAT and is typically located in directory:

C:\Program Files\Microsoft Visual Studio\VC98\Bin 

This should be run first and then the command line make files may be run using nmake i.e. to build ME:-

nmake -f win32v6.mak me 

To build NE:-

nmake -f win32v6.mak ne 

To clean up after:-

nmake -f spotless 

If you are going to perform a lot of command line building then it is easier to set up the environment and not have to run VCVARS32.BAT every time you compile.

You can add the variables to your environment, you will need to expand the VCVARS32.BAT script and then add the results. The following example is for MS-Dev 6.0 under W2K, the settings will differ depending on what O/S variant you are running and where you have installed software. The following ONLY serves as an example, you need to tailor for your installation.

• To set up the variables then Start -> Settings -> Control Panel which displays the Control Panel items.
• Select System -> Advanced -> Environment variables
• In User Variables for <User> then New... or Edit... the PATH variable. Add the command line tools execution paths to the environment variable, this will be something like the following (but without newlines):-

  Variable Name:  PATH 
  Variable Value: %PATH%; 
                  C:\PROGRA~1\MICROS~3\Common\msdev98\BIN; 
                  C:\PROGRA~1\MICROS~3\VC98\BIN; 
                  C:\PROGRA~1\MICROS~3\Common\TOOLS\WINNT; 
                  C:\PROGRA~1\MICROS~3\Common\TOOLS; 
  

  Similarly add the INCLUDE variable:-

  Variable Name:  INCLUDE 
  Variable Value: C:\PROGRA~1\MICROS~3\VC98\ATL\INCLUDE; 
                  C:\PROGRA~1\MICROS~3\VC98\INCLUDE; 
                  C:\PROGRA~1\MICROS~3\VC98\MFC\INCLUDE; 
                  %INCLUDE% 
  

  Similarly add the LIB variable:-

  Variable Name:  LIB 
  Variable Value: C:\PROGRA~1\MICROS~3\VC98\LIB; 
                  C:\PROGRA~1\MICROS~3\VC98\MFC\LIB; 
                  %LIB% 
  

  Accept the entries and close down the dialog. Start a new DOS command line and the variables should be set up ready for the build.

NOTES

Other UNIX ports should be fairly easy from the base set of ported platforms. If any new platform ports are performed by individuals then please submit the makefiles and any source changes back to JASSPA - see Contact Information.

(c) Copyright JASSPA 2025
Last Modified: 2025/08/28
Generated On: 2025/09/29