[PD-dev] dealing with patch dependencies (being stuck at widget's redesign)

Hans-Christoph Steiner hans at eds.org
Tue Apr 29 17:47:12 CEST 2003

I have been using the CVS compiles on Windows, Linux and MacOS X and that
has helped a lot in terms of having all of the same objects on all
platforms.  (It would be great if cyclone was in there too.)  

And now that CVS externals are starting to get made into OS packages, it
will be much easier to keep up to date.  (Debian .debs and MacOS X .pkgs,
currently, I plan on trying my hand at a Windows installer this summer,
and Nando from CCRMA has RPMs, I think).


On Tue, 29 Apr 2003, Krzysztof Czaja wrote:

> hi des1gner,
> yeah, that would be the best way.  It works in Pd, as long as the
> stuff used in a single Pd session does not come from more than one
> directory.  I mean, for example, an external, once loaded, is
> registered for good, and used in any patch, which happens to be
> loaded later -- regardless of its home directory.
> Same goes for widget type in my case, this is the point I am
> stuck in...
> However you are right.  Resolution should be directory-based, this
> is the most natural way,
> thanks,
> Krzysztof
> and sorry for my isp (having all sorts of trouble with
> chopin.edu.pl, most of the time)
> des1gner at optusnet.com.au wrote:
> ...
>  > in the max-msp-nato world it is quite common for dependencies which are
>  > patchers and  objects and files to be included in the directory which
>  > contains the patch...is this a reasonable solution for pd also?
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.kug.ac.at
> http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev


More information about the Pd-dev mailing list