Skip to content

Commit 267753d

Browse files
ipstoneipstone
committed
0 parents  commit 267753d

File tree

171 files changed

+108213
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

171 files changed

+108213
-0
lines changed

‎COPYING

+340
Large diffs are not rendered by default.

‎build.txt

+210
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,210 @@
1+
2+
3+
4+
Build(2) microemacs Build(2)
5+
6+
7+
8+
9+
BUILD
10+
MicroEmacs 2009 may be compiled from the source files using the command
11+
shell build scripts build (UNIX Bourne Shell) or build.bat (DOS/Windows).
12+
A default compile sequence may be achieved with a simple:
13+
14+
build
15+
16+
from the command line. The build script attempts to detect the host system
17+
and available compiler and build the editor.
18+
19+
The build script recognizes the following options:-
20+
21+
-C Build clean. Delete all of the object files.
22+
23+
-d Build a debugging version, the output is med (or med32 for 32-bit
24+
Windows versions).
25+
26+
-h Display a simple help page
27+
28+
-l logfile
29+
Redirect all compilation output to the logfile, this may not work on
30+
DOS or Windows systems.
31+
32+
-la logfile
33+
Append all compilation output to the end of logfile, this may not
34+
work on DOS or Windows systems.
35+
36+
-m makefile
37+
Build using the specified makefile. over-riding the auto system
38+
detect. The supplied makefiles include:-
39+
40+
* aix4.mak IBM AIX 4.x native.
41+
* aix5.mak IBM AIX 5.x native.
42+
* aix4.gmk IBM AIX 4.x using GNU tools.
43+
* aix5.gmk IBM AIX 5.x using GNU tools.
44+
* cygwin.gmk Cygwin using GNU tools under Windows.
45+
* darwin.gmk Apple Darwin (console and X-Windows).
46+
* dosdj1.mak Microsoft DOS build using djgpp version 1.
47+
* dosdj2.mak Microsoft DOS build using djgpp version 2.
48+
* freebsd.gmk Free BSD using GNU tools.
49+
* hpux9.gmk HP-UX 9.x using GNU tools.
50+
* hpux9.mak HP-UX 9.x native
51+
* hpux10.gmk HP-UX 10.x using GNU tools.
52+
* hpux10.mak HP-UX 10.x native
53+
* hpux11.gmk HP-UX 11.x using GNU tools.
54+
* hpux11.mak HP-UX 11.x native
55+
* irix5.gmk Silicon Graphics IRIX 5.x using GNU tools
56+
* irix5.mak Silicon Graphics IRIX 5.x native
57+
* irix6.gmk Silicon Graphics IRIX 6.x using GNU tools
58+
* irix6.mak Silicon Graphics IRIX 6.x native
59+
* linux2.gmk Linux 2.2/4 kernels using GNU tools
60+
* linux26.gmk Linux 2.6 kernels using GNU tools
61+
* mingw.gmk minGW http://www.MinGW.org using GNU tools.
62+
* osf1.gmk OSF1 using GNU tools.
63+
* openbsd.gmk OpenBSD using GNU tools.
64+
* openstep.mak Openstep 4.2 on NeXTstep (BSD 4.3).
65+
* sunos5.gmak Sun Solaris 5.5/6/7/8/9/10 using GNU tools
66+
* sunos5.mak Sun Solaris 5.6/7/8/9/10 native
67+
* sunosx86.gmk Sun Solarais 2.6/7/8/9/10 (Intel) using GNU tools.
68+
* win32bc.mak Borland C, 32-bit Windows version.
69+
* win32b55.mak Borland C 5.5, 32-bit Windows version (Free
70+
compiler).
71+
* win32sv2.mak Microsoft Developer v2.x, Win32s (for Win 3.xx)
72+
* win32sv4.mak Microsoft Developer v4.2, Win32s (for Win 3.xx)
73+
* win32v2.mak Microsoft Developer v2.x, 32-bit Windows.
74+
* win32v5.mak Microsoft Developer v5.x, 32-bit Windows.
75+
* win32v6.mak Microsoft Developer v6.x, 32-bit Windows.
76+
* zaurus.gmk Zauras palm using GNU tools.
77+
78+
-ne Build NanoEmacs (a cut down version aimed as a vi replacement), the
79+
output is ne (or ned32 for 32-bit Windows versions).
80+
81+
-S Build spotless. Deletes all of the object files and any backup files,
82+
tag files etc.
83+
84+
-t type
85+
Set the build type, where type can be one of the following:
86+
87+
* c Build a console only version (i.e. no window support), the
88+
output is mec (or mec32 on Windows).
89+
* w Build a windows only version (i.e. no console support), the
90+
output is mew (or mew32 on Windows).
91+
* cw Build a version which supports both console and windows, the
92+
output is mecw (or mecw32 on Windows).
93+
94+
Makefiles
95+
The supplied makefiles are provided in two forms:-
96+
97+
* .gmk - GNU make, using gcc.
98+
* .mak - Native make, consistent with the compiler and platform.
99+
100+
The makefiles are supplied with the following targets:-
101+
102+
* all - Default build.
103+
* clean - Removes intermediate files.
104+
* spotless - Removes intermediate files and any backup files.
105+
* me - Builds the default MicroEmacs executable.
106+
* med - Builds a debugging version.
107+
* mec - Builds a console only version.
108+
* mew - Builds a windows only version.
109+
* mecw - Builds a version which supports both console and windows.
110+
* ne - Builds NanoEmacs executable.
111+
112+
WINDOWS ENVIRONMENT
113+
The Windows environment is a little more difficult than UNIX because it
114+
does not have a good native command line environment. There are two
115+
Microsoft Developer options for building. If you have not purchased MS-DEV
116+
then use the FREE Borland compiler which runs on the command line.
117+
118+
MinGW Build
119+
A collection of freely available and freely distributable Windows specific
120+
header files and import libraries combined with GNU toolsets that allow
121+
one to produce native Windows programs that do not rely on any 3rd-party C
122+
runtime DLLs. Available from http://www.mingw.org, mingw allows a
123+
Microsoft Windows version MicroEmacs to bu built and maintained.
124+
125+
MS-Dev GUI Build
126+
MicroEmacs is supplied with a MS-Dev 6.x project for building. This has
127+
only been set up for debugging and has limited build options, it will also
128+
produce a large executable image. The MS-Windows images shipped by JASSPA
129+
are built using the command line build environment which is detailed in a
130+
later section.
131+
132+
MS-Dev Command Line Build
133+
The command line build with MS-Dev is a little messy to set up, in the
134+
following sections we discuss MS-Dev 6.x under Windows 2000. There will be
135+
differences with different operating systems versions, different install
136+
paths and different versions of the MS-Dev toolkit. Use the following
137+
information as an outline ONLY, JASSPA will not take responsibility for
138+
the configuration of the command line environment, if in doubt then use
139+
the GUI builder.
140+
141+
To run nmake(1) from a DOS box then the MS-Dev compiler tools must be
142+
available in the command path. The MS-Dev kit V6.x is supplied with the
143+
necessary file to set up the path which is called VCVARS32.BAT and is
144+
typically located in directory:
145+
146+
C:\Program Files\Microsoft Visual Studio\VC98\Bin
147+
148+
This should be run first and then the command line make files may be run
149+
using nmake i.e. to build ME:-
150+
151+
nmake -f win32v6.mak me
152+
153+
To build NE:-
154+
155+
nmake -f win32v6.mak ne
156+
157+
To clean up after:-
158+
159+
nmake -f spotless
160+
161+
If you are going to perform a lot of command line building then it is
162+
easier to set up the environment and not have to run VCVARS32.BAT every
163+
time you compile.
164+
165+
You can add the variables to your environment, you will need to expand the
166+
VCVARS32.BAT script and then add the results. The following example is for
167+
MS-Dev 6.0 under W2K, the settings will differ depending on what O/S
168+
variant you are running and where you have installed software. The
169+
following ONLY serves as an example, you need to tailor for your
170+
installation.
171+
172+
* To set up the variables then Start -> Settings -> Control Panel which
173+
displays the Control Panel items.
174+
* Select System -> Advanced -> Environment variables
175+
* In User Variables for <User> then New... or Edit... the PATH
176+
variable. Add the command line tools execution paths to the
177+
environment variable, this will be something like the following (but
178+
without newlines):-
179+
180+
Variable Name: PATH
181+
Variable Value: %PATH%;
182+
C:\PROGRA~1\MICROS~3\Common\msdev98\BIN;
183+
C:\PROGRA~1\MICROS~3\VC98\BIN;
184+
C:\PROGRA~1\MICROS~3\Common\TOOLS\WINNT;
185+
C:\PROGRA~1\MICROS~3\Common\TOOLS;
186+
187+
* Similarly add the INCLUDE variable:-
188+
189+
Variable Name: INCLUDE
190+
Variable Value: C:\PROGRA~1\MICROS~3\VC98\ATL\INCLUDE;
191+
C:\PROGRA~1\MICROS~3\VC98\INCLUDE;
192+
C:\PROGRA~1\MICROS~3\VC98\MFC\INCLUDE;
193+
%INCLUDE%
194+
195+
* Similarly add the LIB variable:-
196+
197+
Variable Name: LIB
198+
Variable Value: C:\PROGRA~1\MICROS~3\VC98\LIB;
199+
C:\PROGRA~1\MICROS~3\VC98\MFC\LIB;
200+
%LIB%
201+
202+
* Accept the entries and close down the dialog. Start a new DOS command
203+
line and the variables should be set up ready for the build.
204+
205+
NOTES
206+
Other UNIX ports should be fairly easy from the base set of ported
207+
platforms. If any new platform ports are performed by individuals then
208+
please submit the makefiles and any source changes back to JASSPA - see
209+
Contact Information.
210+

0 commit comments

Comments
 (0)