Update of /cvsroot/playerstage/code/stage
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14686
Modified Files:
INSTALL bootstrap
Log Message:
tweaks for better scalability and some bugfixes
Index: bootstrap
===================================================================
RCS file: /cvsroot/playerstage/code/stage/bootstrap,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** bootstrap 21 Nov 2006 01:30:47 -0000 1.10
--- bootstrap 11 Sep 2007 01:14:18 -0000 1.11
***************
*** 5,13 ****
autoreconf -fi
-
- #set -x
- #aclocal
- #libtoolize --force
- #autoheader
- #automake --gnu --add-missing
- #autoconf
--- 5,6 ----
Index: INSTALL
===================================================================
RCS file: /cvsroot/playerstage/code/stage/INSTALL,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** INSTALL 1 Mar 2006 00:25:56 -0000 1.7
--- INSTALL 11 Sep 2007 01:14:18 -0000 1.8
***************
*** 2,7 ****
*************************
! Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 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,
! 2006 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
***************
*** 11,15 ****
==================
! These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
--- 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
***************
*** 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
--- 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
***************
*** 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.
--- 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.
***************
*** 79,83 ****
is an example:
! ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
--- 79,83 ----
is an example:
! ./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
***************
*** 88,116 ****
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
==================
! 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=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
! give `configure' the option `--exec-prefix=PREFIX', the package will
! use PREFIX 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
--- 88,114 ----
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
==================
! By default, `make install' installs the package's commands under
! `/usr/local/bin', include files under `/usr/local/include', etc. You
! can specify an installation prefix other than `/usr/local' by giving
! `configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
! pass the option `--exec-prefix=PREFIX' to `configure', the package uses
! PREFIX as the prefix for installing programs and libraries.
! Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
***************
*** 160,164 ****
If you are _building_ compiler tools for cross-compiling, you should
! use the `--target=TYPE' option to select the type of system they will
produce code for.
--- 158,162 ----
If you are _building_ compiler tools for cross-compiling, you should
! use the option `--target=TYPE' to select the type of system they will
produce code for.
***************
*** 190,196 ****
./configure CC=/usr/local2/bin/gcc
! will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
======================
--- 188,199 ----
./configure CC=/usr/local2/bin/gcc
! 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
======================
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Playerstage-commit mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/playerstage-commit
