<html><head></head><body><div class="ydp6341fce8yahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 13px;"><div></div>
<div><span style="color: rgb(38, 40, 42);">> On Sunday, May 12, 2019, 10:58:52 AM EDT, Christof Ressi <christof.ressi@gmx.at> wrote:</span><br></div></div><div id="ydp747fb2f7yahoo_quoted_7980615853" class="ydp747fb2f7yahoo_quoted"><div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div><br></div>
<div><span style="font-family: Verdana; font-size: 12px;">>> that allows it to be built both as a single binary *or* with one class per binary.</span><br></div><div><div id="ydp747fb2f7yiv2266498462"><div style="font-family:Verdana;font-size:12.0px;">
<div> </div>
<div>> ah, of course that makes sense.</div>
<div> </div>
<div>>> with multi-binary style I can do [declare -lib foo/bar] whereas with the single-binary style that won't work.</div>
<div> </div>
<div>> I'm not sure I understand. Can give an example?</div><div><br></div><div>That's the libdir prefix logic. Say I have a "foo" library where one of many binaries inside "extra/foo/" is </div><div>named bar.pd_linux. Then I can do [declare -lib foo/bar] to load that library.</div><div><br></div><div>On the other hand, if "foo" was compiled as a single binary with many classes inside it, then there is </div><div>just "extra/foo/foo.pd_linux." In that case [declare -lib foo/bar] won't work.</div><div><br></div><div>Theoretically you could have a loader branch that would look for the "foo" binary in that case, load it, and then </div><div>search for a "bar_setup" routine. But that's getting pretty damned complicated. And without a spec for </div><div>what the loader is supposed to be doing in the first place I'd be hesitant to add that.</div><div><br></div><div><br></div>
</div></div></div>
</div>
</div></body></html>