Update of /cvsroot/playerstage/code/stage
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13371
Modified Files:
INSTALL
Log Message:
builds & runs in Linux but many bugs remain
Index: INSTALL
===================================================================
RCS file: /cvsroot/playerstage/code/stage/INSTALL,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** INSTALL 11 Sep 2007 01:14:18 -0000 1.8
--- INSTALL 19 Jan 2008 01:20:08 -0000 1.9
***************
*** 2,7 ****
*************************
! Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
! 2006 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
--- 2,7 ----
*************************
! Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
! Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
***************
*** 11,18 ****
==================
! Briefly, the shell commands `./configure; make; make install' should
! configure, build, and install this package. The following
! more-detailed instructions are generic; see the `README' file for
! instructions specific to this package.
The `configure' shell script attempts to guess correct values for
--- 11,15 ----
==================
! These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
***************
*** 27,33 ****
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
! the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
! cache files.
If you need to do unusual things to compile the package, please try
--- 24,30 ----
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
! the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
! cache files.)
If you need to do unusual things to compile the package, please try
***************
*** 39,53 ****
The file `configure.ac' (or `configure.in') is used to create
! `configure' by a program called `autoconf'. You need `configure.ac' 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.
! Running `configure' might take a while. While running, it prints
! some messages telling which features it is checking for.
2. Type `make' to compile the package.
--- 36,53 ----
The file `configure.ac' (or `configure.in') is used to create
! `configure' by a program called `autoconf'. You only need
! `configure.ac' 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.
***************
*** 79,83 ****
is an example:
! ./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
--- 79,83 ----
is an example:
! ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
***************
*** 88,100 ****
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 can use 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 `..'.
! With a non-GNU `make', it is safer 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
--- 88,102 ----
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 support 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
***************
*** 189,198 ****
causes the specified `gcc' to be used as the C compiler (unless it is
! overridden in the site shell script).
! Unfortunately, this technique does not work for `CONFIG_SHELL' due to
! an Autoconf bug. Until the bug is fixed you can use this workaround:
! CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
`configure' Invocation
--- 191,200 ----
causes the specified `gcc' to be used as the C compiler (unless it is
! overridden in the site shell script). Here is a another example:
! /bin/bash ./configure CONFIG_SHELL=/bin/bash
! Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
! configuration-related scripts to be executed by `/bin/bash'.
`configure' Invocation
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Playerstage-commit mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/playerstage-commit
