aboutsummaryrefslogtreecommitdiffstats
path: root/INSTALL
diff options
context:
space:
mode:
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL69
1 files changed, 47 insertions, 22 deletions
diff --git a/INSTALL b/INSTALL
index a7ee64b..0d1ba36 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,34 +1,59 @@
-Compiling the package
----------------------
+howto compile and install this package
+======================================
-The driver itself is provided as patch. There are patches for both
-2.2.x and 2.4.x kernels. Apply the patch, configure the kernel,
-recompile. The 2.2.x version isn't maintained any more. The old patch
-is still there, but the latest and greatest stuff is available for 2.4.x
-only.
-A simple 'make' should compile the tools. After compiling you should
-have the following files:
+really short install instructions
+---------------------------------
- mover - a small program for testing the driver / sending commands
- to the changer
- xmover - a X11 frontend for the driver -- needs Motif.
- autojuke - a tool for using a changer with autofs.
- unload - a even smaller program to send a eject to any SCSI device
- load - (symlink to unload) sends a load instead of eject.
+ $ make
+ $ su -c "make install"
-man-pages for these utilities are available. Also have a look at the
-README for some general informations about scsi changers and about the
-driver.
-In the todo subdirectory is autojuke version with support for
-double-sided media hacked in. Drawback is that volume tag support is
-broken in this version. To be merged some day ...
+
+the more detailed version
+-------------------------
+
+Make sure you use GNU make. The file name "GNUmakefile" isn't a joke,
+this package really requires GNU make.
+
+As first step make will do some config checks on your system and write
+the results to Make.config. If you want to have a look at Make.config
+before the actual build starts you can run this step separately using
+"make config".
+
+The Makefiles use the usual GNU-ish Makefile conventions for variable
+names and default values, i.e. prefix=/usr/local, ...
+
+The values for some frequently adapted variables are initialized from
+the enviroment. Thus you can change the defaults simply by setting
+environment variables:
+
+ $ prefix="/usr"
+ $ CFLAGS="-O3 -mcpu=i686"
+ $ export prefix CFLAGS
+
+Almost any variable can be overridden on the make command line. It is
+often used this way to install into some buildroot for packaging ...
+
+ $ su -c "make DESTDIR=/tmp/buildroot install"
+
+... but it works for most other variables equally well. There are
+some exceptions through, it usually does _not_ work for CFLAGS for
+example.
+
+Try "make verbose=yes" if you want to see the complete command lines
+executed by make instead of the short messages (for trouble shooting,
+because you like this way, for whatever reason ...). This also makes
+the config checks performed by "make config" more verbose.
+
+If you don't trust my Makefiles you can run "make -n install" to see
+what "make install" would do on your system. It will produce
+human-readable output (unlike automake ...).
Have fun,
Gerd
---
+--
Gerd Knorr <kraxel@bytesex.org>