| 1 |
|
| 2 |
*****************WARNING****************** |
| 3 |
Do not attempt to compile individual programs |
| 4 |
in individual program subdirectories! |
| 5 |
*****************WARNING****************** |
| 6 |
|
| 7 |
MAKE CHANGES IN THE TOP-LEVEL MAKEFILE |
| 8 |
|
| 9 |
CALL MAKE FROM THE TOP LEVEL |
| 10 |
|
| 11 |
I have a weakness for complex, multilevel makefiles. Therefore, the |
| 12 |
makefiles included here are complex and multilevel. Always run make from |
| 13 |
the top-level directory. Try 'make help' for a listing of possible |
| 14 |
targets (the only one left out is randstr: compile it with make randstr). |
| 15 |
All the important variables are defined in the top-level makefile, and |
| 16 |
most of the make targets will crash and burn if they do not find the |
| 17 |
variables that they are looking for. |
| 18 |
|
| 19 |
The good part of this is that except for the datfiles tree, the |
| 20 |
sub-makefiles are all very simple. All the programs have rules of |
| 21 |
the form: program: program.o, with the appropriate link command. |
| 22 |
The only target safe to call in individual directories is clean. |
| 23 |
|
| 24 |
The makefiles for the datfiles subdirectory are complex in an attempt to |
| 25 |
avoid distributing any more data than needed. The offensive files are |
| 26 |
distributed in unrotated format; the make files have to rotate these |
| 27 |
files before strfiling them. The make clean routine has to be able to |
| 28 |
delete the rotated files without touching the unrotated ones. |
| 29 |
|
| 30 |
Pretty much everything is configurable in the top-level makefile, and it |
| 31 |
mostly has pretty decent comments telling you what it is that you're |
| 32 |
configuring. Read and change it as necessary. |
| 33 |
|
| 34 |
Amy A. Lewis [email protected] |
| 35 |
|
| 36 |
|
| 37 |
Notes for non-Linux users |
| 38 |
------------------------- |
| 39 |
|
| 40 |
The only system-dependant thing you should need to worry about is which |
| 41 |
C function library to use for regular expressions. Two are supported: |
| 42 |
the BSD regex library (re_comp/re_exec), and the POSIX regex library |
| 43 |
(regcomp/regexec). Which you should use depends on what functions are |
| 44 |
available, and which performs faster for you. |
| 45 |
|
| 46 |
If neither are available, you could try compiling the GNU Rx library, |
| 47 |
which offers a high-performance regular expression library with both BSD |
| 48 |
and POSIX interfaces. This is available at your nearest GNU software |
| 49 |
mirror. |
| 50 |
|
| 51 |
To select the BSD regex library, add -DBSD_REGEX to REGEXDEFS in the |
| 52 |
top-level Makefile. To select the POSIX regex library, add add |
| 53 |
-DPOSIX_REGEX to REGEXDEFS. If neither is defined, no regular |
| 54 |
expression support will be included. |
| 55 |
|
| 56 |
Using the POSIX regex library requires the POSIX regex data structures |
| 57 |
to be declared. This might be in the <regex.h> header, or in the <rx.h> |
| 58 |
header. Define -DHAVE_REGEX_H in REGEXDEFS if it is in the <regex.h> |
| 59 |
header, or -DHAVE_RX_H if it is in the <rx.h> header. If it turns out |
| 60 |
to be somewhere else for your platform, please report this to the |
| 61 |
current fortune-mod maintainer. |
| 62 |
|
| 63 |
The -DHAVE_REGEX_H and -HAVE_RX_H defines are also applicable to the BSD |
| 64 |
regex library, but as they do not use custom data structures, not using |
| 65 |
them should not result in anything more than "function not declared" |
| 66 |
warnings. |
| 67 |
|
| 68 |
-- Dennis L. Clark <[email protected]> |