aboutsummaryrefslogtreecommitdiff
path: root/README.txt
blob: db488fe1223d24772266f5d130901c015c1e0701 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
the zexy external

general::
the zexy external is a collection of externals for miller.s.puckette's realtime-computermusic-environment called "puredata" (or abbreviated "pd")
this zexy external will be of no use, if you don't have a running version of pd on your system.
check out for http://pd.iem.at to learn more about pd and how to get it 

note: the zexy external is published under the Gnu General Public License that is included (GnuGPL.txt). some parts of the code are taken directly from the pd source-code, they, of course, fall under the license pd is published under.


installation::
linux :
change to directory source
run:
 "./configure"
 "make clean"
 "make"
 "make install"
this will install the zexy external into /usr/local/lib/pd/externs
(the path can be changed either via the "--prefix"-flag to "configure"
or by editing the makefile
alternatively you can try "make everything"
note: if you don't want the parallel-port object [lpt]
 (e.g.: because you don't have a parallel-port) you can disable it with "--disable-lpt"

win32 :
extract the zexy-0_x.zip to your pd-path (this file should be located at <mypdpath>/pd/zexy/)
execute the "z_install.bat", this should copy all necessary files to the correct places
to compile: w/ MSVC makefile.nt or zexy.dsw, or with GCC configure your pd path, eg:
./configure --prefix=/c/program/pd; make; make install

irix :
though i have physical access to both SGI's O2s and indys,
i haven't tried to compile the zexy externals there for years.
the configure-script should work here too;
if not, try "make -f makefile.irix"
Good luck !

macOS-X:
the configure-script should work here too;
if not, try "make -f makefile.darwin"


making pd run with the zexy external::
make sure, that pd will be looking at this location (add "-path <mypath>/pd/externs" either to your .pdrc or each time you execute pd)
make sure, that you somehow load the zexy external (either add "-lib zexy" (if you advised pd somehow to look at the correct place) or "-lib <myzexypath>/zexy" to your startup-script (.pdrc or whatever) or load it via the object "zexy" at runtime


authors::
this software is copyleft by iohannes m zmoelnig <zmoelnig@iem.kug.ac.at>
with some contributions by winfried ritsch, guenter geiger, miller.s.puckette and maybe some others