libburnia/legacy
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Version leap to libisoburn-0.3.7

Browse Source
This commit is contained in:
Thomas Schmitt
2009-03-16 12:07:24 +00:00
parent f8715da40e
commit b6713dccc6
10 changed files with 86 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
libisoburn/trunk/xorriso/README
View File

@ -4,7 +4,7 @@
xorriso. By Thomas Schmitt <scdbackup@gmx.net>
Integrated sub project of libburnia-project.org but also published via:
http://scdbackup.sourceforge.net/xorriso_eng.html
http://scdbackup.sourceforge.net/xorriso-0.3.5.tar.gz
http://scdbackup.sourceforge.net/xorriso-0.3.7.tar.gz
Copyright (C) 2006-2009 Thomas Schmitt, provided under GPL version 2.
------------------------------------------------------------------------------
@ -16,13 +16,15 @@ information of existing ISO images and it writes the session results to
optical media or to filesystem objects.
Vice versa xorriso is able to restore file objects from ISO 9660 filesystems.
Currently it is supported on Linux with kernels >= 2.4 and on FreeBSD versions
with ATAPI/CAM support enabled in the kernel, see atapicam(4).
A special property of xorriso is that it needs neither an external ISO 9660
formatter program nor an external burn program for CD or DVD but rather
incorporates the libraries of libburnia-project.org .
Currently it is fully supported on Linux with kernels >= 2.4 and on
FreeBSD versions with ATAPI/CAM support enabled in the kernel, see atapicam(4).
On other X/Open compliant systems there will only be POSIX i/o with disk
file objects, but no direct MMC operation on CD/DVD/BD drives.
By using this software you agree to the disclaimer at the end of this text:
"... without even the implied warranty ..."
@ -43,10 +45,10 @@ Optional at compile time are:
If they were present at compile time, then the optional libraries have to
be present at runtime, too.
Obtain xorriso-0.3.5.tar.gz, take it to a directory of your choice and do:
Obtain xorriso-0.3.7.tar.gz, take it to a directory of your choice and do:
tar xzf xorriso-0.3.5.tar.gz
cd xorriso-0.3.5
tar xzf xorriso-0.3.7.tar.gz
cd xorriso-0.3.7
Within that directory execute:
@ -86,6 +88,9 @@ development package is installed, then rather build xorriso by:
./configure --prefix=/usr --disable-libreadline
make clean ; make
Never omit the "make clean" command after switching libreadline enabling.
Other deliberate dependency reduction options of ./configure are:
--disable-libacl avoid use of ACL functions like acl_to_text()
--disable-xattr avoid use of xattr functions like listxattr()
If you want xorriso to report a "Build timestamp" with its option -version:
make buildstamped
@ -135,7 +140,8 @@ by prepending "stdio:" to the path.
Like:
xorriso -dev stdio:/dev/sdb ...more arguments...
This rule may be changed by xorriso option -drive_class.
Prefix "mmc:" causes a path to be accepted only if it is a real optical drive.
Prefix "mmc:" causes a path to be accepted only if it is a real optical drive
which is accessible by generic SCSI/MMC commands.
Testing
@ -206,9 +212,9 @@ and a matching dynamically linked xorriso binary.
This binary is leaner but depends on properly installed libraries of suitable
revision.
Dynamic library and compile time header requirements for libisoburn-0.3.5 :
- libburn.so.4 , version libburn-0.6.0 or higher
- libisofs.so.6 , version libisofs-0.6.14 or higher
Dynamic library and compile time header requirements for libisoburn-0.3.6 :
- libburn.so.4 , version libburn-0.6.4 or higher
- libisofs.so.6 , version libisofs-0.6.16 or higher
libisoburn and xorriso will not start with libraries which are older than their
headers seen at compile time. So compile in the oldest possible installation
setup unless you have reason to enforce a newer bug fix level.