Hallo, David Kendall hat gesagt: // David Kendall wrote:

The sIgpAtch library looks great. But I am trying to run them on Pd 0.37 for windows, and I get messages like "vowel~ 0 ...couldn't create," but with all the objects. I've made sure that the search paths are in order, but I suppose I am missing something. Am I missing something?

sIgPatcH is compiled as a library (I would prefer single externals, hint, hint) so you need to add "-lib sIgpAtch" or similar.

ciao

Frank Barknecht _ ______footils.org__

Hallo, huolong@arcor.de hat gesagt: // huolong@arcor.de wrote:

i managed to compile pd from CVS. was easier than i thought ! (this was the very first time i used CVS)

now my question:

when there are some new features in the CVS version of pd, can i just get the sources again with:

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pure-data co pd

It's much easier: Just use "cvs update" in your checkout directory. You might get some messages about merged changes or such, that's why I normally keep two trees of cvs: One to compile and make minor local changes, the other for the upstream versions.

and compile it again ?

or do i have to 'deinstall' the old compiled pd first... (actually i've newer compiled pd twice, i used to update my linux more often :)

After the update, just "./configure && make && make install" it again. No need to deinstall the old version (normally).

btw. i have my sources in '/usr/local/src', is this the linux way ?

You can put it whereever you like, as long as you can remember, where you've put it. But wait, there's "locate" so you don't even need that. ;)

(why do i ask, i had to chmod this folder before the users could use it)

That's because normally only root can write below /usr. I tend to unpack Pd sources in my home directory like ~/src/pd/... because of that. (I "su" to root before doing a "make install" there.)

ciao

Frank Barknecht _ ______footils.org__

Korhan Erel wrote:

I have added "-lib sigpack" but now I get the message "load_object: Symbol "sIgpAck_setup" not found". What should I do? I'm on Windows.

read the emails ;-)

sIgPatcH is compiled as a library (I would prefer single externals, hint, hint) so you need to add "-lib sIgpAtch" or similar.

it said "-lib sIgpAtch" and not "-lib sigpack" note the upper/lower-cases! actually the "-lib" flags means 2 things: a) open the specified file (with an added suffix , like dll). since you are on windows the case of the filename doesn't matter. however there is still the 2nd thingie: b) try to execute a specially named function; this function is named <libraryname>_setup(); in your case it is sIgpAck_setup(). and although the windows filesystem is not case-sensitive (as noted above), C is, and most externals are written in C (or C++ which is the same in terms of case-sensitivity) these are 2 completely different things.

mfg.a.sdr IOhannes

ciao

Hi David, after rereading the message of Iohannes, you could also try "-lib sIgpAtch". It should run on Win98 too, although this is for sure not the recommended platform.

T

----- Original Message ----- From: "David Kendall" dkendall@calarts.edu To: "IOhannes zmoelnig" zmoelnig@iem.kug.ac.at Cc: pd-list@iem.kug.ac.at Sent: Tuesday, December 23, 2003 9:16 PM Subject: Re: [PD] Re: [PD-announce] sIgpAck 0.02 for win32

Now when I add the flag -lib sIgpAck_setup() when I load Pd-0.37 (on windows), I still get the message sIgpAck_setup(): can't load library Is there something that needs to go between the parentheses? Is there

still

something else to try? I'm running Pd on windows98 (!!!) ... could that

have

something to do with it? David

...

it said "-lib sIgpAtch" and not "-lib sigpack" note the upper/lower-cases! actually the "-lib" flags means 2 things: a) open the specified file (with an added suffix , like dll). since you are on windows the case of the filename doesn't matter. however there is still the 2nd thingie: b) try to execute a specially named function; this function is named <libraryname>_setup(); in your case it is sIgpAck_setup(). and although the windows filesystem is not case-sensitive (as noted above), C is, and most externals are written in C (or C++ which is the same in terms of case-sensitivity) these are 2 completely different things.

mfg.a.sdr IOhannes

...

ciao

---

PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list

---

PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list

Omit the upper/lower cases and just write -lib sigpack (not patch) and it works.

-----Original Message----- From: pd-list-admin@iem.at [mailto:pd-list-admin@iem.at] On Behalf Of enrike Sent: 26 Aralık 2003 Cuma 00:03 To: pd-list@iem.kug.ac.at Subject: Re: [PD] Re: [PD-announce] sIgpAck 0.02 for win32

after rereading the message of Iohannes, you could also try "-lib sIgpAtch". It should run on Win98 too, although this is for sure not the recommended platform.

It didnt work for me on XP.

It would be great that the readme files of all the externals include some info about how to run it, sometimes theres no help at all.