======================================================================= 9 Sep 2006 DON'T USE THIS. See the latest version of poplog in http://www.cs.bham.ac.uk/research/projects/poplog/freepoplog.html ======================================================================= SHORT-CUT-INSTALLATION.txt http://www.cs.bham.ac.uk/research/poplog/local/com/SHORT-CUT-INSTALLATION.txt $poplocal/local/ftp/linux-cd/SHORT-CUT-INSTALLATION.txt 6 Apr 2004 Aaron Sloman http://www.cs.bham.ac.uk/~axs/ ------------------------------ Modified 30 Nov 2004 To refer to new script http://www.cs.bham.ac.uk/research/poplog/com/CHECK_LINUX_FACILITIES ------------------------------ This file is http://www.cs.bham.ac.uk/research/poplog/linux-cd/SHORT-CUT-INSTALLATION.txt ------------------------------ PRE-INSTALLATION-CHECK Before installing linux Poplog it is a good idea to fetch the file http://www.cs.bham.ac.uk/research/poplog/com/CHECK_LINUX_FACILITIES make it executable chmod 755 CHECK_LINUX_FACILITIES and run it ./CHECK_LINUX_FACILITIES That will check whether you have a C compiler (gcc) which is required for rebuilding poplog, and various X window system libraries required for poplog's graphical facilities. In some cases the libraries are present but have not been set up to support software development. The script will fix that by adding symbolic links. The script will also check whether you have Motif present, which is required for some of poplog's graphical facilties, though not all and will also create a symbolic link to make Motif accessible by Poplog if necessary. If you do not have gcc present it may be possible to get a pre-built poplog executable to run on your system. If gcc is present and the X window graphical libraries are present, you can continue as follows. ------------------------------ The rest of this file assumes that you have fetched the file http://www.cs.bham.ac.uk/research/poplog/bham-linux-poplog.tar.gz and untarred it somewhere, using one of these commands tar xfz bham-linux-poplog.tar.gz zcat bham-linux-poplog.tar.gz | tar xf - This will produce various things including information files with suffix '.txt' (like this one) and some installation scripts, described below. ======================================================================= SHORT CUT INSTALLATION 1. The preinstallation checking script described above is included in the package, and can be run if you have not already run it: ./CHECK_LINUX_FACILITIES Note what is printed out. If it says anything is missing you may have to get help (e.g. via the comp.lang.pop news group or the pop-forum AT cs.bham.ac.uk email list) before proceeding. If the checking script says everything is present except Motif, then you can link poplog without Motif, as explained below. Most things will still work. Two further scripts are provided, described below, which automate the installation of Linux Poplog so as to replicate the installation at Birmingham. 2. Decide whether you can use motif or not. You may or may not have motif installed. It is useful but not essential. When you run the pre-installation checking script ./CHECK_LINUX_FACILITIES It will tell you whether you Motif. If you don't have motif, read preliminary steps 1 and 2 of the file: AREADME.motifcheck.txt If you don't have motif you can follow instructions for installing it, or else install poplog without motif facilities. Most things work without motif, though the XVed editor will not have menu buttons or a scroll-bar if poplog is run without motif. 3. After untarring the main file bham-linux-poplog.tar.gz decide (a) whether you wish to install Poplog with or without motif (with motif is normally the preferred option, but not essential) (b) whether you want to install Poplog in the default directory /usr/local/poplog/ or somewhere else. There are two 'short-cut' scripts which are available in the directory where you untarred the poplog distribution file. These will install poplog with the Birmingham extras, and create appropriate startup scripts for users: INSTALL_EVERYTHING_WITH_MOTIF INSTALL_EVERYTHING_WITHOUT_MOTIF As explained below, you can run them with an installation directory for poplog specified, or run them without specifying a directory, in which case they will use /usr/local/poplog as the directory (and you will the probably have to run them while logged in as superuser). These scripts produce a lot of output. It is recommended that you save the output in a log file, e.g. using ' > install.log ' as indicated below. Error messages will not go into the file, and will be printed direct to the screen. By sending the main output to a file, you will make it easier to review the output later on, e.g. using a text editor, or using 'less install.log' to read through it. You can then see any further instructions or comments that are printed out, though there is a lot of printout that can be ignored as it merely reports what is being done. When Poplog lisp is installed that produces warning messages that can be ignored. INSTALLATION PROCEDURE: Choose one of the following four installation options: Option 1: ./INSTALL_EVERYTHING_WITH_MOTIF > install.log If you have motif and want to use it and want poplog to go into the default directory (/usr/local/poplog) Option 2: ./INSTALL_EVERYTHING_WITHOUT_MOTIF > install.log If you don't have motif or don't want poplog to use it, and want poplog to go into the default directory (/usr/local/poplog). Those scripts will install poplog in /usr/local/poplog. You may not wish to do this, or you may not have super-user privileges required for doing it. In that case you can run those scripts with an optional argument specifying an alternative installation directory. E.g. if you want poplog to be installed in your directory ~/poplog, then do one of these (or change the installation directory as appropriate): Option 3: ./INSTALL_EVERYTHING_WITH_MOTIF ~/poplog > install.log Option 4: ./INSTALL_EVERYTHING_WITHOUT_MOTIF ~/poplog > install.log The directory ~/poplog will be created if it does not exist. If the directory is publicly accessible then anyone else will be able to run poplog installed in your directory, provided that they use an appropriate startup script, as explained below. The creation of directories is handled by the script INSTALL_POPLOG Read the log file with a text editor or using the command less install.log (use space bar to get each new screenful). 4. After installation is complete, read the following file to find out how to run Poplog. HOW-RUN-POPLOG.txt Note that the installation script will create two startup scripts in the startup subdirectory of the directory in which the installation script is run, i.e. startup/poplog.sh for users of bash, ksh, or sh startup/poplog for users of tcsh or csh Copy those files to another place after installation, as each time you run the installation scripts new versions of the poplog and poplog.sh files will be created, possibly specifying different installation directories. Comments and queries can be posted to this news group comp.lang.pop or to pop-forum email list AT cs.bham.ac.uk ----------------------------------------------------------------------- CHANGE NOTES Updated: 30 Nov 2004 Some of the steps previously required are replaced by running the new checking script. Updated: 6 Apr 2004 Step 1 which previously referred to the requirement for termcap has been changed to mention possible problems with X libraries. The termcap library is no longer required in linux poplog.