Mercurial > ~dholland > hg > ag > index.cgi

comparison doc/install/install.txt @ 2:4b08ee1ecb99

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Adjust install notes to clarify that Wine applies only to the Windows build. (Thanks to Perry Metzger for test-driving.)
author David A. Holland
date Sun, 26 Apr 2009 17:58:26 -0400
parents 13d2b8934445
children e23ad76d0588
comparison
equal deleted inserted replaced
1:60d3ca9d3f6b 2:4b08ee1ecb99
20 The Unix build currently requires gcc 3.x or 4.x. Reasonable patches 20 The Unix build currently requires gcc 3.x or 4.x. Reasonable patches
21 for other Unix compilers (e.g. the Intel compiler on Linux, or Sun's 21 for other Unix compilers (e.g. the Intel compiler on Linux, or Sun's
22 payware compiler) will probably be accepted. If you have gcc set up as 22 payware compiler) will probably be accepted. If you have gcc set up as
23 a cross-compiler, you can cross-compile AnaGram. See below. 23 a cross-compiler, you can cross-compile AnaGram. See below.
24 24
25 The Windows build requires IBM Visual Age for C++ version 3.5, because 25 The Windows GUI build requires IBM Visual Age for C++ version 3.5,
26 the GUI uses that compiler's semi-proprietary GUI class library. You 26 because the GUI uses that compiler's semi-proprietary GUI class
27 also need a recent version of Wine. 27 library. You also need Wine 1.0 or later. See below.
28
29 Wine must be configured such that I:\\IBMCPPW\\BIN\\ICC.EXE is the
30 main compiler executable. (To arrange this, create a suitable symbolic
31 link named "i:" in ~/.wine/dosdevices.) Note that while it would not
32 be difficult to make this more flexible, migrating away from this
33 compiler is a better use of time.
34
35 The source tree must also be accessible to Wine somehow; it doesn't
36 matter what the specific drive or path mapping is.
37
38 At one time it was necessary to use patchlevel 354 (neither newer nor
39 older) of ILINK.EXE, which you can get from IBM support. This version
40 is 188928 bytes long and has md5sum f48f0aace7c6f247bae015b43f16969a.
41 Wine has improved a good deal since then, however, and this may no
42 longer be necessary.
43
44 Because of problems with Wine on NetBSD, you can only compile the
45 Windows build on NetBSD with some combinations of versions of NetBSD
46 and of Wine. Linux works, however.
47 28
48 Note that the source, though not the build system, has some support 29 Note that the source, though not the build system, has some support
49 for a number of other Windows compilers (including Borland, Watcom, 30 for a number of other Windows compilers (including Borland, Watcom,
50 and Microsoft) and you may be able to get these to work to build the 31 and Microsoft) and you may be able to get these to work to build the
51 command-line-only version. Building a Windows command-line only 32 command-line-only version. Building a Windows command-line only
56 37
57 Building the manual requires LaTeX. It doesn't require anything that 38 Building the manual requires LaTeX. It doesn't require anything that
58 doesn't come with teTeX, so no unusual steps should be necessary. 39 doesn't come with teTeX, so no unusual steps should be necessary.
59 40
60 41
42 1a. Notes on Wine (Windows build only)
43
44 The Windows build requires version 3.5 of the IBM Visual Age for C++
45 compiler, and Wine to run it.
46
47 Wine must be configured such that I:\\IBMCPPW\\BIN\\ICC.EXE is the
48 main compiler executable. (To arrange this, create a suitable symbolic
49 link named "i:" in ~/.wine/dosdevices.) Note that while it would not
50 be difficult to make this more flexible, migrating away from this
51 compiler is a better use of time.
52
53 The source tree must also be accessible to Wine somehow; it doesn't
54 matter what the specific drive or path mapping is.
55
56 At one time, long before Wine 1.0, it was necessary to use patchlevel
57 354 (neither newer nor older) of ILINK.EXE, which you can get from IBM
58 support. This version is 188928 bytes long and has md5sum
59 f48f0aace7c6f247bae015b43f16969a. Wine has improved a good deal since
60 then, however, and this may no longer be necessary.
61
62 Because of problems with Wine on NetBSD, you can only compile the
63 Windows build on NetBSD with some combinations of versions of NetBSD
64 and of Wine. Linux works, however.
65
66
61 2. Configuring 67 2. Configuring
62 68
63 AnaGram comes with a "configure" script that sets up the build 69 AnaGram comes with a "configure" script that sets up the build
64 environment. This is *not* a GNU autoconf script, although it looks 70 environment. This is *not* a GNU autoconf script, although it looks
65 superficially like one. 71 superficially like one.