I built zexy from svn-repo (revision: r17214) and I have same issue as in zexy tarball release, -- I have no [pack~] and [unpack~], but if I using zexy from binary debian package (Pd-0.44.0-extended-20140130-debian-wheezy-amd64), -- then I have [pack~] and [unpack~], and because pd-extended zexy version has this object, -- I trying to build pd-extended zexy version, but I can't.
On 30 January 2014 18:03, IOhannes m zmölnig zmoelnig@iem.at wrote:
On 01/30/2014 01:43 PM, John Smith wrote:
Hello. I try to build zexy from Pd-extended_0.43.4-source.tar.bz2.
please post a complete build log (without omissions).
also, why don't you use either an svn-checkout of zexy: svn clone https://svn.code.sf.net/p/pure-data/svn/trunk/externals/zexy or a release tarball http://puredata.info/downloads/zexy/2.2.5/
afaik, the Pd-extended sources are really for building the entire Pd-extended suite (which builds zexy in a slightly different way).
fg,ar IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-01-31 12:10, John Smith wrote:
I built zexy from svn-repo (revision: r17214) and I have same issue as in zexy tarball release, -- I have no [pack~] and [unpack~], but if I using zexy from binary debian package (Pd-0.44.0-extended-20140130-debian-wheezy-amd64), -- then I have [pack~] and [unpack~], and because pd-extended zexy version has this object, -- I trying to build pd-extended zexy version, but I can't.
then you have something else wrong. [pack~] and [unpack~] *are* part of zexy-2.2.4, zexy-2.2.5 and today's zexy-svn (rev.17259). i just checked all of them.
#1) by default, zexy will build a single binary "zexy.pd_linux"; you have to load this library (e.g. "-lib zexy", or [declare -lib zexy]) in order to use any zexy objects. this is different from pd-extended, where you get multiple binary objects (e.g. "pack~.pd_linux") and you have to use [import zexy] (or add the path/to/zexy to Pd's search paths). if you want to build zexy the same way as pd-extended builds it, you ought to use the "--disable-library" flag when running "./configure" (don't forget to run "make clean" before running "make" again).
#2) i still don't really understand your error message when compiling. there is explicit code in zexy that prevents "setup" from being multiply defined. what's the output when you run the f ollowing command in the src/ subfolder? gcc -DHAVE_CONFIG_H -I. -I.. -DZEXY_LIBRARY -g -O2 -mms-bitfields 0x2e.c -fPIC -DPIC
fgsdmr IOhannes
-
IOhannes m zmoelnig -
John Smith