1 Notes on porting Jam - revised 12/31/2000
3 1) Working out system dependencies in the Jam code.
5 Jam's OS footprint is fairly small. For OS independent work Jam
6 liberally uses standard libc functions like stdio, malloc, and
7 string. The OS dependent interfaces are:
11 file_parse() - split a file name into dir/base/suffix/member
12 file_build() - build a filename given dir/base/suffix/member
13 file_dirscan() - scan a directory for files
14 file_archscan() - scan an archive for files
15 file_time() - get the timestamp of a file, if not already
16 done by file_dirscan().
20 execcmd() - execute a shell script
21 execwait() - wait for any outstanding execcmd()'s.
23 The current implementations are:
32 execunix.c - UNIX, OS/2, NT
35 2) Defining OSMAJOR, OSMINOR in jam.h
37 So that the Jambase and Jamfile know their host, Jam defines $(OS)
38 to be something useful for each platform. Make sure that there is
39 code in jam.h to generate a useful value for $(OS), and key it off
40 the platform specific C-preprocessor symbol. If the C-preprocessor
41 doesn't itself defines such a symbol, add a define to the Makefile.
43 In addition to $(OS), you can also set $(OSPLAT) if the OS runs on
44 multiple platforms (like Linux or NT).
46 3) Working out system dependencies in the Jambase
48 With the value of $(OS) available, the Jambase can be extended to
49 support special variables or rules for new platforms. See the
50 current support for VMS, NT, and Mac.
54 The generated files jamgram.h and jamgram.c are distributed for the
55 poor souls without yacc.
57 5) Known problematic systems:
59 - Pyramid has no malloc.h, memory.h
61 - Encore has no stdlib.h
63 - Bull DPX has sys/file.h problems
65 6) Send the results back.
67 If you do porting work, the result can be integrated into future
68 releases if you send it back to the author's address in the README.