ok your two lines of code work, but they just give me the
file.pd_linux. how do i get the .pd file out of it so i can actually use my external? and do i need to place my files in any certain pd directory? thanks,
scott
On Wed, 24 Jul 2002, Bryan Jurish wrote:
argh!
sorry, i sent my last mail last night at 2am, and just realized it won't work that way -- maybe Andrew's example Makefile solved your problem, but i just realized that my gcc command line wasn't entirely kosher -- its argument should really be the '.o' file and not the '.c' file, so:
bash$ gcc -c -o myfile.o myfile.c bash$ gcc -shared -export_dynamic -o myfile.pd_linux myfile.o
... the additional flags and the 'strip' in Andrew's Makefile are probably also a good idea.
have you had a look at Johannes' pd-external-HOWTO? i've found it very useful: http://iem.kug.ac.at/pd/externals-HOWTO
marmosets, Bryan
On 23 July 2002 at 17:27:39, J. Scott Hildebrand wrote:
then what do i do? i can get the executable file from the object file, but from then on i don't know what to do to create the library or .pd file. thanks,
scottOn Wed, 24 Jul 2002, Bryan Jurish wrote:
[snip]
bash$ gcc -Wall -o myextern.pd_linux myextern.o
"640K ought to be enough for anybody." -- Bill Gates, 1981
you can copy the pd_linux file into your pd/extra folder (mine is /usr/local/lib/pd/extra/) or you can just run pd from the same folder as your extern with:
pd -lib file
Where "file" is the name of your extern without the .pd_linux part.
good luck. Ben
On Wed, 24 Jul 2002, J. Scott Hildebrand wrote:
ok your two lines of code work, but they just give me thefile.pd_linux. how do i get the .pd file out of it so i can actually use my external? and do i need to place my files in any certain pd directory? thanks,
scottOn Wed, 24 Jul 2002, Bryan Jurish wrote:
argh!
sorry, i sent my last mail last night at 2am, and just realized it won't work that way -- maybe Andrew's example Makefile solved your problem, but i just realized that my gcc command line wasn't entirely kosher -- its argument should really be the '.o' file and not the '.c' file, so:
bash$ gcc -c -o myfile.o myfile.c bash$ gcc -shared -export_dynamic -o myfile.pd_linux myfile.o
... the additional flags and the 'strip' in Andrew's Makefile are probably also a good idea.
have you had a look at Johannes' pd-external-HOWTO? i've found it very useful: http://iem.kug.ac.at/pd/externals-HOWTO
marmosets, Bryan
On 23 July 2002 at 17:27:39, J. Scott Hildebrand wrote:
then what do i do? i can get the executable file from the object file, but from then on i don't know what to do to create the library or .pd file. thanks,
scottOn Wed, 24 Jul 2002, Bryan Jurish wrote:
[snip]
bash$ gcc -Wall -o myextern.pd_linux myextern.o
"640K ought to be enough for anybody." -- Bill Gates, 1981
B. Bogart
Hi, Ben Bogart - FMPM/F1999 hat gesagt: // Ben Bogart - FMPM/F1999 wrote:
you can copy the pd_linux file into your pd/extra folder (mine is /usr/local/lib/pd/extra/) or you can just run pd from the same folder as your extern with:
pd -lib file
Where "file" is the name of your extern without the .pd_linux part.
If you have only a single .pd_linux file for a single object, and not a real library full of objects like IEMLIB or ggee, then you don't need to start with -lib. The pd_linux file just has to be in a directory inside of PD's search path, which can be set with "-path /my/extern/directory" or in the directory next to the using patch.
ciao,
Frank Barknecht _ ______footils.org__
-
Ben Bogart - FMPM/F1999 -
Frank Barknecht -
J. Scott Hildebrand