WARNING
=======

THIS IS AN EARLY STAGE BETA WHICH WILL UNDERGO A LOT OF CHANGES ON THE
RELEASE. PLEASE REFRAIN FROM DOING "make install" FOR NOW!

This could distribute files which may be in the way for later releases
or cause other disturbances, because this part of make has not been
undergone testing as of yet.

Basic Installation
==================

   These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  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.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  4b. Because libcddb is a library you will have to run the 'ldconfig'
     program after installation.  This will make sure that the dynamic
     linker is able to find the library when executing programs using
     libcddb.

  5. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  To also remove the
     files that `configure' created (so you can compile the package for
     a different kind of computer), type `make distclean'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Apache 2 settings
=================

For DVDs with many data (e.g. a huge synopsis or many chapters), queries 
may fail with log entries in apache's error.log similar to:

"Warning: Unknown: POST Content-Length of 23655223 bytes exceeds the limit 
of 10485760 bytes in Unknown on line 0"

To fix this, set bigger limits in php.ini file, for example:

post_max_size = 32M
upload_max_filesize = 32M

Locate the lines and change the limits. The values may vary, but 32M seem
to at least be required for the database.

Then reload apache:

service httpd reload

or 

rcapache2 restart


Windows
=======

To build under windows, either Cygwin is required (see Cygwin section 
under "Compilers and Options". To build a generic windows version (that 
does not require cywin dlls), a *nix like shell must be available to do 
the ./configure and ./make sequence.

There is a MinGW toolchain available for windows:

GNU MSYS/MinGW can be downloaded from http://www.mingw.org/wiki/MSYS.

There is an excellent guide how to install Minimum GNU for Windows (MinGW)
that can be found here:
http://blog.florianwolters.de/educational/2013/11/21/Installing-MinGW/

Different from the above guid, assuming MinGW is on c:\mingw, run these 
commands:

set MINGW_HOME=c:\mingw
PATH=%PATH%;%MINGW_HOME%\msys\1.0\bin;%MINGW_HOME%\bin

If you follow these instructions and add MinGW to your path, you can simply
start a bash shell (type bash on a command prompt).

Next mount the mingw directory as decribed on the MinGW wiki 
and run configure+make (see http://www.mingw.org/wiki/msys):

Using MSYS with MinGW

It is convenient to have your MinGW installation mounted on /mingw, since 
/mingw is on MSYS PATH by default. For this to work, just type (assuming 
MinGW is on c:\mingw):

mount c:/mingw /mingw

To install 3rd party library and applications which uses the autotools build system the following commands are often used.

./configure --prefix=/mingw
make
make install

It provides all necessary tools, including a shell prompt that can be used
to execute ./configure. This will build a "real" windows DLL that can be
used by any program code that supports using DLLs.

To be able to use the DLL, include the following DLLs:

libdvdetect-0.dll  	well, off course
libgcc_s_sjlj-1.dll  	for MinGW exception handling
libstdc++-6.dll  	the c++ stdlib
libwinpthread-1.dll	for threading

Because the C API is a wrapper around the C++ library, the c++ dll is
required in any case.

The basic set of MinGW tools required is:

* Package mingw-developer-toolkit; Class bin
* Package mingw32-base; Class bin
* Package mingw32-gcc-g++; Class bin
* Package mingw32-gcc-g++; Class dev
* Package msys-base; Class bin

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
     
Cygwin     
======

You need to install libtool. This will normally also install automake as
well, which is also needed. gcc-g++ C++ compiler is also required.

Then you should be ready to do the usual

./configure
./make -s

If this does not work, you may regenerate the whole configure script:

./aclocal
./autoconf
./autoheader
./libtoolize
./automake --add-missing -a --foreign

and then do

./configure
./make -s

Don't forget to unpack tinyxml to win\tinyxml\! The compile will otherwise
print several of these misleading errors:

xmldocparser.h:64: error: `TiXmlElement' has not been declared
xmldocparser.h:64: error: ISO C++ forbids declaration of `pRoot' with no type

This means tinyxml.h is not found.

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, 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
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

   If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
     Use and save the results of the tests in FILE instead of
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
     debugging `configure'.

`--help'
     Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`configure' also accepts some other, not widely useful, options.
