Splay Installation

I recommended you to install libpthread before installing
You can get libpthread http://adam.kaist.ac.kr/~jwj95

From this version, I uses libpthread-0.6. (may works in libpthread-0.5)

From this version, X-interface is included.
And splay_pentium is X-interface version.
If you have trouble, please use Non X-nterface version.

X-interface version wants libpthread, libqt 
  and X11 libraries WHICH IS COMPILED FOR SUPPORTING THREAD.
You can get LIBQT from http://www.troll.no/
This X-interface version is not good yet.
You can select files via xsplay -l listfile or
	xsplay /songs/*.mp3
Or, in MENU!!!

There are two way to use X-interface splay.

First way,
  First
    Replace you X11 libries with X11 libries compiled for thread
      in this package by cp xlibs/*.so* /usr/X11/lib/
    The version of X11 libraries in this package is 
      XFree-3.2 (Not 3.2A)

  Second
    cp splay_pentium /usr/local/bin/splay
    cd /usr/local/bin
    ln -s splay xsplay

    run xsplay -s /songs/*.mp*

Second way, (For those who (can't or don't want to) patch X11 libraries)
  First,
    Copy X11 libraries compiled for thread to anywhere you like
	ex) cp xlibs/*.so* /usr/local/X11Thr/
     And copy splay and xsplay like First way.

  Second,
     make script or alias. (I recommended alias)
     Enjoy

xsplay_starter
==========================================================
#!/bin/sh
export LD_PRELOAD="/usr/local/X11Thr/libX11.so.6.1:/usr/local/X11Thr/libX11ThrStub.so.6.0"
/usr/local/bin/xsplay $1 $2 $3 $4 $5 $6 $7 $8 $9 ${10} ${11} ...
==========================================================

or

alias xsplay_starter 'LD_PRELOAD="/usr/local..." /usr/local/bin/xsplay'


To compile:
	Warning:
		libQt can't be compiled by pgcc yet.

	`cd' to the directory containing the packages' source code.

	./configure  or  ./configure.more
		./configure.more may optimize more for i486
		Of course, you can use this for pentium or up.
		You can't use ./configure.more for non-intel machine.

		--with-pthread    : compile with pthread 
					(default if pthread exist)
		--without-pthread : compile without pthread
		--with-nativeasm  : compile with inline assembly for ix86
		--with-xsplay	  : make x-interface version
				    It require qt, pthread, and
				    X11 libraies compiled for thread.

	make

	make install

	then make symbolic link xsplay to splay

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

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'.

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.

`--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.


