Hiding all non-API symbols from the linker by use of --version-script

libisoburn/trunk/README

@@ -55,11 +55,14 @@ Then become superuser and execute
     make install
 which will make available libisoburn.so.1 and the program xorriso.
 
-For the API concepts and calls see
-    ./libisoburn/libisoburn.h
-as well as
-    /usr/lib/libisofs/libisofs.h
-    /usr/lib/libburn/libburn.h
+
+By use of a version script, the libisoburn.so library exposes no other function
+names but those of the API definitions in <libsoburn/libisoburn.h> and
+<libisoburn/xorriso.h>.
+If -Wl,--version-script=... makes problems with the local compiler, then
+disable this encapsulation feature by
+    ./configure --disable-versioned-libs
+    make clean ; make
 
 
                               xorriso
@@ -103,6 +106,15 @@ if 64 KB rather than 32 KB are transmitted in each write operation.
     --enable-dvd-obs-64k
 
 
+          libisoburn, libisofs, and libburn C language API
+
+For the lower API concepts and calls see
+    ./libisoburn/libisoburn.h
+as well as
+    /usr/include/libisofs/libisofs.h
+    /usr/include/libburn/libburn.h
+
+
                       xorriso C language API
 
 Actually the dynamically linked xorriso binary is only a small start program
@@ -119,7 +131,7 @@ The header file  xorriso.h  gets installed suitable for
   #include <libisoburn/xorriso.h>
 
 So after installation of a binary libisoburn package you may find it e.g. as
-  /usr/local/include/libisoburn/xorriso.h
+  /usr/include/libisoburn/xorriso.h
 
 
                        Drives and Disk File Objects