Revise installation instructions and add what you need to do if you want to develop libcdio
This commit is contained in:
30
README.develop
Normal file
30
README.develop
Normal file
@@ -0,0 +1,30 @@
|
|||||||
|
Software you'll need to build a development version libcdio
|
||||||
|
- git
|
||||||
|
- autoconf (which contains programs autoconf and autoreconf)
|
||||||
|
- automake
|
||||||
|
- m4 (used by autoconf)
|
||||||
|
- texinfo (for building documentation)
|
||||||
|
|
||||||
|
This is in addition to the software needed to build starting from a the
|
||||||
|
source tar. See README.libcdio for that additional software.
|
||||||
|
|
||||||
|
The source code lives the GNU software repository https://savannah.gnu.org/
|
||||||
|
The main page Savannah page is
|
||||||
|
https://savannah.gnu.org/projects/libcdio/
|
||||||
|
|
||||||
|
If you check out the source code, you'll need git installed. See the git
|
||||||
|
tab of the libcdio project https://savannah.gnu.org/git/?group=libcdio
|
||||||
|
which has an additional link for how to get "git".
|
||||||
|
|
||||||
|
One you have git:
|
||||||
|
|
||||||
|
git clone git://git.savannah.gnu.org/libcdio.git
|
||||||
|
|
||||||
|
Change into the libcdio directory that just created and run the "autogen.sh"
|
||||||
|
shell script
|
||||||
|
|
||||||
|
cd libcdio
|
||||||
|
sh ./autogen.sh
|
||||||
|
|
||||||
|
Please see README.libcdio and follow those instructions starting at step 3.
|
||||||
|
Normally autogen doesn't
|
||||||
@@ -1,13 +1,31 @@
|
|||||||
If you check out the source from CVS run
|
See README.develop if you plan use the git or development version.
|
||||||
./autogen.sh then follow as below, except you don't need to run
|
|
||||||
./configure.
|
|
||||||
|
|
||||||
To compile the source:
|
0. To compile the source, you'll need a POSIX shell and utilites (sh,
|
||||||
|
sed, grep, cat), an ANSI C compiler like gcc, and a POSIX "make"
|
||||||
|
program like GNU make. You may also want to have "libtool" installed
|
||||||
|
for building portable shared libraries.
|
||||||
|
|
||||||
|
1. Uncompress and unpack the source code using for example "tar". Recent
|
||||||
|
versions of GNU tar can do this in one step like this:
|
||||||
|
tar -xpf libcdio-*.bz # or libcdio-*.gz
|
||||||
|
|
||||||
|
2. Go into the directory, run "configure" followed by "make":
|
||||||
|
|
||||||
|
cd libcdio-*
|
||||||
|
sh ./configure MAKE=gmake
|
||||||
|
|
||||||
|
3. If step 2 works, Now compile everything:
|
||||||
|
|
||||||
./configure MAKE=gmake
|
|
||||||
make
|
make
|
||||||
|
|
||||||
|
4. Run the regression tests if you want:
|
||||||
|
|
||||||
make check
|
make check
|
||||||
make install # may have to do this as root
|
|
||||||
|
5. Install. If the preceeding steps were successful:
|
||||||
|
|
||||||
|
make install # you may have to do this as root
|
||||||
|
# or "sudo make install"
|
||||||
|
|
||||||
|
|
||||||
If you have problems linking libcdio or libiso9660, see the BSD
|
If you have problems linking libcdio or libiso9660, see the BSD
|
||||||
@@ -100,5 +118,3 @@ seems to lag behind.
|
|||||||
|
|
||||||
Of late FreeBSD folks have been pretty good about testing new releases
|
Of late FreeBSD folks have been pretty good about testing new releases
|
||||||
and reporting problems.
|
and reporting problems.
|
||||||
|
|
||||||
$Id: README.libcdio,v 1.12 2008/03/22 22:51:30 rocky Exp $
|
|
||||||
|
|||||||
Reference in New Issue
Block a user