$Id: README.win32,v 1.2 2001/09/05 20:25:20 cwolf Exp $
$Name:  $

Win32 port of libao, September 2001,  Chris Wolf <cwolf@starclass.com>
===========================================================================
This is the win32 port of the libao library and example program.
It has only been tested using MSVC v6, sp5 on Windows 2000 server, but
should build on other win32 platforms as long as MCVC v6 is used.

BUILDING

  Command line build:
  Before building, "prebuild.bat" should be called to create 
  working directories. 

  The libraries and executables may be built by invoking "build_all.bat".

  Note that the makefiles are generated from the IDE, and are thus a
  reflection of the workspace and project file states.  It is strongly
  recommended to make changes via the IDE and export the makefiles,
  rather than tweaking the makefiles directly.

  IDE build:
  Load the "all.dsw" workspace.  This workspace loads and manages the
  the dependent project files.  To perform a build, from the "build"
  menu, select the "build" menu item.

INSTALLING
  The script "install.bat" can be edited to reflect your environment.
  It will copy the DLLs to the designated directory.  Also, it will copy
  the plugins to a designated directory.
  

DIRECTORIES

  Debug and release versions of both the static and dynamic (DLL) libraries
  will be created in the win32/lib directory.

  The debug and release versions of the statically and dynamically linked
  versions of the executables will be created in the following directories:

  Debug/bin/static
  Debug/bin/dynamic
  Release/bin/static
  Release/bin/dynamic

  N.B. In order to execute the dynamically linked executables, the
       corresponding DLL's must be in the PATH.  There are two options:

       1.) put the fully qualified path of "win32/lib" in the PATH.

LIBRARY NAMING CONVENTIONS

  There is an ambiguity with Microsoft's naming convention; a file with
  a "*.lib" extension could either be a static library, or a DLL export
  library, therefore the following naming convention is adopted to resolve
  the ambiguity:

  Static Library:      BASENAME_static.lib   e.g. ao_static.lib
  DLL export Library:  BASENAME.lib          e.g. ao.lib

  In addition, appending "_d" to the basename denotes a debug version of
  the library. e.g. ao_static_d.lib, ao_d.dll

  The module definition file (ao.def) does not explicitly name
  the library, to allow the linker to set the name based on the
  type of build.