From: José Rafael Subía Valdez jsubiavaldez@gmail.com To: Jonathan Wilkes jancsika@yahoo.com Cc: pd-list pd-list@iem.at Sent: Thursday, April 12, 2012 6:40 PM Subject: Re: [PD] libdir question (was: Re: pduino patches on pdx)
Its adressed to hans.. but maybe.. just maybe
[declare -path name]
this should work
It works if I then use [bar], but if I use [abs2/bar], it fails.
Let me see if I can clarify the question:
How do I design a library "foo" (of abstractions) so that it can use abstractions
from library "bar" if "bar" is installed to the system libdir location, but also so that it can use abstractions from "bar" when both "foo" and "bar" are shipped with the patch in its
directory?
For example, let's say my "foo" library uses some abstractions from list-abs. I'd like to
design it so that I can ship my patch with "foo" and "list-abs" included with it, but also so
that "foo" can be used by anyone who downloads it and already has list-abs installed. I
can't think of a way to do that, other than making "list-abs" a subdirectory of "foo", which is
ugly.
-Jonathan
On Thu, Apr 12, 2012 at 2:34 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Hans,
Let's say I have a patch in its own directory. In the same directory I have put two libraries that are made up solely of abstractions, in sub-directories named abs1 and abs2.
abs1/foo.pd relies on abs2/bar.pd.
What can I do in abs1/foo.pd to make sure that abs2/bar.pd is loaded? All I can think of is [../abs2/bar.pd] because [import abs2] won't find the abs2 directory on the parent directory. But there needs to be a clear way of doing this, as putting the patch and libdirs all in one directory is the safest way to ensure that one's patch will work on someone else's system.
-Jonathan
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Lic. José Rafael Subía Valdez
SoundArtist
www.facebook.com/JRafaelSubiaValdez (Public Page) www.myspace.com/joserafaelsubiavaldez https://puredata.info/author/rafasubia www.redce.org