| 1 |
This is the root directory for jmake. |
| 2 |
|
| 3 |
The jmake program is a Makefile generator. It comes from 'imake' one |
| 4 |
may find in the X11R4 distribution, but it produces a Makefile.SH |
| 5 |
instead of a Makefile. Jmake has a template which knows some metaconfig |
| 6 |
symbols and has built-in commands which make it more powerful than imake. |
| 7 |
|
| 8 |
The jmkmf script may be used to produce the Makefile.SH from a Jmakefile. |
| 9 |
Once the bootstrap is done, you can run 'make Makefile.SH' to rebuild the |
| 10 |
Makefile.SH in the current directory, or 'make Makefiles.SH' to build the |
| 11 |
Makefiles in a recursive manner. |
| 12 |
|
| 13 |
All the rules used by jmake are listed in an automatically built index. |
| 14 |
The jmake's cryptic syntax is documented in file NOTES. You may also |
| 15 |
have a look at the sample Jmakefiles that come with this package. |
| 16 |
Usually, you do not include them in the release, but I kept them so |
| 17 |
that you may have a real example and see how things are organized. |
| 18 |
|
| 19 |
If you choose to use jmake, then you will have to use metaconfig, in |
| 20 |
order to get a meaningful value for all the needed symbol. Thus, each |
| 21 |
time you change your Jmakefiles, it may be necessary to update the |
| 22 |
Configure script. |
| 23 |
|
| 24 |
Here is how to use jmake... |
| 25 |
|
| 26 |
First, you have to write a Jmakefile for each directory where you want |
| 27 |
to put a Makefile. Be sure to declare all the sub-directories with the |
| 28 |
SetSubdirs rule. Usually, the order of the rules is not significant, |
| 29 |
but you should make sure the Makefile begins with an 'all::' target, |
| 30 |
so that a default 'make' does not run a clean for instance. |
| 31 |
|
| 32 |
Then, if this is the first time, you have to bootstrap. Go to the main |
| 33 |
directory of your package and run: |
| 34 |
|
| 35 |
jmkmf |
| 36 |
make Makefiles.SH |
| 37 |
|
| 38 |
which will first produce the main makefile and then recursively build |
| 39 |
all the makefiles. |
| 40 |
|
| 41 |
Once you have bootstrapped once, you can edit a Jmakefile and rebuild |
| 42 |
the local makefile with |
| 43 |
|
| 44 |
make Makefile |
| 45 |
|
| 46 |
or all the hierachy below with: |
| 47 |
|
| 48 |
make Makefiles.SH |
| 49 |
|
| 50 |
If you want to extract all the makefiles, you may run |
| 51 |
|
| 52 |
sh Makefile.SH |
| 53 |
make Makefiles |
| 54 |
|
| 55 |
in the top-level directory. Finally, if you only want to test the |
| 56 |
generated Makefile.SH without disturbing the Makefile, run |
| 57 |
|
| 58 |
make Makefile.SH |
| 59 |
|
| 60 |
which will stop before running the produced file through sh. |
| 61 |
|
| 62 |
|
| 63 |
CAUTION: |
| 64 |
|
| 65 |
On machines whose cpp eats up tabs in macro expansion, the Makefile.SH |
| 66 |
produced might not be indented properly inside rules. |
| 67 |
|
| 68 |
Perl 4.0 PL10 sometimes dumps core, while PL3 does not. Thus, perl 4.0 |
| 69 |
PL10 should NOT be used with jmake, at least on a MIPS. |
| 70 |
|