diff options
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL | 95 |
1 files changed, 31 insertions, 64 deletions
@@ -23,7 +23,7 @@ directory of your choice using the command: tar xfvz mdk-X.Y.tar.gz where X.Y stands for the downloaded version (the current stable release -being version {No value for `VERSION'}). +being version 1.2). Requirements ============ @@ -31,21 +31,21 @@ Requirements In order to build and install MDK, you will need the following libraries installed in your system: - - GLIB 1.2.0 (http://www.gtk.org) (required) + - GLIB 2.4.0 (http://www.gtk.org) (required) - - GNU Flex 2.3 (http://www.gnu.org/software/flex/flex.html) + - GNU Flex 2.5 (http://www.gnu.org/software/flex/flex.html) (required) - - GTK 1.2.0 (http://www.gtk.org) (optional) + - GTK 2.4.0 (http://www.gtk.org) (optional) - - Libglade (ftp://ftp.gnome.org/pub/GNOME/stable/sources/libglade/) + - Libglade 2.4.0 (http://ftp.gnome.org/pub/GNOME/sources/libglade/2.4/) (optional) - GNU Readline (http://cnswww.cns.cwru.edu/php/chet/readline/rltop.html) (optional) - - GNU Libguile 1.3 (http://www.gnu.org/software/guile) (optional) + - GNU Libguile 1.6 (http://www.gnu.org/software/guile) (optional) If present, readline and history are used to provide command completion and history management to the command line MIX virtual @@ -56,8 +56,8 @@ support and will be extensible using Scheme. *Please note*: you need both the libraries _and_ the headers; this means both the library package and the `-dev' package if you do not -compile your libraries yourself (ex: installing `libgtk1.2' and -`libgtk1.2-dev' on Debian). +compile your libraries yourself (ex: installing `libgtk2.0' and +`libgtk2.0-dev' on Debian). Basic installation ================== @@ -78,8 +78,8 @@ and, if they are present, will generate the appropiate makefiles for building the `gmixvm' graphical user interface. Upon completion, you should see a message with the configuration results like the following: - *** GNU MDK 0.5 has been successfully configured. *** - + *** GNU MDK 1.2 has been successfully configured. *** + Type 'make' to build the following utilities: - mixasm (MIX assembler) - mixvm (MIX virtual machine, with readline support, @@ -148,42 +148,9 @@ switches with configure: configure --help -Supported platforms -=================== - - GNU MDK has been tested in the following platforms: - - * Debian GNU/Linux 2.2/2.3/3.0 - - * Redhat GNU/Linux 7.0 (Agustin Navarro), 6.2 (Roberto Ferrero) - - * Mandrake 8.0 (Agustin Navarro) - - * FreeBSD 4.2, 4.3, 4.4, 4.5 (Ying-Chieh Liao) - - * Solaris 2.8/gcc 2.95.3 (Stephen Ramsay) - - * MS Windows 98 SE/Cygwin 1.1.8-2 (Christoph von Nathusius)(1) - - * Mac OS X 10.1.2 (Johan Swanljung) +------------------------------------------------------------------------ +------------------------------------------------------------------------ - MDK will probably work on any GNU/Linux and BSD platform. If you try -it in a platform not listed above, please send a mail to the author -<jao@gnu.org>. - - ---------- Footnotes ---------- - - (1) Caveats: Christoph has only tested `mixvm' and `mixasm' on this -platform, using `gcc' 2.95.3-2, `GLIB' 1.2.10 and `GNUreadline' 4.1-2. -He has reported missing history functionalities on a first try. If you -find problems with history/readline functionality, please try a -newer/manually installed readline version. - - - - ------------------------------------------------------------------------ - ------------------------------------------------------------------------ - Generic configure help ********************** @@ -192,36 +159,36 @@ Basic Installation ================== For more information specific to this package, please read the README -file. This source code distribution is autoconfiguring and you should be -able to compile it and install it without manual interventions such as -editing Makefiles, configuration files, and so on. These are generic +file. This source code distribution is autoconfiguring and you should be +able to compile it and install it without manual interventions such as +editing Makefiles, configuration files, and so on. These are generic instructions for people who are not familiar with installing autoconfiguring software. The simplest way to compile this package is to enter the source code main directory and do the following: - + 1. Configure the source code by typing: % sh ./configure If you're planning to install the package into your home directory or to a location other than `/usr/local' then add the flag - `--prefix=PATH' to `configure'. For example, if your home directory + `--prefix=PATH' to `configure'. For example, if your home directory is `/home/luser' you can configure the package to install itself there by invoking: % sh ./configure --prefix=/home/luser - + While running, `configure' prints some messages telling which - features is it checking for. + features is it checking for. 2. Compile the package by typing: % make Running `make' takes a while. If this is a very large package, now is the time to go make some coffee. - - 3. Some packages are bundled with self-tests for source-code - verification. If this package includes such tests, you can - optionally run them after compilation by typing + + 3. Some packages are bundled with self-tests for source-code + verification. If this package includes such tests, you can + optionally run them after compilation by typing % make check 4. Type `make install' to install the programs and any data files and @@ -236,9 +203,9 @@ main directory and do the following: in the `--prefix' flag. If any of these directories do not presently exist, they will be - created on demand. + created on demand. - If you are installing in your home directory make sure that + If you are installing in your home directory make sure that `/home/luser/bin' is in your path. If you're using the bash shell add this line at the end of your .cshrc file: PATH="/home/luser/bin:${PATH}" @@ -257,7 +224,7 @@ Compiler configuration ====================== The `configure' shell script is responsible for choosing and configuring -the compiler(s). +the compiler(s). The following options allow you to specify whether you want to enable or disable various debugging mechanisms: @@ -288,7 +255,7 @@ On the tcsh shell, use the `setenv' command instead: For other shell, please consult your shell's documentation. Similarly, you can increase the optimization level by assigning these -variables to "-g -O3". +variables to "-g -O3". The following options allow you to reconsider the `configure' shell script's choice of Fortran compilers. @@ -296,10 +263,10 @@ choice of Fortran compilers. `--with-f2c' Compile the Fortran code by translating it to C, even if a native Fortran compiler is available. A copy of the f2c translator should be - bundled in the distribution. It will be compiled and then used to + bundled in the distribution. It will be compiled and then used to compile your Fortran code. `--with-g77' - Compile the Fortran code with g77 even if a proprietary Fortran + Compile the Fortran code with g77 even if a proprietary Fortran compiler is available `--with-f77=F77' Compile the Fortran code with the specified Fortran compiler. @@ -310,7 +277,7 @@ or may not be available. To see what is available, type: About the configure script ========================== - + The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. @@ -369,4 +336,4 @@ you can use the `configure' options `--x-includes=DIR' and ---- -$Id: INSTALL,v 1.5 2002/04/08 00:29:59 jao Exp $
\ No newline at end of file +$Id: INSTALL,v 1.6 2004/08/02 11:26:40 jao Exp $
\ No newline at end of file |