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
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
mpg123 install hints
--------------------
(This file has very long lines - die-hard terminal nostalgists can be satisfied by `fmt -s -w 75 < INSTALL | less`. I think it's better to let the reader's preference rule than to preformat the stuff to some arbitrary width.)
There are now two basic ways to get your mpg123 installation consisting of
a) the mpg123 binary file
- with libmpg123 as shared library or statically linked
- with audio output plugins, or one statically linked
b) a man page
(you may want to copy some of the documentation - README, etc - to /usr/share/doc/mpg123 or the like, too)
0. Prerequesites
You really need:
- a C compiler; we try to keep the code ANSI C89/ISO C90 compatible
gcc from 2.95 on should work, others, too - please report any issues
Actually, we have a confirmed working build (svn trunk leading to release 0.67) on SunOS 4.1.4 with gcc-2.7.0 .
- an (UNIX-like) operating system with standard tools; MinGW32 and Cygwin are working for Microsoft Windows, too.
- For the library only, you may get lucky with MSVC++ using the project files under ports/
- For other exotic platforms, see ports/
You want:
- working assembler (recent GNU binutils) if using certain CPU optimizations
- headers and lib for certain audio output drivers (libasound for alsa, sdl for sdl...)
1. New installation via GNU autotools
The GNU 3-step procedure:
./configure
make
make install
Run
./configure --help
for a list of possible parameters you can specify. The obvious are --prefix and the normal GNU autotool bunch, but others include what audio subsystem to use and what CPU optimizations to build in.
For the optimizations (decoder choice), the default on 32bit x86 systems since version 0.66 is a build that combines all possible optimizations and chooses one at runtime (see --cpu, --list-cpu and --test-cpu parameters).
Update: x86 build includes all but i586_dither, which is a bit bigger due to the dither noise; use x86_dither to get it into the bunch, too.
Another posibly important choice is --with-seektable=<number> for setting the size for the table of stored frame addresses to make seeking faster. When you want a minimal memory footprint, you can set number to 0. Seeking will always start from the beginning, then - being accurate, but rather slow, what doesn't matter if you don't use interactive seeking forth and back.
There are various library features you can leave out via --disable options (like output formats, resampling modes). Please note that this is only configured/tested for the generic (fpu) decoder, not optimized ones. Perhaps that changes in future.
2. The classic way via the provided Makefile
No, the Makefile is not provided anymore. Even if autotools is complicated, it is more cumbersome to take care of two build systems in parallel.
You can dig in SVN for MakeLegacy.sh and src/Makefile.legacy and src/config.h.legacy, if you want.
Again, to be clear: There is no classic way anymore.
3. Do something different on a special platform/compiler/...
Look into the ports/ directory for some traces of "porting" mpg123 or usually libmpg123 alone to different systems and compilers.
3a. Preparing Win32 binary packages.
Caution: You should make sure to use some gcc >= 4.2.0, even if it's still the experimental package for MinGW32.
This helps preventing incompatibilities between generated DLL files and other compilers (it's about stack alignment).
Get MinGW/MSYS installed, run the MSYS shell.
Enter the mpg123 source directory.
Execute sh ./windows-builds.sh .
After some time, you should have some relevant files under releases/ (or releases\, for Windows people;-).
You don't just get one build -- there are several variants, corresponding to what usually is to be found under http://mpg123.org/download/win32 .
4. Have fun!
These are some remarks from Michael that could still bear some relevance:
- There is currently no direct audio hardware support for the
"dec" and "generic" targets. That means that you have to use
the "-s" commandline option to write the decoded audio data
to stdout.
- On Solaris, use Sun's SparcWorks compiler ("make solaris")
if at all possible. It generates faster code than gcc, so
use gcc only if there's no other way.
- The macro "htons" causes a compiler warning in httpget.c
(at least on FreeBSD 2.1.x). This can be safely ignored.
- For Solaris 2.4: append the options "-L/usr/ucblib -lucb"
at the end of the link command line. Do this ONLY for
Solaris 2.4, NOT for Solaris 2.5 or newer versions.
- The HP-UX port might be broken. I was able to compile it
on an HP-UX 9 account, but there were some problems with
libraries on HP-UX 10. I'm not an HP expert, but perhaps
someone else can fix it.
[note: some people report NO problems also with HP-UX 10]
- IRIX: some people reported compile problems on IRIX 5.x (5.3)
but 6.x seems to compile without problems
|
