File: HACKING

package info (click to toggle)
libao 1.2.2+20180113-1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 2,348 kB
  • sloc: sh: 11,281; ansic: 5,715; makefile: 277
file content (48 lines) | stat: -rw-r--r-- 1,721 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
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 official 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. svn checkout of the sources, or svn update.  RTFM from your
   favorite flavor of SVN documentation; information on the xiph.org
   code repository can be found at http://www.xiph.org/svn.

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 environment 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.