[Gmyth-commits] SF.net SVN: gmyth: [853] trunk/gmyth-stream

[<me...@us...>]

Revision: 853
          http://gmyth.svn.sourceforge.net/gmyth/?rev=853&view=rev
Author:   melunko
Date:     2007-09-18 05:45:36 -0700 (Tue, 18 Sep 2007)

Log Message:
-----------
gmemcoder folder renamed to gmencoder

Added Paths:
-----------
    trunk/gmyth-stream/gmencoder/
    trunk/gmyth-stream/gmencoder/AUTHORS
    trunk/gmyth-stream/gmencoder/COPYING
    trunk/gmyth-stream/gmencoder/ChangeLog
    trunk/gmyth-stream/gmencoder/INSTALL
    trunk/gmyth-stream/gmencoder/Makefile.am
    trunk/gmyth-stream/gmencoder/NEWS
    trunk/gmyth-stream/gmencoder/README
    trunk/gmyth-stream/gmencoder/autogen.sh
    trunk/gmyth-stream/gmencoder/configure.ac
    trunk/gmyth-stream/gmencoder/m4/
    trunk/gmyth-stream/gmencoder/src/
    trunk/gmyth-stream/gmencoder/tests/

Removed Paths:
-------------
    trunk/gmyth-stream/gmemcoder/
    trunk/gmyth-stream/gmencoder/AUTHORS
    trunk/gmyth-stream/gmencoder/COPYING
    trunk/gmyth-stream/gmencoder/ChangeLog
    trunk/gmyth-stream/gmencoder/INSTALL
    trunk/gmyth-stream/gmencoder/Makefile.am
    trunk/gmyth-stream/gmencoder/NEWS
    trunk/gmyth-stream/gmencoder/README
    trunk/gmyth-stream/gmencoder/autogen.sh
    trunk/gmyth-stream/gmencoder/configure.ac
    trunk/gmyth-stream/gmencoder/m4/
    trunk/gmyth-stream/gmencoder/src/
    trunk/gmyth-stream/gmencoder/tests/

Copied: trunk/gmyth-stream/gmencoder (from rev 850, trunk/gmyth-stream/gmemcoder)

Deleted: trunk/gmyth-stream/gmencoder/AUTHORS
===================================================================

Copied: trunk/gmyth-stream/gmencoder/AUTHORS (from rev 851, trunk/gmyth-stream/gmemcoder/AUTHORS)
===================================================================

Deleted: trunk/gmyth-stream/gmencoder/COPYING
===================================================================

Copied: trunk/gmyth-stream/gmencoder/COPYING (from rev 851, trunk/gmyth-stream/gmemcoder/COPYING)
===================================================================

Deleted: trunk/gmyth-stream/gmencoder/ChangeLog
===================================================================

Copied: trunk/gmyth-stream/gmencoder/ChangeLog (from rev 851, trunk/gmyth-stream/gmemcoder/ChangeLog)
===================================================================

Deleted: trunk/gmyth-stream/gmencoder/INSTALL
===================================================================
--- trunk/gmyth-stream/gmemcoder/INSTALL	2007-09-14 20:35:12 UTC (rev 850)
+++ trunk/gmyth-stream/gmencoder/INSTALL	2007-09-18 12:45:36 UTC (rev 853)
@@ -1,236 +0,0 @@
-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.
-
-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, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
-
-   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
-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 you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
-
-   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.
-
-  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.
-
-  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.
-
-Compilers and Options
-=====================
-
-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
-by setting variables in the command line or in the environment.  Here
-is an example:
-
-     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
-
-   *Note Defining Variables::, for more details.
-
-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 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' 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.
-
-   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' 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:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS KERNEL-OS
-
-   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 machine type.
-
-   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.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-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.
-
-Defining Variables
-==================
-
-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
-variables may be lost.  In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'.  For example:
-
-     ./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'
-`-h'
-     Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`--cache-file=FILE'
-     Enable the cache: use and save the results of the tests in FILE,
-     traditionally `config.cache'.  FILE defaults to `/dev/null' to
-     disable caching.
-
-`--config-cache'
-`-C'
-     Alias for `--cache-file=config.cache'.
-
-`--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.
-
-`configure' also accepts some other, not widely useful, options.  Run
-`configure --help' for more details.
-

Copied: trunk/gmyth-stream/gmencoder/INSTALL (from rev 851, trunk/gmyth-stream/gmemcoder/INSTALL)
===================================================================
--- trunk/gmyth-stream/gmencoder/INSTALL	                        (rev 0)
+++ trunk/gmyth-stream/gmencoder/INSTALL	2007-09-18 12:45:36 UTC (rev 853)
@@ -0,0 +1,236 @@
+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.
+
+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, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   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
+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 you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   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.
+
+  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.
+
+  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.
+
+Compilers and Options
+=====================
+
+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
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+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 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' 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.
+
+   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' 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:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS KERNEL-OS
+
+   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 machine type.
+
+   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.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+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.
+
+Defining Variables
+==================
+
+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
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./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'
+`-h'
+     Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--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.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.
+

Deleted: trunk/gmyth-stream/gmencoder/Makefile.am
===================================================================
--- trunk/gmyth-stream/gmemcoder/Makefile.am	2007-09-14 20:35:12 UTC (rev 850)
+++ trunk/gmyth-stream/gmencoder/Makefile.am	2007-09-18 12:45:36 UTC (rev 853)
@@ -1,7 +0,0 @@
-SUBDIRS = src
-
-EXTRA_DIST = 			\
-	ChangeLog
-	
-DIST_SUBDIRS = 			\
-	src

Copied: trunk/gmyth-stream/gmencoder/Makefile.am (from rev 851, trunk/gmyth-stream/gmemcoder/Makefile.am)
===================================================================
--- trunk/gmyth-stream/gmencoder/Makefile.am	                        (rev 0)
+++ trunk/gmyth-stream/gmencoder/Makefile.am	2007-09-18 12:45:36 UTC (rev 853)
@@ -0,0 +1,7 @@
+SUBDIRS = src
+
+EXTRA_DIST = 			\
+	ChangeLog
+	
+DIST_SUBDIRS = 			\
+	src

Deleted: trunk/gmyth-stream/gmencoder/NEWS
===================================================================

Copied: trunk/gmyth-stream/gmencoder/NEWS (from rev 851, trunk/gmyth-stream/gmemcoder/NEWS)
===================================================================

Deleted: trunk/gmyth-stream/gmencoder/README
===================================================================

Copied: trunk/gmyth-stream/gmencoder/README (from rev 851, trunk/gmyth-stream/gmemcoder/README)
===================================================================

Deleted: trunk/gmyth-stream/gmencoder/autogen.sh
===================================================================
--- trunk/gmyth-stream/gmemcoder/autogen.sh	2007-09-14 20:35:12 UTC (rev 850)
+++ trunk/gmyth-stream/gmencoder/autogen.sh	2007-09-18 12:45:36 UTC (rev 853)
@@ -1,19 +0,0 @@
-#!/bin/sh
-# Run this to generate all the initial makefiles, etc.
-
-srcdir=`dirname $0`
-test -z "$srcdir" && srcdir=.
-
-PKG_NAME="gmemcoder"
-
-(test -f $srcdir/configure.ac) || {
-    echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
-    echo " top-level $PKG_NAME directory"
-    exit 1
-}
-
-which gnome-autogen.sh || {
-    echo "You need to install gnome-common from the GNOME CVS"
-    exit 1
-}
-REQUIRED_AUTOMAKE_VERSION=1.9 USE_GNOME2_MACROS=1 . gnome-autogen.sh

Copied: trunk/gmyth-stream/gmencoder/autogen.sh (from rev 851, trunk/gmyth-stream/gmemcoder/autogen.sh)
===================================================================
--- trunk/gmyth-stream/gmencoder/autogen.sh	                        (rev 0)
+++ trunk/gmyth-stream/gmencoder/autogen.sh	2007-09-18 12:45:36 UTC (rev 853)
@@ -0,0 +1,19 @@
+#!/bin/sh
+# Run this to generate all the initial makefiles, etc.
+
+srcdir=`dirname $0`
+test -z "$srcdir" && srcdir=.
+
+PKG_NAME="gmemcoder"
+
+(test -f $srcdir/configure.ac) || {
+    echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
+    echo " top-level $PKG_NAME directory"
+    exit 1
+}
+
+which gnome-autogen.sh || {
+    echo "You need to install gnome-common from the GNOME CVS"
+    exit 1
+}
+REQUIRED_AUTOMAKE_VERSION=1.9 USE_GNOME2_MACROS=1 . gnome-autogen.sh

Deleted: trunk/gmyth-stream/gmencoder/configure.ac
===================================================================
--- trunk/gmyth-stream/gmemcoder/configure.ac	2007-09-14 20:35:12 UTC (rev 850)
+++ trunk/gmyth-stream/gmencoder/configure.ac	2007-09-18 12:45:36 UTC (rev 853)
@@ -1,93 +0,0 @@
-#                                               -*- Autoconf -*-
-# Process this file with autoconf to produce a configure script.
-
-AC_PREREQ(2.50)
-
-AC_INIT([gmemcoder],[0.1])
-
-AC_CONFIG_MACRO_DIR([m4])
-AC_CONFIG_HEADER(config.h)
-
-AS_VERSION(gmemcoder, GMEMCODER, 0, 1, 0, 0, GMEMCODER_SVN="no", GMEMCODER_SVN="yes")
-GMEMCODER_MAJORMINOR=$GMEMCODER_VERSION.$GMEMCODER_MINOR_VERSION
-AC_SUBST(GMEMCODER_MAJORMINOR)
-
-dnl AM_MAINTAINER_MODE provides the option to enable maintainer mode
-AM_MAINTAINER_MODE
-dnl make aclocal work in maintainer mode
-AC_SUBST(ACLOCAL_AMFLAGS, "-I m4")
-
-AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
-
-# Checks for programs.
-# check for tools
-# Make sure CFLAGS is defined to stop AC_PROC_CC adding -g
-CFLAGS="$CFLAGS -Wall"
-AC_PROG_CC
-AC_PROG_LIBTOOL
-
-# Checks for libraries.
-
-# Checks for header files.
-AC_HEADER_STDC
-
-#Test if --disable-debug given
-AC_ARG_ENABLE(debug,
-	AC_HELP_STRING([--disable-debug], [enable debugging mode]))
-if test x"$enable_debug" != xno; then
-    CFLAGS="$CFLAGS -g -DMYTH_STREAM_USE_DEBUG"
-else
-    CFLAGS="$CFLAGS -O2 -DG_DISABLE_CHECKS"
-fi          
-
-
-# Checks required packages ####################################################
-###############################################################################
-
-## Check for pkgconfig ########################################################
-###############################################################################
-AC_CHECK_PROG(HAVE_PKGCONFIG, pkg-config, yes, no)
-if test "x$HAVE_PKGCONFIG" = "xno"; then
-  AC_MSG_ERROR(you need to have pkgconfig installed !)
-fi
-
-## Check for Glib2.0 ##########################################################
-###############################################################################
-PKG_CHECK_MODULES(GLIB, glib-2.0, HAVE_GLIB=yes,HAVE_GLIB=no)
-if test "x$HAVE_GLIB" = "xno"; then
-  AC_MSG_ERROR(you need glib-2.0 installed)
-fi
-AC_SUBST(GLIB_CFLAGS)
-AC_SUBST(GLIB_LIBS)
-
-## Check for GnomeVFS ##########################################################
-###############################################################################
-PKG_CHECK_MODULES(GVFS, gnome-vfs-2.0, HAVE_GVFS=yes,HAVE_GVFS=no)
-if test "x$HAVE_GVFS" = "xno"; then
-  AC_MSG_ERROR(you need gnome-vfs-2.0 installed)
-fi
-AC_SUBST(GVFS_CFLAGS)
-AC_SUBST(GVFS_LIBS)
-
-
-## Check for gst-base #########################################################
-###############################################################################
-PKG_CHECK_MODULES(GST, [gstreamer-base-0.10])
-AC_SUBST(GST_CFLAGS)
-AC_SUBST(GST_LIBS)
-
-AC_SUBST(CFLAGS)
-AC_SUBST(LDFLAGS)
-AC_SUBST(LIBS)
-
-AC_OUTPUT([
-Makefile
-src/Makefile
-])
-
-if test "x$enable_debug" != "xno"; then
-    AC_MSG_NOTICE([Debug: Enabled])
-else
-    AC_MSG_NOTICE([Debug: Disabled])
-fi          
-

Copied: trunk/gmyth-stream/gmencoder/configure.ac (from rev 851, trunk/gmyth-stream/gmemcoder/configure.ac)
===================================================================
--- trunk/gmyth-stream/gmencoder/configure.ac	                        (rev 0)
+++ trunk/gmyth-stream/gmencoder/configure.ac	2007-09-18 12:45:36 UTC (rev 853)
@@ -0,0 +1,93 @@
+#                                               -*- Autoconf -*-
+# Process this file with autoconf to produce a configure script.
+
+AC_PREREQ(2.50)
+
+AC_INIT([gmemcoder],[0.1])
+
+AC_CONFIG_MACRO_DIR([m4])
+AC_CONFIG_HEADER(config.h)
+
+AS_VERSION(gmemcoder, GMEMCODER, 0, 1, 0, 0, GMEMCODER_SVN="no", GMEMCODER_SVN="yes")
+GMEMCODER_MAJORMINOR=$GMEMCODER_VERSION.$GMEMCODER_MINOR_VERSION
+AC_SUBST(GMEMCODER_MAJORMINOR)
+
+dnl AM_MAINTAINER_MODE provides the option to enable maintainer mode
+AM_MAINTAINER_MODE
+dnl make aclocal work in maintainer mode
+AC_SUBST(ACLOCAL_AMFLAGS, "-I m4")
+
+AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
+
+# Checks for programs.
+# check for tools
+# Make sure CFLAGS is defined to stop AC_PROC_CC adding -g
+CFLAGS="$CFLAGS -Wall"
+AC_PROG_CC
+AC_PROG_LIBTOOL
+
+# Checks for libraries.
+
+# Checks for header files.
+AC_HEADER_STDC
+
+#Test if --disable-debug given
+AC_ARG_ENABLE(debug,
+	AC_HELP_STRING([--disable-debug], [enable debugging mode]))
+if test x"$enable_debug" != xno; then
+    CFLAGS="$CFLAGS -g -DMYTH_STREAM_USE_DEBUG"
+else
+    CFLAGS="$CFLAGS -O2 -DG_DISABLE_CHECKS"
+fi          
+
+
+# Checks required packages ####################################################
+###############################################################################
+
+## Check for pkgconfig ########################################################
+###############################################################################
+AC_CHECK_PROG(HAVE_PKGCONFIG, pkg-config, yes, no)
+if test "x$HAVE_PKGCONFIG" = "xno"; then
+  AC_MSG_ERROR(you need to have pkgconfig installed !)
+fi
+
+## Check for Glib2.0 ##########################################################
+###############################################################################
+PKG_CHECK_MODULES(GLIB, glib-2.0, HAVE_GLIB=yes,HAVE_GLIB=no)
+if test "x$HAVE_GLIB" = "xno"; then
+  AC_MSG_ERROR(you need glib-2.0 installed)
+fi
+AC_SUBST(GLIB_CFLAGS)
+AC_SUBST(GLIB_LIBS)
+
+## Check for GnomeVFS ##########################################################
+###############################################################################
+PKG_CHECK_MODULES(GVFS, gnome-vfs-2.0, HAVE_GVFS=yes,HAVE_GVFS=no)
+if test "x$HAVE_GVFS" = "xno"; then
+  AC_MSG_ERROR(you need gnome-vfs-2.0 installed)
+fi
+AC_SUBST(GVFS_CFLAGS)
+AC_SUBST(GVFS_LIBS)
+
+
+## Check for gst-base #########################################################
+###############################################################################
+PKG_CHECK_MODULES(GST, [gstreamer-base-0.10])
+AC_SUBST(GST_CFLAGS)
+AC_SUBST(GST_LIBS)
+
+AC_SUBST(CFLAGS)
+AC_SUBST(LDFLAGS)
+AC_SUBST(LIBS)
+
+AC_OUTPUT([
+Makefile
+src/Makefile
+])
+
+if test "x$enable_debug" != "xno"; then
+    AC_MSG_NOTICE([Debug: Enabled])
+else
+    AC_MSG_NOTICE([Debug: Disabled])
+fi          
+

Copied: trunk/gmyth-stream/gmencoder/m4 (from rev 851, trunk/gmyth-stream/gmemcoder/m4)

Copied: trunk/gmyth-stream/gmencoder/src (from rev 851, trunk/gmyth-stream/gmemcoder/src)

Copied: trunk/gmyth-stream/gmencoder/tests (from rev 851, trunk/gmyth-stream/gmemcoder/tests)


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.