Adjustments about libisoburn and xorriso dynamic dependencies
This commit is contained in:
parent
f9ea542216
commit
9134a8d5b8
@ -128,11 +128,12 @@ second file to compare.
|
|||||||
Example: After
|
Example: After
|
||||||
xorriso ... -pathspecs on -add /=/original/dir --
|
xorriso ... -pathspecs on -add /=/original/dir --
|
||||||
mount /media/dvd
|
mount /media/dvd
|
||||||
|
cd test
|
||||||
compare tree /media/dvd with tree /original/dir :
|
compare tree /media/dvd with tree /original/dir :
|
||||||
find /original/dir -exec compare_file '{}' /original/dir /media/dvd ';' \
|
find /original/dir -exec ./compare_file '{}' /original/dir /media/dvd ';' \
|
||||||
| less
|
| less
|
||||||
and vice versa:
|
and vice versa:
|
||||||
find /media/dvd -exec compare_file '{}' /media/dvd /original/dir ';' \
|
find /media/dvd -exec ./compare_file '{}' /media/dvd /original/dir ';' \
|
||||||
| less
|
| less
|
||||||
|
|
||||||
|
|
||||||
@ -142,20 +143,25 @@ xorriso is based on libisofs which does ISO 9600 filesystem aspects and on
|
|||||||
libburn which does the input and output aspects. Parts of this foundation
|
libburn which does the input and output aspects. Parts of this foundation
|
||||||
are accessed via libisoburn, which is closely related to xorriso.
|
are accessed via libisoburn, which is closely related to xorriso.
|
||||||
|
|
||||||
libisoburn takes care for the emulation of ISO 9660 multi-session on
|
libisoburn provides two services:
|
||||||
overwriteable media or random access files. It also encapsulates the
|
- Encapsulation of coordination between libisofs and libburn.
|
||||||
coordination between libisofs and libburn.
|
- Emulation of ISO 9660 multi-session on overwriteable media
|
||||||
|
or random access files.
|
||||||
|
|
||||||
The sourcecode of all three libraries is included in the xorriso standalone
|
The sourcecode of all three libraries is included in the xorriso standalone
|
||||||
tarball.
|
tarball. It is compiled with xorriso and linked statically.
|
||||||
But you may as well get and install releases of libburn and libisofs,
|
But you may as well get and install releases of libburn and libisofs, in order
|
||||||
in order to be able to install a release of libisoburn which produces a
|
to be able to install a release of libisoburn which produces libisoburn.so.1
|
||||||
dynamically linked xorriso binary. This binary is leaner but depends on
|
and a matching dynamically linked xorriso binary.
|
||||||
properly installed libraries of suitable revision.
|
This binary is leaner but depends on properly installed libraries of suitable
|
||||||
|
revision.
|
||||||
|
|
||||||
Dynamic library requirements for libisoburn-0.1.0 :
|
Dynamic library and compile time header requirements for libisoburn-0.1.0 :
|
||||||
- libburn.so.4 , version 0.4.2 or higher
|
- libburn.so.4 , version libburn-0.4.2 or higher
|
||||||
- libisofs.so.6 , version 0.6.2 or higher
|
- libisofs.so.6 , version libisofs-0.6.2 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.
|
||||||
|
|
||||||
Standalone xorriso has less runtime dependencies and can be moved more freely.
|
Standalone xorriso has less runtime dependencies and can be moved more freely.
|
||||||
|
|
||||||
|
@ -1080,8 +1080,14 @@ subtracting already foreseeable consumption by next -commit.
|
|||||||
.TP
|
.TP
|
||||||
\fB\-cd\fR iso_rr_path
|
\fB\-cd\fR iso_rr_path
|
||||||
Change the current working directory in the emerging ISO
|
Change the current working directory in the emerging ISO
|
||||||
image as it is at the moment. This typically is prepended to iso_rr_paths
|
image as it is at the moment. This is prepended to iso_rr_paths
|
||||||
which do not begin with '/'.
|
which do not begin with '/'.
|
||||||
|
.br
|
||||||
|
It is possible to set the working directory to a path which does not exist
|
||||||
|
yet in the ISO image. The necessary parent directories will be created when
|
||||||
|
the first file object is inserted into that virtual directory.
|
||||||
|
Use -mkdir if you want to enforce the existence of the directory already at
|
||||||
|
first insertion.
|
||||||
.TP
|
.TP
|
||||||
\fB\-cdx\fR disk_path
|
\fB\-cdx\fR disk_path
|
||||||
Change the current working directory on filesystem.
|
Change the current working directory on filesystem.
|
||||||
|
Loading…
Reference in New Issue
Block a user