<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><i>There was a bug in earlier versions of Pd (up to 0.43 I think), that</i></div><div><i>Pd did not look in the same folder for a dependency.</i></div></blockquote><div><br></div><div><br></div><div>Not sure what you mean.</div><div><br></div><div>If you make an external that needs another .dll, for example an mp3 player ext, and you use an 3th party lib like lib-somthing-mp3.dll.</div><div><br></div><div>Its a Windows fact that your compiled object “pdmp3.dll” will find “lib-somthing-mp3.dll” if it is in the same dir.</div><div><br></div><div>A proof for that is that if you check “pdmp3.dll” with <a href="http://www.dependencywalker.com/">http://www.dependencywalker.com/</a> it will say it`s ok if they are both in the same dir. And it will say that it can`t find it if its not there (same dir) or on system folders.</div><div><br></div><div>Other places that the system will search are for example pd/bin but that`s out of scope for dependencywalker but you get the idea.</div><div><br></div><div><br></div><br><font face="Courier New, Courier, Monospace" size="2">Mensaje telepatico asistido por maquinas.</font><br><br><div>> To: pd-list@lists.iem.at<br>> From: thomas@residuum.org<br>> Date: Fri, 15 Jul 2016 14:10:28 +0200<br>> Subject: Re: [PD] w32 Deken package issues.<br>> <br>> On 15.07.2016 12:17, IOhannes m zmölnig wrote:<br>> > On 07/14/2016 08:17 PM, Thomas Mayer wrote:<br>> >> - I compile these dependencies (and their dependencies) in the <br>> >> resulting dlls, because there is no user-friendly way to tell<br>> >> users to download the dlls.<br>> > <br>> > hmm. i'm not sure i can follow here. i guess you meant "I link<br>> > these dependencies statically into the resulting dlls" when you<br>> > wrote "I compile these dependencies into the resulting dlls", as<br>> > there is no way to "compile" two binaries together. however, the<br>> > really unclear thing is whether you actually meant static linking<br>> > (or not).<br>> <br>> Yes, I meant staic linking.<br>> <br>> > also, what is wrong with just putting the dependency dlls *besides*<br>> > the external (as has been suggested).<br>> <br>> There was a bug in earlier versions of Pd (up to 0.43 I think), that<br>> Pd did not look in the same folder for a dependency. Before that, I<br>> had a shared library, but have removed it. But that can now safely be<br>> reverted, as I make new packages available from deken, and deken is<br>> bundled with Pd 0.47.<br>> <br>> >> - I do not know how to do it in Mac OS X, but as far as I can<br>> >> tell from pull requests that I have merged, it is more like on<br>> >> Windows than on Linux.<br>> > <br>> > i don't know about your pull requests, but OSX uses the unix way<br>> > to resolve dependencies (just like linux): the resulting binary<br>> > (your external) has a notion of where to look for a given<br>> > dependency, and if that fails it will search the system paths.<br>> <br>> The external has two shell scripts for embedding:<br>> https://github.com/residuum/PuRestJson/blob/master/embed-MacOSX-dependencies.sh<br>> https://github.com/residuum/PuRestJson/blob/master/embed-osx-dep-homebrew.sh<br>> <br>> I am not sure, if these are needed.<br>> <br>> I hope, I could make my thoughts clearer,<br>> Thomas<br>> -- <br>> "Chaney was aware that anything, however small, can get the eye of the<br>> media if it's repulsive enough." (Robert Anton Wilson - The Universe<br>> Next Door)<br>> http://www.residuum.org/<br>> <br>> _______________________________________________<br>> Pd-list@lists.iem.at mailing list<br>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list<br></div> </div></body>
</html>