Hello. I'm once again trying to control my school's Moog with Pd, this time going with the serial port on my new laptop. I downloaded and compiled the [comport] external. I moved the file comport.pd_linux to /usr/local/lib/pd/extra. If I open the comport-help file, which I moved to the same folder, it opens fine. However, if I start a new patch and add a [comport] object, it is unable to load. Why does [comport] not load, while [expr] and its cousins do? Does Pd not check /usr/local/lib/pd/extra?
Thanks. Chuckk
BTW, I also tried [declare] with an absolute path, naming "-lib comport" specifically, and it wouldn't load.
On 11/5/06, Chuckk Hubbard badmuthahubbard@gmail.com wrote:
Hello. I'm once again trying to control my school's Moog with Pd, this time going with the serial port on my new laptop. I downloaded and compiled the [comport] external. I moved the file comport.pd_linux to /usr/local/lib/pd/extra. If I open the comport-help file, which I moved to the same folder, it opens fine. However, if I start a new patch and add a [comport] object, it is unable to load. Why does [comport] not load, while [expr] and its cousins do? Does Pd not check /usr/local/lib/pd/extra?
Thanks. Chuckk
-- "Far and away the best prize that life has to offer is the chance to work hard at work worth doing." -Theodore Roosevelt
hi
i think it depends on where pd itself is: if it's in /usr/local/bin it will check /usr/local/lib/pd/extra, but if it's in /usr/bin it will look in /usr/lib/pd/extra. just add /usr/local/lib/pd/extra to your path and it will always be checked.
m
Chuckk Hubbard schreef:
BTW, I also tried [declare] with an absolute path, naming "-lib comport" specifically, and it wouldn't load.
On 11/5/06, Chuckk Hubbard badmuthahubbard@gmail.com wrote:
Hello. I'm once again trying to control my school's Moog with Pd, this time going with the serial port on my new laptop. I downloaded and compiled the [comport] external. I moved the file comport.pd_linux to /usr/local/lib/pd/extra. If I open the comport-help file, which I moved to the same folder, it opens fine. However, if I start a new patch and add a [comport] object, it is unable to load. Why does [comport] not load, while [expr] and its cousins do? Does Pd not check /usr/local/lib/pd/extra?
Thanks. Chuckk
-- "Far and away the best prize that life has to offer is the chance to work hard at work worth doing." -Theodore Roosevelt
Ah, I found it. For some reason I have pd-0.40-2 in both /usr/local and in my home folder. I copied the comport files to my home folder's extra folder, and it works. Now to decide which Pd to keep...
On 11/5/06, mik mprims@skynet.be wrote:
hi
i think it depends on where pd itself is: if it's in /usr/local/bin it will check /usr/local/lib/pd/extra, but if it's in /usr/bin it will look in /usr/lib/pd/extra. just add /usr/local/lib/pd/extra to your path and it will always be checked.
m
Chuckk Hubbard schreef:
BTW, I also tried [declare] with an absolute path, naming "-lib comport" specifically, and it wouldn't load.
On 11/5/06, Chuckk Hubbard badmuthahubbard@gmail.com wrote:
Hello. I'm once again trying to control my school's Moog with Pd, this time going with the serial port on my new laptop. I downloaded and compiled the [comport] external. I moved the file comport.pd_linux to /usr/local/lib/pd/extra. If I open the comport-help file, which I moved to the same folder, it opens fine. However, if I start a new patch and add a [comport] object, it is unable to load. Why does [comport] not load, while [expr] and its cousins do? Does Pd not check /usr/local/lib/pd/extra?
Thanks. Chuckk
-- "Far and away the best prize that life has to offer is the chance to work hard at work worth doing." -Theodore Roosevelt
--
Come to think of it, wouldn't it be useful if Pd just *always* checked for extensions in the user's home folder? ~/.pd-extra, for instance.
(Whether it should be first or last on the search path, I'm not sure.)
Steve
On 11/5/06, Chuckk Hubbard badmuthahubbard@gmail.com wrote:
Ah, I found it. For some reason I have pd-0.40-2 in both /usr/local and in my home folder. I copied the comport files to my home folder's extra folder, and it works. Now to decide which Pd to keep...
Stephen Sinclair wrote:
Come to think of it, wouldn't it be useful if Pd just *always* checked for extensions in the user's home folder? ~/.pd-extra, for instance.
i don't know the benefits of such additional auto-searched folder. i am working with different pd-versions on different platforms (and architectures!) ((oops i did it again)), and your proposal adds more trouble for me...(of course i wouldn't have to use it)
nevertheless you can already do with pd what you are suggesting: just add ~/.pd-extra to your search-path in ~/.pdsettings (or ~/.pdrc);
each pd (regardless where it actually lives) will read pd-configuration file in your hoem-directory and add your path.
mfg.adsr IOhannes