-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL
146 lines (98 loc) · 5.59 KB
/
INSTALL
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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
Installation:
If you fetched the source tree directly from CVS, you will first have
to run the autogen.sh script to unpack the scsilib and pccts libraries
and generate all the Makefiles.
1. CONFIGURE OPTIONS
Type './configure' to run the configuration scripts. Use 'configure --help' for the list of available options, or see explanations below.
1.1. LAME support
The toc2mp3 utility requires the mp3lame library to encode its output
audio files into the MP3 format. The following options control the way
toc2mp3 is built:
--without-lame Disable building of toc2mp3.
--with-lame-include Specifies the directory containing the lame
include directory.
--with-lame-lib Specifies the directory containing mp3lame
library.
--disable-lame-test Do not run a test program that checks for the
required mp3lame library version. It will be
assumed that the correct mp3lame library is
available.
1.2. PCCTS support
Cdrdao requires PCCTS at build time to generate its TOC file parser,
but because it depends on a specific older version of it (1.33),
cdrdao includes the PCCTS 1.33 source code in its source code
distribution and will build and use it by default.
You can use the following options to use the PCCTS compiler and
libraries from an external source. We DO recommend however to use the
default version shipped with cdrdao as it works fine and has no known
bugs.
--with-pcctsbin=dir Specifies directory that contains the PCCTS
executables (default: pccts/bin)
--with-pcctsinc=dir Specifies directory that contains the PCCTS
header and source files
(default: pccts/h)
1.3. SCSI library options
Cdrdao was written to take advantage of the scsi libraries that are
part of the cdrtools project (sometimes installed as the cdrecord and
cdrecord-devel packages with some distributions). Cdrdao can be
compiled in three different modes wrt to the cdrtools libraries :
1.3.1. Using the provided cdrtools library
Che cdrdao source distribution provides a subset of the cdrtools tree
in the scsilib directory. To select it, use :
--with-scglib=pkg Use cdrtools tree provided in scsilib
directory
1.3.2. Using an external cdrtools package.
If you have the cdrtools development libraries installed on your
system, you can build cdrdoa against those rather than using the
scsilib directory. Note however that cdrdao requires specific header
files from cdrtools that are not installed by default. Currently, only
the RedHat/Fedora packaging of cdrtools (cdrecord-devel) provides the
sufficient headeres and libraries.
--with-scglib=sys Use installed cdrtools headers. Try to
autodetect the location of libscg.a and
schily/schily.h.
You can also explicitely set the location of those files with the
following options :
--with-scglib-inc=dir Use SCSI library include files from specified
directory instead from the SCSI library that
comes with the cdrdao package.
--with-scglib-lib=dir Specifies the directory that contains the SCSI
library.
This is the recommended way of building cdrdao. You want to use the
available cdrtools package provided by your distribution rather than
the one packaged with the cdrdao source code, as distribution usually
include patches and fixes than you want cdrdao to benefit
from. Unfortunately, it is currently somewhat tricky to build cdrdao
straight from a manually compiled cdrtools package (because cdrtools
doesn't really export an 'official' API or devel-like package).
1.3.3. Don't use cdrtools at all
If cdrtools is not available for your operating system, you can still
build cdrdao using a simpler direct SCSI implementation provided by
cdrdao, and currently available for Linux and FreeBSD :
--without-scglib Use a direct SCSI implementation instead of
Joerg Schilling's SCSI library. This makes only
sense if the SCSI library does not compile for
some reason. Direct SCSI implementations are
currently available for Linux and FreeBSD.
1.4. GCDMaster option
GCDMaster is written in C++ and therefore requires the Gnome/Gtk C++
bindings to build (libsigc++, gtkmm and libgnomeuimm). The packages
are available from www.gnome.org and gtkmm.sourceforge.net.
GCDMaster has the following configuration options :
--with-ogg-support Use the libogg and libvorbis libraries to add
Ogg Vorbis audio files support to GCDMaster.
--with-mp3-support Use the libmad library to add MP3 files support
to GCDMAster.
--without-xdao Disable build of gcdmaster completely.
1.5. Misc configuration options
--with-linux-qnx-sched Enables Linux QNX real time scheduling.
This will only work if your kernel is compiled
with the QNX scheduler.
--without-posix-threads Do not use posix threads for ring buffer even
if the system supports it.
2. BUILDING
Type 'make' to compile the package.
3. INSTALLATION
Type 'make install' as root to install the executables and the manual
pages under '/usr/local' or whatever was specified as the installation
prefix.