[simspark-cvs] simspark/spark INSTALL,1.1,1.2 configure.ac,1.1,1.2

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/simspark/simspark/spark
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2143

Modified Files:
	INSTALL configure.ac 
Log Message:
- added spark-config script template
- changed prefix in *-config scripts from rcssserver3d to simspark

Index: configure.ac
===================================================================
RCS file: /cvsroot/simspark/simspark/spark/configure.ac,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** configure.ac	19 Dec 2005 20:09:16 -0000	1.1
--- configure.ac	25 Dec 2005 14:55:51 -0000	1.2
***************
*** 181,185 ****
  		 oxygen/Makefile \
  		 oxygen/oxygen-config \
! 		 spark/Makefile ],
  	        [test -f salt/salt-config && chmod a+x salt/salt-config && \
  		 test -f zeitgeist/zeitgeist-config && chmod a+x zeitgeist/zeitgeist-config && \
--- 181,196 ----
  		 oxygen/Makefile \
  		 oxygen/oxygen-config \
! 		 spark/Makefile \
! 		 spark/spark-config \
! 		 plugin/Makefile \
! 		 plugin/filesystemstd/Makefile \
! 		 plugin/sceneeffector/Makefile \
! 		 plugin/inputsdl/Makefile \
!                  plugin/openglsyssdl/Makefile \
! 		 plugin/sexpparser/Makefile \
! 		 plugin/rubysceneimporter/Makefile \
! 		 plugin/sparkmonitor/Makefile \
! 		 plugin/sparkagent/Makefile \
! 	         test/coretest/Makefile ],
  	        [test -f salt/salt-config && chmod a+x salt/salt-config && \
  		 test -f zeitgeist/zeitgeist-config && chmod a+x zeitgeist/zeitgeist-config && \

Index: INSTALL
===================================================================
RCS file: /cvsroot/simspark/simspark/spark/INSTALL,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** INSTALL	19 Dec 2005 20:09:16 -0000	1.1
--- INSTALL	25 Dec 2005 14:55:51 -0000	1.2
***************
*** 1,6 ****
! Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
! Foundation, Inc.

!    This file is free documentation; the Free Software Foundation gives
  unlimited permission to copy, distribute and modify it.

--- 1,9 ----
! Installation Instructions
! *************************

! 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
  unlimited permission to copy, distribute and modify it.

***************
*** 8,12 ****
  ==================

!    These are generic installation instructions.

     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
***************
*** 68,74 ****
  =====================

!    Some systems require unusual options for compilation or linking that
! the `configure' script does not know about.  Run `./configure --help'
! for details on some of the pertinent environment variables.

     You can give `configure' initial values for configuration parameters
--- 71,77 ----
  =====================

! Some systems require unusual options for compilation or linking that the
! `configure' script does not know about.  Run `./configure --help' for
! details on some of the pertinent environment variables.

     You can give `configure' initial values for configuration parameters
***************
*** 83,87 ****
  ====================================

!    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
--- 86,90 ----
  ====================================

! 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
***************
*** 100,116 ****
  ==================

!    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.
--- 103,119 ----
  ==================

! 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
! options like `--bindir=DIR' 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.
***************
*** 123,127 ****
  =================

!    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
--- 126,130 ----
  =================

! 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
***************
*** 138,146 ****
  ==========================

!    There may be some features `configure' cannot figure out
! automatically, but needs to determine by the type of machine the package
! will run on.  Usually, assuming the package is built to be run on the
! _same_ architectures, `configure' can figure that out, but if it prints
! a message saying it cannot guess the machine type, give it the
  `--build=TYPE' option.  TYPE can either be a short name for the system
  type, such as `sun4', or a canonical name which has the form:
--- 141,149 ----
  ==========================

! There may be some features `configure' cannot figure out automatically,
! but needs to determine by the type of machine the package will run on.
! Usually, assuming the package is built to be run on the _same_
! architectures, `configure' can figure that out, but if it prints a
! message saying it cannot guess the machine type, give it the
  `--build=TYPE' option.  TYPE can either be a short name for the system
  type, such as `sun4', or a canonical name which has the form:
***************
*** 157,161 ****

     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.

--- 160,164 ----

     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.

***************
*** 168,174 ****
  ================

!    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
--- 171,177 ----
  ================

! 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
***************
*** 179,183 ****
  ==================

!    Variables not defined in a site shell script can be set in the
  environment passed to `configure'.  However, some packages may run
  configure again during the build, and the customized values of these
--- 182,186 ----
  ==================

! Variables not defined in a site shell script can be set in the
  environment passed to `configure'.  However, some packages may run
  configure again during the build, and the customized values of these
***************
*** 187,198 ****
       ./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
  ======================

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

  `--help'
--- 190,205 ----
       ./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).  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
  ======================

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

  `--help'