1INSTALLATION PROCEDURE: 2---------------------- 3 41. First, decide whether you want ncurses to replace your existing library (in 5 which case you'll need super-user privileges) or be installed in parallel 6 with it. 7 8 The --prefix option to configure changes the root directory for installing 9 ncurses. The default is normally in subdirectories of /usr/local, except 10 for systems where ncurses is normally installed as a system library (see 11 "IF YOU ARE A SYSTEM INTEGRATOR"). Use --prefix=/usr to replace your 12 default curses distribution. 13 14 The package gets installed beneath the --prefix directory as follows: 15 16 In $(prefix)/bin: tic, infocmp, captoinfo, tset, 17 reset, clear, tput, toe, tabs 18 In $(prefix)/lib: libncurses*.* libcurses.a 19 In $(prefix)/share/terminfo: compiled terminal descriptions 20 In $(prefix)/include: C header files 21 Under $(prefix)/man: the manual pages 22 23 Note that the configure script attempts to locate previous installation of 24 ncurses, and will set the default prefix according to where it finds the 25 ncurses headers. 26 27 Do not use commands such as 28 29 make install prefix=XXX 30 31 to change the prefix after configuration, since the prefix value is used 32 for some absolute pathnames such as TERMINFO. Instead do this 33 34 make install DESTDIR=XXX 35 36 See also the discussion of --with-install-prefix. 37 382. Type `./configure' in the top-level directory of the distribution to 39 configure ncurses for your operating system and create the Makefiles. 40 Besides --prefix, various configuration options are available to customize 41 the installation; use `./configure --help' to list the available options. 42 43 If your operating system is not supported, read the PORTABILITY section in 44 the file ncurses/README for information on how to create a configuration 45 file for your system. 46 47 The `configure' script generates makefile rules for one or more object 48 models and their associated libraries: 49 50 libncurses.a (normal) 51 52 libcurses.a (normal, a link to libncurses.a) 53 This gets left out if you configure with --disable-overwrite. 54 55 libncurses.so (shared) 56 57 libncurses_g.a (debug) 58 59 libncurses_p.a (profile) 60 61 libncurses.la (libtool) 62 63 If you configure using the --enable-widec option, a "w" is appended to the 64 library names (e.g., libncursesw.a), and the resulting libraries support 65 wide-characters, e.g., via a UTF-8 locale. The corresponding header files 66 are compatible with the non-wide-character configuration; wide-character 67 features are provided by ifdef's in the header files. The wide-character 68 library interfaces are not binary-compatible with the non-wide-character 69 version. Building and running the wide-character code relies on a fairly 70 recent implementation of libiconv. We have built this configuration on 71 various systems using libiconv, sometimes requiring libutf8. 72 73 If you configure using the --with-pthread option, a "t" is appended to 74 the library names (e.g., libncursest.a, libncursestw.a). 75 76 If you do not specify any models, the normal and debug libraries will be 77 configured. Typing `configure' with no arguments is equivalent to: 78 79 ./configure --with-normal --with-debug --enable-overwrite 80 81 Typing 82 83 ./configure --with-shared 84 85 makes the shared libraries the default, resulting in 86 87 ./configure --with-shared --with-normal --with-debug --enable-overwrite 88 89 If you want only shared libraries, type 90 91 ./configure --with-shared --without-normal --without-debug 92 93 Rules for generating shared libraries are highly dependent upon the choice 94 of host system and compiler. We've been testing shared libraries on 95 several systems, but more work needs to be done to make shared libraries 96 work on other systems. 97 98 If you have libtool installed, you can type 99 100 ./configure --with-libtool 101 102 to generate the appropriate static and/or shared libraries for your 103 platform using libtool. 104 105 You can make curses and terminfo fall back to an existing file of termcap 106 definitions by configuring with --enable-termcap. If you do this, the 107 library will search /etc/termcap before the terminfo database, and will 108 also interpret the contents of the TERM environment variable. See the 109 section BSD CONVERSION NOTES below. 110 1113. Type `make'. Ignore any warnings, no error messages should be produced. 112 This should compile the ncurses library, the terminfo compiler tic(1), 113 captoinfo(1), infocmp(1), toe(1), clear(1) tset(1), reset(1), and tput(1) 114 programs (see the manual pages for explanation of what they do), some test 115 programs, and the panels, menus, and forms libraries. 116 1174. Run ncurses and several other test programs in the test directory to 118 verify that ncurses functions correctly before doing an install that 119 may overwrite system files. Read the file test/README for details on 120 the test programs. 121 122 NOTE: You must have installed the terminfo database, or set the 123 environment variable $TERMINFO to point to a SVr4-compatible terminfo 124 database before running the test programs. Not all vendors' terminfo 125 databases are SVr4-compatible, but most seem to be. 126 127 It is possible to configure ncurses to use other terminfo database formats. 128 A few are provided as examples in the include-directory (see --with-caps). 129 130 If you run the test programs WITHOUT installing terminfo, ncurses may 131 read the termcap file and cache that in $HOME/.terminfo, which will 132 thereafter be used instead of the terminfo database. See the comments 133 on "--enable-getcap-cache", to see why this is a Bad Thing. 134 135 The ncurses program is designed specifically to test the ncurses library. 136 You can use it to verify that the screen highlights work correctly, that 137 cursor addressing and window scrolling works OK, etc. 138 1395. Once you've tested, you can type `make install' to install libraries, 140 the programs, the terminfo database and the manual pages. Alternately, you 141 can type `make install' in each directory you want to install. In the 142 top-level directory, you can do a partial install using these commands: 143 144 'make install.progs' installs tic, infocmp, etc... 145 'make install.includes' installs the headers. 146 'make install.libs' installs the libraries (and the headers). 147 'make install.data' installs the terminfo data. (Note: `tic' must 148 be installed before the terminfo data can be 149 compiled). 150 'make install.man' installs the manual pages. 151