1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
INSTALLING ICMAKE
=================
Version 12.01.00 (and beyond).
1. Unpack the archive:
======================
Instead of unpacking icmake can be cloned from
https://gitlab.com/fbb-git/icmake. See also https://fbb-git.gitlab.io/icmake/.
The installation files for Icmake comes as an archive, e.g.,
"icmake_12.01.00.tar.gz". These archives unpack to several directories and
files.
The archive unpacks to a directory icmake-12.01.00 below the current
directory. The version number in this directory may change to newer release
versions.
So, if you unpack icmake_12.01.00.tar.gz (or later versions) in the directory
/usr/local/src, a directory /usr/local/src/icmake/icmake-12.01.00 is created, as
well as other subdirectories below /usr/local/src/icmake/icmake-12.01.00
To unpack the archives, create an appropriate directory (e.g.,
`/usr/local/src/icmake' E.g,
tar xvzf icmake_12.01.00.tar.gz
The extraction of files from the archive should yield a lot of C source files
in various directories. Icmake's default distribution does not contain
makefiles for the Unix-utility `make' anymore.
2. Compile the programs
=======================
Change to the directory into which the sources were unpacked. E.g., do
cd icmake-12.01.00
This directory should contain this file (i.e., INSTALL). Icmake uses several
support programs, which do not have to be stored in the PATH
diretories. Before starting the compilation, make sure their locations are
in accordance with your local requirements:
- Inspect (and optionally modify) the path-settings in INSTALL.im.
In particular check:
#define BINDIR "usr/bin"
#define SKELDIR "usr/share/icmake"
#define MANDIR "usr/share/man"
#define LIBDIR "usr/lib/icmake"
#define CONFDIR "etc/icmake"
#define DOCDIR "usr/share/doc/icmake"
These locations are all are relative to a specifiable base-directory.
Meaning:
BINDIR the binary programs and scripts
SKELDIR the icmstart-script skeleton files
MANDIR the base directory of man-pages (under MANDIR/man1 and
MANDIR/man2)
LIBDIR icmake's support programs
CONFDIR the system-wide configuration files (AUTHOR, VERSION,
icmstart.rc)
DOCDIR various doc-files (e.g., changelog)
- Inspect (and optionally modify) the availability of the program
mentioned in ./def/programs (they should be available on any Unix(like)
systems).
- Prepare for the program construction by running the shell-script
`prepare' as follows:
./prepare /
(this assumes that you want to prepend all base locations mentioned in
INSTALL.im with /; other base locations are also possible, e.g.,
./prepare /tmp
prepares for installation of all files in the specified locations, all below
/tmp.
- Next run the shell-script `buildlib' as follows:
./buildlib x
This constructs the library used by the various icmake programs.
- To create icmake and its support programs run
./build all
3. Install the files
====================
You probably must do this as `root':
./install [strip] all
This installs all files under the root directory (which was initially
specied when calling ./prepare) When providing the strip argument
binaries are stripped before being installed.
Note that by default unstripped binaries are installed.
Separate parts may be installed as well. E.g.,
./install [strip] progs / - installs all executables
./install scripts / - installs the icmstart/icmbuild scripts
./install man / - installs the man-pages
./install skel / - installs the skeletons
./install etc / - installs the default icmstart.rc
related files
./install doc / - installs the docs
4. Clean up the garbage
=======================
./clean
5. Predefined symbols
=====================
Icmake does not require special modifications. However, you may wish
to take a look at the file icm-pp/loadsymbols.c. In this file the function
'loadSymbols()' of the preprocessor icm-pp is found. The preloaded symbols of
Icmake are defined in this function. If you plan to use these predefined
symbols in your Icmake scripts, make sure that the conditional code in the
file pp/loadsym.c recognizes your platform.
If you are unsure whether this code recognizes your compiler, build
Icmake as distributed and try out the sample icmake file examples/defines.im
(i.e., say: "icmake examples/defines"). If the output of the makefile is
not satisfatory, modify pp/loadsym.c. E.g., if your MegaC compiler defines the
symbol MEGA_C, you might want to add the following lines to pp/loadsym.c:
#ifdef MEGA_C
preload("MEGA_C", "1");
#else
preload("MEGA_C", "0");
#endif
Currently the following symbols are predefined:
--------------------------------------------------------------
symbol 1 when defined on the platform ... otherwise 0
--------------------------------------------------------------
unix Unix, usually with GNU's gcc compiler
UNIX same
linux '386 or '486 running Linux (usually with gcc)
LINUX same
M_SYSV, M_UNIX '386 or '486 running SCO/Unix (usually with
Microsoft C)
_POSIX_SOURCE Unix with Posix compliant compiler
__hpux HP-UX, with the native HP compiler
--------------------------------------------------------------
If you want to modify something here which hasn't been done before, please
email me about it, and I'll include it in the standard distribution.
|
