File: INSTALL

package info (click to toggle)
ftjam 2.5.2-1.1
  • links: PTS
  • area: main
  • in suites: bullseye, buster, jessie, jessie-kfreebsd, lenny, sid, squeeze, stretch, wheezy
  • size: 1,216 kB
  • ctags: 1,237
  • sloc: ansic: 7,226; sh: 2,751; yacc: 443; makefile: 121
file content (136 lines) | stat: -rwxr-xr-x 3,710 bytes parent folder | download | duplicates (2)
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
I. Compiling FT Jam:
--------------------

  1. With a previous version of Jam:
  ----------------------------------
  
  The easiest way to compile Jam is to use a previous version of the
  program. If you already have one installed on your system, simply
  type "jam" in this directory.
  
  This will create a new executable named "jam" or "jam.exe", located
  in a new system-dependent directory, whose name can be:
  
     bin.ntx86\jam.exe
     bin.linux86\jam
     etc..
     

  1. On Unix and Cygwin:
  ----------------------
  
  FTJam supports the traditionnal Unix build & installation sequences,
  you can simply type:
  
     ./configure --prefix=<yourprefix>
     make
     make install
     
  note that only the jam executable will be installed. No documentation
  is provided for now...
  
  
  2. With toolset-specific makefiles:
  -----------------------------------
  
  You can also use one of the Makefiles located in the "builds"
  directory. Here's what you need to type on the command line,
  depending on your system and compiler:
  
  
  a. Windows + Visual C++:
  
       set VISUALC=/install/path/to/visual/compiler
       set JAM_TOOLSET=VISUALC
       nmake -f builds\win32-visualc.mk
                           
                           
  b. Windows + Borland C++: (be sure to use the Borland "make" tool)

        set BORLANDC=/install/path/to/borland/compiler
        set JAM_TOOLSET=BORLANDC
        make -fbuilds\win32-visualc.mk   


  c. Windows + Mingw (gcc):

        set BORLANDC=/install/path/to/borland/compiler
        set JAM_TOOLSET=BORLANDC
        make -f builds\win32-visualc.mk   


  WE DO NOT PROVIDE PROJECT FILES FOR ANY SPECIFIC COMPILER/TOOLSET
 
      



  3. Without jam:
  ---------------
  
  If you don't have a jam binary installed, you can still compile the
  program using the following method:
  
    - copy the file "Makefile0" to "Makefile"
    
    - edit the new "Makefile"  and adapt it to your OS. Simply uncomment the
      lines specific to your system
      
    - invoke your make tool
  

  Note that the Makefile is used to build a boot-strap version of jam,
  called "jam0". Once it is built, the "jam0" executable is called to
  re-build itself.
  
  If this second pass doesn't work, this is probably because you didn't
  set some environment variable that indicates which compiler to use to
  Jam. Read the Jam documentation for more information on this.. 


  

II. Installation:
-----------------

  Except for Unix, we do not provide any sophisticated
  installation pass. Simply copy the new jam executable
  to any directory in your current path.. and start
  using it !!


III. Default files:
-------------------

  All default files for Jam are compiled within the
  executable itself.
  
  There are no special configuration directory to
  place global or user preferences. Until further
  notice, all defaults can only be changed by using
  command line switches and setting environment
  variables..


IV. Windows and OS/2 Binary packages:
-------------------------------------

  It's possible to create zip files of the binaries
  on Windows and OS/2 system by following these simple
  steps (you need to have the "zip" utility in your
  path !!):
  
    1. build jam
    2. strip the jam.exe executable in bin.ntx86 when
       possible
    3. call "jam package"
    
  you should see a file named "ftjam-xxxxx-win32.zip"
  or "ftjam-xxxxx-os2.zip" in the current directory,
  as well as "ftjam-xxxxx.zip" (containing the sources)


Good luck,


- David Turner,  28 Jul 2001