From 2dd16c5ca5fe4ccfc995f23df1b752299108a488 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Thu, 19 Jun 2008 13:14:39 +0000 Subject: updated readme.txt like vincent rioux suggested; fixed configure to also search for libdmx4l (which is the library installed by he upstream dmx4linux package) svn path=/trunk/externals/iem/dmx512/; revision=10044 --- dmx512/README.txt | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) (limited to 'dmx512/README.txt') diff --git a/dmx512/README.txt b/dmx512/README.txt index 7cb93f8..3eda9d8 100644 --- a/dmx512/README.txt +++ b/dmx512/README.txt @@ -38,11 +38,14 @@ and run finally become root and do # make install +after all has gone well, load the appropriate kernel modules -load the appropriate kernel modules + +btw, it is always a good idea to read the readme that comes with dmx4linux... B. permissions +============== the dmx device-files created by udev will be owned by root.root and not be read/writeable by anyone but root. in order to use them as an ordinary user, become root and create a group @@ -55,9 +58,26 @@ the next time you load a dmx-driver if you have problems, try plugging your device out and in again +C. compiling the Pd-objects +=========================== +so now it is time to get the Pd-objects going. +for this change into the "./src" directory of the iem/dmx512/ folder +(this might well be the folder that holds this README.txt you are currently +reading) + +if you have obtained the source-code via subversion, you will first have to run +% autoconf +(this should not be needed if you downloaded the sources as a release tarball; +that is: if the person who created the tarball has not forgotten to do it for you) + +then run +% configure +% make +you should now have 2 binary files in the src/ folder called [dmxin] and [dmxout] +go on and use em! -- cgit v1.2.1