Source

debugftjam /

Filename Size Date modified Message
builds
1.0 KB
3.3 KB
8.7 KB
3.5 KB
40.5 KB
85.0 KB
25.5 KB
6.2 KB
49.0 KB
2.1 KB
2.8 KB
4.1 KB
37.5 KB
10.6 KB
274 B
1.1 KB
1.6 KB
547 B
19.7 KB
2.3 KB
190 B
421 B
1.5 KB
13.6 KB
9.3 KB
3.3 KB
13.0 KB
339 B
3.6 KB
6.9 KB
3.0 KB
531 B
8.7 KB
7.2 KB
2.5 KB
6.4 KB
1.2 KB
3.7 KB
348 B
3.8 KB
206 B
9.6 KB
10.9 KB
56.3 KB
373 B
62.4 KB
4.0 KB
9.5 KB
8.4 KB
1.0 KB
4.7 KB
2.2 KB
13.8 KB
336 B
16.3 KB
2.1 KB
1.9 KB
358 B
3.0 KB
610 B
2.1 KB
854 B
163 B
6.2 KB
1.2 KB
5.1 KB
8.7 KB
31.4 KB
821 B
1.1 KB
491 B
7.4 KB
6.3 KB
7.5 KB
1.4 KB
1.6 KB
302 B
992 B
296 B
332 B
4.5 KB
5.6 KB
5.1 KB
4.0 KB
259 B
6.6 KB
712 B
1.4 KB
=============================================================================

This if "FT-Jam", a simple derivative of the Jam build tool, based and
100% compatible with Jam 2.5. See http://www.freetype.org/jam/ for more
details.

Note that you'll find the original Jam README in the file README.ORG



Installation on Unix (and Cygwin):
----------------------------------

Unlike Classic Jam, this release can be installed with traditionnal Unix
commands, i.e.:

  ./configure <options>
  make
  make install    (may need to be root)

at the moment, only the 'jam' executable is installed in $prefix/bin.
we'll try to install the documentation and convert it to manpages later,
if time permits.

If the './configure' command doesn't work, do the following, you might
have a working source release that wasn't packaged for distribution. You
can get it to install normally doing the following:

  chmod +x configure
  chmod +x yyacc
  cd builds/unix
  autoconf
  cd ../..

then

  ./configure <options>
  make
  make install


Installation on Win32:
----------------------

We provide a few build scripts for various compilers on Win32. In all cases,
this will generate an executable named 'jam.exe' within the bin.ntx86
directory:

  Visual C++:
    set JAM_TOOLSET=VISUALC
    nmake -f builds\win32-visualc.mk

  Borland C++:
    set JAM_TOOLSET=BORLANDC
    make -fbuilds\win32-borlandc.mk

  Mingw:
    set JAM_TOOLSET=MINGW
    gmake -f builds/win32-gcc.mk

  Digital Mars:
    set JAM_TOOLSET=DIGITALMARS
    make -f builds\win32-dmars.mk

  Cygwin:
    make -f builds/win32-cygwin.mk


Copy the executable to your path.

==============================================================================
IMPORTANT FOR CYGWIN AND MINGW USERS:
Note that the Mingw and Cygwin builds produce different executables !!
the first one will only work correctly on the Windows command line, while
the second one will only work on a Unix shell (e.g. Bash).
===============================================================================


Installation with Jam or FT-Jam:
--------------------------------

If you already have a previous version of Jam or FT-Jam in your path, simply
invoke it from the root directory. This will generate the 'jam' or 'jam.exe'
executable in a directory named 'bin.<system>', where '<system>' depends
on your platform, e.g.  bin.linuxx86, bin.ntx86, etc...


Differences with Classic Jam:
-----------------------------

See the file CHANGES for a list of differences from Classic Jam, and between
successive revisions of FT-Jam.

Note that you can also parse the Jambase, since documentation comments
have been added to nearly all rules


Troubleshooting:
----------------

Please report problems to the Jam mailing list (jamming@perforce.com).
We'll try to create a FT-Jam specific list in the future.