This file documents the installation of the Windows32 API Library.
Copyright (C) 1996 Free Software Foundation, Inc.  You may copy,
distribute, and modify it freely as long as you preserve this
copyright notice and permission notice.

Installing the Windows32 API Library
************************************

  If you just wish to use the headers and import libraries for
  writing Windows32 API applications then it is not necessary to compile
  the source code.  Maintainers of the Windows32 API Library should
  read below on how to install so that the source code can be
  compiled, and the headers and import libraries can be recreated.

  If you are installing the headers within the MediaBook environment then
  read the section below for instructions.

  To install the headers and import libraries:

     ./configure --prefix=/usr/local
     make install

  Here are more detailed instructions.

  1. Configure the package for your system.  In the directory that this
     file is in, type `./configure'.  If you're using `csh' on an old
     version of System V, you might need to type `sh configure' instead
     to prevent `csh' from trying to execute `configure' itself.

     The `configure' shell script attempts to guess correct values for
     various system-dependent variables used during compilation, and
     creates the Makefile(s) (one in each subdirectory of the source
     directory).  In some packages it creates a C header file
     containing system-dependent definitions.  It also creates a file
     `config.status' that you can run in the future to recreate the
     current configuration.

     Running `configure' takes less than a minute or two.  While it is
     running, it prints some messages that tell what it is doing.  If
     you don't want to see the messages, run `configure' with its
     standard output redirected to `/dev/null'; for example:
          ./configure >/dev/null

     To compile the package in a different directory from the one
     containing the source code, you must use a version of make that
     supports the VPATH variable, such as GNU make.  `cd' to the
     directory where you want the object files and executables to go
     and run `configure'.  `configure' automatically checks for the
     source code in the directory that `configure' is in and in `..'.
     If for some reason `configure' is not in the source code directory
     that you are configuring, then it will report that it can't find
     the source code.  In that case, run `configure' with the option
     `--srcdir=DIR', where DIR is the directory that contains the
     source code.

     By default, `make install' will install the package's files in
     /usr/local/bin, /usr/local/lib, /usr/local/man, etc.  You can
     specify an installation prefix other than /usr/local by giving
     `configure' the option `--prefix=PATH'.  Alternately, you can do
     so by giving a value for the `prefix' variable when you run
     `make', e.g.,
          make prefix=/usr/gnu

     You can specify separate installation prefixes for
     architecture-specific files and architecture-independent files.
     If you give `configure' the option `--exec_prefix=PATH' or set the
     `make' variable `exec_prefix' to PATH, the package will use PATH
     as the prefix for installing programs and libraries.  Data files
     and documentation will still use the regular prefix.  Normally,
     all files are installed using the regular prefix.

     You can tell `configure' to figure out the configuration for your
     system, and record it in `config.status', without actually
     configuring the package (creating `Makefile's and perhaps a
     configuration header file).  To do this, give `configure' the
     `--no-create' option.  Later, you can run `./config.status' to
     actually configure the package.  This option is useful mainly in
     `Makefile' rules for updating `config.status' and `Makefile'.  You
     can also give `config.status' the `--recheck' option, which makes
     it re-run `configure' with the same arguments you used before.
     This is useful if you change `configure'.

     `configure' ignores any other arguments that you give it.

     If your system requires unusual options for compilation or linking
     that `configure' doesn't know about, you can give `configure'
     initial values for some variables by setting them in the
     environment.  In Bourne-compatible shells, you can do that on the
     command line like this:
          CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure

     The `make' variables that you might want to override with
     environment variables when running `configure' are:

     (For these variables, any value given in the environment overrides
     the value that `configure' would choose:)
    `CC'
          C compiler program.  Default is `cc', or `gcc' if `gcc' is in
          your PATH.

    `INSTALL'
          Program to use to install files.  Default is `install' if you
          have it, `install.sh' otherwise.

     (For these variables, any value given in the environment is added
     to the value that `configure' chooses:)
    `DEFS'
          Configuration options, in the form `-Dfoo -Dbar ...'

    `LIBS'
          Libraries to link with, in the form `-lfoo -lbar ...'

     If you need to do unusual things to compile the package, we
     encourage you to figure out how `configure' could check whether to
     do them, and mail diffs or instructions to the address given in
     the `README' so we can include them in the next release.

  2. Type `make install' to install the import libraries, header
     files, and documentation.


Installation for maintainers of the Windows32 API Library
*********************************************************

  Here are quick and dirty instructions:

     ./configure --prefix=/usr/local
     make NATIVE_HEADERS="/msdev/include"
     make headers
     make libraries
     make install

  Here are more detailed instructions.

  1. Make sure that the native Win32 header files are located in your
     compiler's search path.  When compiling you want to make sure that
     the programs include in the native Win32 header files and NOT the
     header files that are part of this library.  Alternately, you can
     specify the directory for the native Win32 headers files by setting
     NATIVE_HEADERS variable when calling make.

  2. Install the dlltool utility program.  Currently this is available
     from Cygnus at ftp.cygnus.com; retrieve the comptools.tar.gz file
     from the most recent release of the gnu-win32 tools.  dlltool is
     used for creating the import libraries; I used the version from the
     b14 release to generate the libraries.

  3. Configure the package for your system.  In the directory that this
     file is in, type `./configure'.  If you're using `csh' on an old
     version of System V, you might need to type `sh configure' instead
     to prevent `csh' from trying to execute `configure' itself.

     The `configure' shell script attempts to guess correct values for
     various system-dependent variables used during compilation, and
     creates the Makefile(s) (one in each subdirectory of the source
     directory).  In some packages it creates a C header file
     containing system-dependent definitions.  It also creates a file
     `config.status' that you can run in the future to recreate the
     current configuration.

     Running `configure' takes less than a minute or two.  While it is
     running, it prints some messages that tell what it is doing.  If
     you don't want to see the messages, run `configure' with its
     standard output redirected to `/dev/null'; for example:
          ./configure >/dev/null

     To compile the package in a different directory from the one
     containing the source code, you must use a version of make that
     supports the VPATH variable, such as GNU make.  `cd' to the
     directory where you want the object files and executables to go
     and run `configure'.  `configure' automatically checks for the
     source code in the directory that `configure' is in and in `..'.
     If for some reason `configure' is not in the source code directory
     that you are configuring, then it will report that it can't find
     the source code.  In that case, run `configure' with the option
     `--srcdir=DIR', where DIR is the directory that contains the
     source code.

     By default, `make install' will install the package's files in
     /usr/local/bin, /usr/local/lib, /usr/local/man, etc.  You can
     specify an installation prefix other than /usr/local by giving
     `configure' the option `--prefix=PATH'.  Alternately, you can do
     so by giving a value for the `prefix' variable when you run
     `make', e.g.,
          make prefix=/usr/gnu

     You can specify separate installation prefixes for
     architecture-specific files and architecture-independent files.
     If you give `configure' the option `--exec_prefix=PATH' or set the
     `make' variable `exec_prefix' to PATH, the package will use PATH
     as the prefix for installing programs and libraries.  Data files
     and documentation will still use the regular prefix.  Normally,
     all files are installed using the regular prefix.

     You can tell `configure' to figure out the configuration for your
     system, and record it in `config.status', without actually
     configuring the package (creating `Makefile's and perhaps a
     configuration header file).  To do this, give `configure' the
     `--no-create' option.  Later, you can run `./config.status' to
     actually configure the package.  This option is useful mainly in
     `Makefile' rules for updating `config.status' and `Makefile'.  You
     can also give `config.status' the `--recheck' option, which makes
     it re-run `configure' with the same arguments you used before.
     This is useful if you change `configure'.

     `configure' ignores any other arguments that you give it.

     If your system requires unusual options for compilation or linking
     that `configure' doesn't know about, you can give `configure'
     initial values for some variables by setting them in the
     environment.  In Bourne-compatible shells, you can do that on the
     command line like this:
          CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure

     The `make' variables that you might want to override with
     environment variables when running `configure' are:

     (For these variables, any value given in the environment overrides
     the value that `configure' would choose:)
    `CC'
          C compiler program.  Default is `cc', or `gcc' if `gcc' is in
          your PATH.

    `INSTALL'
          Program to use to install files.  Default is `install' if you
          have it, `install.sh' otherwise.

     (For these variables, any value given in the environment is added
     to the value that `configure' chooses:)
    `DEFS'
          Configuration options, in the form `-Dfoo -Dbar ...'

    `LIBS'
          Libraries to link with, in the form `-lfoo -lbar ...'

     If you need to do unusual things to compile the package, we
     encourage you to figure out how `configure' could check whether to
     do them, and mail diffs or instructions to the address given in
     the `README' so we can include them in the next release.

  4. Type `make' to compile the package.  If you want, you can override
     the `make' variables `CFLAGS' and `LDFLAGS' like this:
          	make CFLAGS=-O2 LDFLAGS=-s
     You may also want to specify where to find the native Win32 header
     files if they are not in your compiler's search path:
		make NATIVE_HEADERS="/msdev/include"

  5. Type `make headers' to execute the compiled programs and recreate
     the header files in the ./Headers directory.

  6. Type `make libraries' to recreate the import libraries in the
     ./Libraries directory

  7. Type `make install' to install the import libraries, header
     files, and documentation.

  8. You can remove the program binaries and object files from the
     source directory by typing `make clean'.  To also remove the
     Makefile(s), and `config.status' (all the files that `configure'
     created), type `make distclean'.

Installing the Windows32 API Library in the MediaBook environment
*****************************************************************

The MediaBook environment under Windows NT and Window 96 utilizes the
native shell of the operating systems, so it does not require you to
have a bash or UNIX-like shell to configure and install the library.
The MediaBook environment utilizes the `configure.bat' batch file to
configure the package; it creates the Makefiles by processing the
Makefile.in's with its corresponding Makefile.sed.nt.

The MediaBook environment should have these environment variables
defined for the installation to work.

  MB_DEV  -The drive and directory of the development root.  For example
	   it may be C:\MBCD\Development; it is analogous to /usr/local
           on UNIX systems.

  MB_H    -The directory name within the development root (MB_DEV) where
           the header files are stored; e.g. Headers.

  MB_LIB  -The directory name within the development root (MB_DEV) where
           the library files are stored; this tends to be specific to
           the target operating system, e.g. Libraries\MS-WIN32.

  To install the headers and import libraries:

     configure.bat
     make install

  Here are more detailed instructions.

  1. Configure the package for your system.  In the directory that this
     file is in, type `configure.bat'.

     The `configure.bat' batch file processes the Makefile.in templates
     with the corresponding Makefile.sed.nt sed script file to produce
     the resultant Makefiles.

     By default, `make install' will install the package's header files
     int $(MB_DEV)\$(MB_H) and the library files in $(MB_DEV)\$(MB_LIB).
     You should have these environment variables defined before you 
     run `make'.  You can change the development root (MB_DEV) by
     giving a value for the `prefix' variable when you run `make', e.g.,
	make prefix=C:\MBCD\MyDevelopment

  2. Type `make install' to install the import libraries, header
     files, and documentation.
