V GUI Library - Version 1.16

X / *nix INSTALLATION instructions

===============================================================

General instructions:

It is easiest to untar the V distribution to its own directory
on some account you wish to use to keep and maintain V. Copy
the V distribution file (usually v-1.16.tar.gz) to the parent
directory of where you want to keep it, and then ungzip and
untar the file. If you have GNU tar, you can combine these
operations by renaming the file to v-1.16.tgz. So:

     gunzip v-1.16.tar.gz
     tar xvf v-1.16.tar

-OR-

    tar xvzf v-1.16.tgz

This will produce a directory structure with /v as the base.

Then change to the /v directory, and make V using the Makefile.
The Makefile has been setup to support several platforms, including
Intel based Linux and ELF Linux, sun4 (SunOS), sgi, hpux,
aix, solaris, and bsd (FreeBSD). You can usually easily
support other platforms my modifying the file Config.mk.
IMPORTANT! These Makefiles used features supported by GNU make,
and will not work with the standard Unix make.

If you are using Linux, see the special Linux instructions below.

The normal way to build V is to first issue the appropriate
following command:

    make linux
or  make linuxelf
or  make sun4
or  make sgi
or  make hpux
or  make aix
or  make solaris
or  make bsd

The definitions used by the various make options have been
contributed by users, and may not work on all platforms of
the specified name. You may have to hand edit the makefile
to produce a platform of your own. The makefile is well
documented, and you should be able to get it modified for
your system. Please e-mail new platforms for inclusion in
future versions.

The above make will build the library (a static version),
the main V test file, the V Application Generator, and
the V icon editor. All the object code, library, and
binaries are placed in the /v hierarchy. If you want
to build some of the other samples, you have to do them
individually.

Once the V library has been built, you will usually want
to copy the files to a standard place so they will be
available system wide. For non-Linux systems, the
strategy I've used is to keep the V stuff in a
/usr/local/v hierarchy (thus, /usr/local/v/lib,
/usr/local/v/include, and /usr/local/v/bin). While not
exactly standard, this strategy allows V to be installed
with minimal impact on the standard system. At UNM, for
example, where it is impossible to get direct access to
any standard places, I got the administrators to place
a symbolic link from /usr/local/v to a directory on my
account. Thus, I can change things, add new directories,
and whatever as I need to.

To install V in the /usr/local/v hierarchy, run the
makefile like this:

    make ARCH=yourarch installv

This will create and copy all the files as needed.

*********************   V on LINUX *************************

Because Linux is the predominate platform V is being used on,
special cases have been added to the makefile to support Linux.
The makefile supports both static and shared ELF libraries.
You can build either or both. If you build both, you should build
and install the static version first, then build and install
the ELF shared version.


First, untar V. Then compile the libraries:

To make the static version:

    make linux

To make the ELF shared version:

    make linuxelf


For Linux, V will be installed in more standard places. The
libraries should be installed in /usr/lib, the include files
in /usr/include/v, and the binaries in /usr/X11/bin.

The current version of V assumes X11R6 and the standard
Xaw Athena library.

If you are going to install both static and shared versions
of the library, you should install the static version first,
and then the shared version. This will end up with the
smaller shared binaries.

To install the static version:

    make installLinux

To install the shared ELF version:

    make installLinuxElf

===============================================================

After you have installed V, you should test for a correct
build by running the V applications: v1 (the full test program),
vgen, the V application generator, and viconed, the V icon editor.