[xiph-cvs] cvs commit: vorbis-tools HACKING autogen.sh
Jeff Squyres
jsquyres at xiph.org
Thu Aug 23 10:39:56 PDT 2001
jsquyres 01/08/23 10:39:55
Modified: . autogen.sh
. autogen.sh
. autogen.sh
. autogen.sh
Added: . HACKING
. HACKING
. HACKING
. HACKING
Log:
- Minor changes to all 4 autogen.sh files (ao, off, vorbis, vorbis-tools) to
allow users to build with !(gcc && gmake) from CVS by adding the use of
the $AUTOMAKE_FLAGS environment variable. (gcc && gmake) users will notice
no difference.
- Added HACKING file to all four projects that gives a brief description on
how to build the source from CVS. Mainly: "cvs update. ./autogen.sh.
./configure. make. Oongowa."
Revision Changes Path
1.3 +2 -2 ao/autogen.sh
Index: autogen.sh
===================================================================
RCS file: /usr/local/cvsroot/ao/autogen.sh,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- autogen.sh 2000/10/31 17:59:38 1.2
+++ autogen.sh 2001/08/23 17:39:53 1.3
@@ -53,8 +53,8 @@
#autoheader
echo " libtoolize --automake"
libtoolize --automake
-echo " automake --add-missing"
-automake --add-missing
+echo " automake --add-missing $AUTOMAKE_FLAGS"
+automake --add-missing $AUTOMAKE_FLAGS
echo " autoconf"
autoconf
1.1 ao/HACKING
Index: HACKING
===================================================================
Note that these instructions are *not* necessary for distribution
tarballs; they have separate configure/build instructions.
Building this package from CVS is mainly intended for developers.
General users should obtain office distribution packages; both source
and binary distributions are available at http://www.vorbis.com/.
-----
These are *brief* instructions on how to build this package from CVS.
Yes, there are details left out.
There are generally four steps necessary when building from CVS (i.e.,
a developer's copy):
1. cvs checkout of the sources, or cvs update. RTFM from your
favorite flavor of CVS documentation; information on the xiph.org
CVS repository can be found at http://www.xiph.org/cvs.html.
2. [re-]generate files such as "configure" and "Makefile.in" with the
GNU autoconf/automake tools. Run the "autogen.sh" script to
perform this step.
*** IF YOU ARE NOT BUILDING WITH GNU MAKE *AND* GCC: you must set
the AUTOMAKE_FLAGS envirnoment variable to "--include-deps"
before running autogen.sh. For example:
csh% setenv AUTOMAKE_FLAGS --include-deps
csh% ./autogen.sh
or
sh% AUTOMAKE_FLAGS=--include-deps ./autogen.sh
3. Run configure. There are several options available; see
"./configure --help" for more information.
4. Run "make" to build the source.
In general, steps 2 and 3 need to be re-run every time any of the
following files are modified (either manually or by a cvs update):
configure.in
acinclude.m4
Running "make clean" after running steps 2 and 3 is generally also
advisable before running step 4. It isn't *always* necessary, but
unless you understand the workings of autoconf/automake, it's safest
to just do it.
1.3 +2 -2 ogg/autogen.sh
Index: autogen.sh
===================================================================
RCS file: /usr/local/cvsroot/ogg/autogen.sh,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- autogen.sh 2000/11/04 07:28:34 1.2
+++ autogen.sh 2001/08/23 17:39:54 1.3
@@ -53,8 +53,8 @@
#autoheader
echo " libtoolize --automake"
libtoolize --automake
-echo " automake --add-missing"
-automake --add-missing
+echo " automake --add-missing $AUTOMAKE_FLAGS"
+automake --add-missing $AUTOMAKE_FLAGS
echo " autoconf"
autoconf
1.1 ogg/HACKING
Index: HACKING
===================================================================
Note that these instructions are *not* necessary for distribution
tarballs; they have separate configure/build instructions.
Building this package from CVS is mainly intended for developers.
General users should obtain office distribution packages; both source
and binary distributions are available at http://www.vorbis.com/.
-----
These are *brief* instructions on how to build this package from CVS.
Yes, there are details left out.
There are generally four steps necessary when building from CVS (i.e.,
a developer's copy):
1. cvs checkout of the sources, or cvs update. RTFM from your
favorite flavor of CVS documentation; information on the xiph.org
CVS repository can be found at http://www.xiph.org/cvs.html.
2. [re-]generate files such as "configure" and "Makefile.in" with the
GNU autoconf/automake tools. Run the "autogen.sh" script to
perform this step.
*** IF YOU ARE NOT BUILDING WITH GNU MAKE *AND* GCC: you must set
the AUTOMAKE_FLAGS envirnoment variable to "--include-deps"
before running autogen.sh. For example:
csh% setenv AUTOMAKE_FLAGS --include-deps
csh% ./autogen.sh
or
sh% AUTOMAKE_FLAGS=--include-deps ./autogen.sh
3. Run configure. There are several options available; see
"./configure --help" for more information.
4. Run "make" to build the source.
In general, steps 2 and 3 need to be re-run every time any of the
following files are modified (either manually or by a cvs update):
configure.in
acinclude.m4
Running "make clean" after running steps 2 and 3 is generally also
advisable before running step 4. It isn't *always* necessary, but
unless you understand the workings of autoconf/automake, it's safest
to just do it.
1.4 +2 -2 vorbis/autogen.sh
Index: autogen.sh
===================================================================
RCS file: /usr/local/cvsroot/vorbis/autogen.sh,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- autogen.sh 2000/10/31 18:40:48 1.3
+++ autogen.sh 2001/08/23 17:39:54 1.4
@@ -53,8 +53,8 @@
#autoheader
echo " libtoolize --automake"
libtoolize --automake
-echo " automake --add-missing"
-automake --add-missing
+echo " automake --add-missing $AUTOMAKE_FLAGS"
+automake --add-missing $AUTOMAKE_FLAGS
echo " autoconf"
autoconf
1.1 vorbis/HACKING
Index: HACKING
===================================================================
Note that these instructions are *not* necessary for distribution
tarballs; they have separate configure/build instructions.
Building this package from CVS is mainly intended for developers.
General users should obtain office distribution packages; both source
and binary distributions are available at http://www.vorbis.com/.
-----
These are *brief* instructions on how to build this package from CVS.
Yes, there are details left out.
There are generally four steps necessary when building from CVS (i.e.,
a developer's copy):
1. cvs checkout of the sources, or cvs update. RTFM from your
favorite flavor of CVS documentation; information on the xiph.org
CVS repository can be found at http://www.xiph.org/cvs.html.
2. [re-]generate files such as "configure" and "Makefile.in" with the
GNU autoconf/automake tools. Run the "autogen.sh" script to
perform this step.
*** IF YOU ARE NOT BUILDING WITH GNU MAKE *AND* GCC: you must set
the AUTOMAKE_FLAGS envirnoment variable to "--include-deps"
before running autogen.sh. For example:
csh% setenv AUTOMAKE_FLAGS --include-deps
csh% ./autogen.sh
or
sh% AUTOMAKE_FLAGS=--include-deps ./autogen.sh
3. Run configure. There are several options available; see
"./configure --help" for more information.
4. Run "make" to build the source.
In general, steps 2 and 3 need to be re-run every time any of the
following files are modified (either manually or by a cvs update):
configure.in
acinclude.m4
Running "make clean" after running steps 2 and 3 is generally also
advisable before running step 4. It isn't *always* necessary, but
unless you understand the workings of autoconf/automake, it's safest
to just do it.
1.3 +2 -2 vorbis-tools/autogen.sh
Index: autogen.sh
===================================================================
RCS file: /usr/local/cvsroot/vorbis-tools/autogen.sh,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- autogen.sh 2000/10/31 19:09:23 1.2
+++ autogen.sh 2001/08/23 17:39:55 1.3
@@ -53,8 +53,8 @@
#autoheader
echo " libtoolize --automake"
libtoolize --automake
-echo " automake --add-missing"
-automake --add-missing
+echo " automake --add-missing $AUTOMAKE_FLAGS"
+automake --add-missing $AUTOMAKE_FLAGS
echo " autoconf"
autoconf
1.1 vorbis-tools/HACKING
Index: HACKING
===================================================================
Note that these instructions are *not* necessary for distribution
tarballs; they have separate configure/build instructions.
Building this package from CVS is mainly intended for developers.
General users should obtain office distribution packages; both source
and binary distributions are available at http://www.vorbis.com/.
-----
These are *brief* instructions on how to build this package from CVS.
Yes, there are details left out.
There are generally four steps necessary when building from CVS (i.e.,
a developer's copy):
1. cvs checkout of the sources, or cvs update. RTFM from your
favorite flavor of CVS documentation; information on the xiph.org
CVS repository can be found at http://www.xiph.org/cvs.html.
2. [re-]generate files such as "configure" and "Makefile.in" with the
GNU autoconf/automake tools. Run the "autogen.sh" script to
perform this step.
*** IF YOU ARE NOT BUILDING WITH GNU MAKE *AND* GCC: you must set
the AUTOMAKE_FLAGS envirnoment variable to "--include-deps"
before running autogen.sh. For example:
csh% setenv AUTOMAKE_FLAGS --include-deps
csh% ./autogen.sh
or
sh% AUTOMAKE_FLAGS=--include-deps ./autogen.sh
3. Run configure. There are several options available; see
"./configure --help" for more information.
4. Run "make" to build the source.
In general, steps 2 and 3 need to be re-run every time any of the
following files are modified (either manually or by a cvs update):
configure.in
acinclude.m4
Running "make clean" after running steps 2 and 3 is generally also
advisable before running step 4. It isn't *always* necessary, but
unless you understand the workings of autoconf/automake, it's safest
to just do it.
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'cvs-request at xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.
More information about the commits
mailing list