B-Toolkit Installation
Installation of the B-Toolkit Release 4.x is either from the file BT_bbb.ppppp.4.vv.tgz
(where bbb is the Motif binding type, ppppp is
the platform type and vv the Release version - for example
BT_Linux.dyn.4.0.tgz would indicate version 4.0 for Linux with the
Motif libraries dynamically bound) or from a set of floppy disks.
This document describes:
Note that gunzip is used in the installation process; if you do
not have gzip/gunzip on your system, it is available from B-Core
(UK) Limited or the ftp site from which you obtained
the installation file.
The B-Toolkit Installation Directory
The B-Toolkit installation directory should be a directory in which you
have write permission (it may be necessary to become super-user to
do this).
The top-level directory of the B-Toolkit is BKIT so if the
installation directory is, for example, /usr/local/tools/BT4 the
files described below should be copied to that directory (when the
BKIT directory will be automatically created during the installation
process) and the BKIT Environment
Variable should be set to /usr/local/tools/BT4/BKIT.
Extracting the Contents of the B-Toolkit Installation
File
The file BT_bbb.ppppp.4.vv.tgz comprises a single compressed tar
file (usually obtained by ftp from B-Core
(UK) Limited) and may be upacked into a temporary
working directory with a command like:
gunzip -c BT_bbb.ppppp.4.vv.tgz | tar xvf -
This will produce the files:
-
BT_bbb.ppppp.4.vv/READ_ME
-
BT_bbb.ppppp.4.vv/binstall
-
BT_bbb.ppppp.4.vv/bkit.tar
Note that if the directory BT_bbb.ppppp.4.vv does not exist
it is created.
Now copy the files:
into the installation directory , when installation
may proceed.
Extracting the Contents of the B-Toolkit Floppy
Disks
The floppies should be extracted into a temporary working directory ; this
process is platform-dependent ,but would typically be done under Solaris
using the Floppy File Manager and under other Unix systems
using a command like:
tar xvf /dev/fd0
This will produce the files:
-
BT_bbb.ppppp.4.vv/READ_ME
-
BT_bbb.ppppp.4.vv/binstall
-
BT_bbb.ppppp.4.vv/bkit_aa
-
BT_bbb.ppppp.4.vv/bkit_ab
-
BT_bbb.ppppp.4.vv/bkit_ac
-
...
(the exact number of bkit_a* files depends on the platform and
B-Toolkit version) . Note that if the directory BT_bbb.ppppp.4.vv
does not exist it is created.
Now copy the files:
-
binstall
-
bkit_aa
-
bkit_ab
-
bkit_ac
-
...
into the installation directory , when installation
may proceed.
Installation
Having copied the files to the installation
directory, cd to that directory and run the script
./binstall
which will build the B-Toolkit installation; the log file BT4vv.log
is created.
A single directory BKIT is created containing:
-
BDEMO
a directory containing cases studies of Abstract Machine developments.
Each demonstration has a READ_ME describing its aims, and instructions
on how to proceed.
-
BHELP
a directory containing hypertext on-line help
files.
-
BLIB
the B-Toolkit library directory.
-
BPALETTE
a directory containing on-line palette
files.
-
BPLAT
the bplatform directory.
-
BProcessInfo
the display B processes
information facility.
-
BTool
the stand-alone BToolProver
-
BTool_Tutorial
a directory containing tutorial examples for the BToolProver
-
BToolkit
the script that the user invokes to run the B-Toolkit.
-
BToolkitd
the B-Toolkit licence manager daemon.
-
BToolkitd_util
the B-Toolkit licence
manager daemon utility
-
BUnlock
the Unlock facility.
-
ErrorCodes
a file containing error codes relating
to problems encountered in running the B-Toolkit.
-
XBMotif
the B-Toolkit X resource
file.
-
XBMotif.mono
the monochrome B-Toolkit X
resource file.
The distribution does not contain the ``B
licence file", B.licence, which is necessary to run the BToolkit
daemon licence manager (and hence the B-Toolkit), and which is separately
supplied to every customer.
Installation - Sample Output
--------------------------------
Script for installation of B-Toolkit
--------------------------------
Installing B-Toolkit in:
/usr/local/tools/BT4/BKIT
concatenating ...
gunzipping ...
extracting (this may take a while) ...
Installation complete.
---------------
B-Toolkit installation log
---------------
< list of extraced files >
---------------
B-Toolkit
Information
---------------
All B-Toolkit users should set the BKIT environment variable:
setenv BKIT /usr/local/tools/BT4/BKIT
If necessary, LD_LIBRARY_PATH should include X/Motif libraries, e.g.:
setenv LD_LIBRARY_PATH /usr/lib:/usr/openwin/lib:/usr/dt/lib
---------------
The BToolkit licence daemon must be started before the B-Toolkit
will run:
/usr/local/tools/BT4/BKIT/BToolkitd \
/usr/local/tools/BT4/BKIT
However the licence file "B.licence" should first be copied into
the BKIT directory (without it the daemon will not start):
cp B.licence /usr/local/tools/BT4/BKIT
The licence file is usually despatched separately - see the
installation documentation.
---------------
Before starting the B-Toolkit, you should consult the on-line help;
it may be viewed outside the B-Toolkit through an appropriate browser:
netscape \
/usr/local/tools/BT4/BKIT/BHELP/GettingStarted.html&
Full details of the licence daemon are contained in:
/usr/local/tools/BT4/BKIT/BHELP/BToolkitd.html
---------------
Note:
Couldn't copy the XBMotif resource file into /usr/lib/X11/app-defaults;
alternatively, it may be copied into your top-level directory (it has
been left in /usr/local/tools/BT4).
---------------
The above information is contained in the file:
/usr/local/tools/BT4/BToolkit.log
Run-time Library Requirements
The B-Toolkit requires dynamic linking to various X and Motif
run-time libraries.
You can find out about the B-Toolkit's requirements for run-time libraries
by setting the BKIT
variable as described above, and issuing the command:
ldd $BKIT/BLIB/BMotif
If there are required libraries that are not found, then ask your system
administrator to help you locate them, and set the environment variable
LD_LIBRARY_PATH accordingly.
The B Licence File
The B Licence file, B.licence,
is supplied separately; it must be located in the $BKIT directory;
the toolkit will not run without it!
Running the B-Toolkit for the First Time
After setting BKIT and positioning the B Licence file as described above,
change to a convenient working directory (for example ``/fs/mydir/tmp''
) and issue the command:
$BKIT/BToolkit
The following should appear in the shell window:-
B-Toolkit
Release 4.0
Copyright(c) 1985-98 B-Core(UK) Ltd
A panel should then appear containing the text:
Create new B-Toolkit directory in:
/fs/mydir/tmp
If you respond by clicking the mouse on the Create button, the
shell window will display
Created new B-Toolkit development directory
and, after a few seconds, the main B-Toolkit Motif panel will appear on
the screen.
More information about running the B-Toolkit can be found in Getting
Started.
Errors
If the installation fails, a message similar to the following will appear.
-- Installation aborted
< reason >
After correction of the problem, the installation should be restarted,
by invoking ./binstall again.
If the following error occurs:
-- Couldn't copy XBMotif resource file into /usr/lib/X11/app-defaults
you may proceed without re-installing by copying the file $BKIT/BLIB/XBMotif
into the home directory of B-Toolkit users. However this might not work
on all systems, since it depends on the local set up, and the setting of
the X files search path; if problems persist, consult your System Administrator.
The Memory Capacity of the B-Toolkit
The toolkit uses the memory allocation routine malloc and so
its capacity is dictated by the physical memory of the machine on
which it is running; if more memory is required, it is recommended that
other processes are shut down, although it may be possible to increase the
swap space of the machine - see your System Administrator.
A full on-line help listing is available
in the Contents Page
Also available in the form of a complete
Index.
© B-Core
(UK) Limited, Last updated: 25/08/99