<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">This is exactly what I was looking for Dan – it really ties it all together. Now when I refactor old patches, I’ll feel like I’m doing it right.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Phil<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Dan Wilcox <danomatika@gmail.com><br>
<b>Date: </b>Thursday, February 25, 2021 at 1:18 AM<br>
<b>To: </b>Philip Stone <pkstone@ucdavis.edu><br>
<b>Cc: </b>Pd-List <pd-list@lists.iem.at><br>
<b>Subject: </b>Re: [PD] detect dependencies from patch<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Howdy Phil,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">We are moving away from the "extra" folder and additional "standard paths" like ~/.pd-externals in favor user search paths for most use cases. This requires specifying folders, so a helper "Documents Directory"
was added, mainly for beginners and students but I find it generally useful. For those that don't, it can simply be ignored and disabled.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I think the info on this was updated in the included Pd manual by Alex, but off the top of my head the simplest explanation is the following:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">If not enabled, enable the Pd Documents Directory:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> Preferences -> Path... -> Pd Documents Directory -> Reset<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">There should now be a ~/Documents/Pd/externals folder which is also added to the user search paths.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Put external library folders in there, deken also downloads to here by default.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Note: You can of course use your own user search path and set the path deken downloads to, in which case the following info still applies.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">You can now find externals in this folder using [declare]. If you have an external called "extname" in the following folder:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> ~/Documents/Pd/externals/extname<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">It should be found by Pd with: [declare -path extname -lib extname]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The -path argument specifies search paths while -lib specifies a location to try to load compiled externals, so some externals may require both while abstraction-only externals should only require -path. More complicated
externals like Gem which also need to load addition dynamic libs should also work, although may require additional steps / folder placement.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Note: once compiled externals are found and loaded, they cannot be unloaded or reloaded.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Also, without using [declare], objects can be found in the user search paths via prepending the external's folder name: <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> [extname/foobar]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Last, if the path given to declare starts with a . or .. (ie. it's a relative path), the search mechanism only looks *relative* to the patch and does not look in further user search or standard paths. This should
help encapsulation of certain projects.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> [declare -path ./extname]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:.5in">On Feb 25, 2021, at 12:15 AM, <a href="mailto:pd-list-request@lists.iem.at">
pd-list-request@lists.iem.at</a> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica">Message: 2<br>
Date: Wed, 24 Feb 2021 15:55:06 +0000<br>
From: Philip Stone <</span><a href="mailto:pkstone@ucdavis.edu"><span style="font-size:9.0pt;font-family:Helvetica">pkstone@ucdavis.edu</span></a><span style="font-size:9.0pt;font-family:Helvetica">><br>
To: "</span><a href="mailto:pd-list@lists.iem.at"><span style="font-size:9.0pt;font-family:Helvetica">pd-list@lists.iem.at</span></a><span style="font-size:9.0pt;font-family:Helvetica">" <</span><a href="mailto:pd-list@lists.iem.at"><span style="font-size:9.0pt;font-family:Helvetica">pd-list@lists.iem.at</span></a><span style="font-size:9.0pt;font-family:Helvetica">><br>
Subject: Re: [PD] detect dependencies from patch<br>
Message-ID:<br>
<</span><a href="mailto:BYAPR08MB5589848DB50E378D344486FDA79F9@BYAPR08MB5589.namprd08.prod.outlook.com"><span style="font-size:9.0pt;font-family:Helvetica">BYAPR08MB5589848DB50E378D344486FDA79F9@BYAPR08MB5589.namprd08.prod.outlook.com</span></a><span style="font-size:9.0pt;font-family:Helvetica">><br>
<br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
I have to say that I have gotten kind of lost in the discussions about loading and declaring external libraries. I would like to embrace the current best practices, but don?t have a solid overview of the whole. Would anybody be willing to write up a summary?<br>
<br>
I think it would be an invaluable resource for new users (as well as old, like me!)<br>
<br>
<br>
Best,<br>
<br>
Phil Stone<br>
Davis, CA</span><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
</div>
</body>
</html>