<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'><div>I think that the goal here is to have Deken packages self “operational”, not needing Dlls outside its folder.</div><div><br></div><div>Here's a list of all Dlls that were used by Extended 0.44: (1)</div><div><br></div><div>Since all of these have to be included in the appropriate Deken pkg, I think its not necessary to recompile externals.</div><div><br></div><div>I understand what you mean by using vanilla`s VS, but there would be lots of cases where the Dlls have to be included because there are no substitutes in the target computer.</div><div><br></div><div>The good news is that the Dlls can be placed in the same folder as the externals (I did a couple of tests, have to make more) </div><div><br></div><div><br></div><div>(1):</div><div><br></div><div>libdca-0.dll</div><div>libdl.dll</div><div>libfftw3-3.dll</div><div>libfftw3f-3.dll</div><div>libfreetype-6.dll</div><div>libgavl-1.dll</div><div>libgcc_s_dw2-1.dll</div><div>libgnurx-0.dll</div><div>libjack.dll</div><div>libjpeg.dll</div><div>libmp3lame-0.dll</div><div>libogg-0.dll</div><div>libopenjpeg-2.dll</div><div>libpng-3.dll</div><div>libpng12-0.dll</div><div>libsndfile-1.dll</div><div>libstdc++-6.dll</div><div>libtheora-0.dll</div><div>libtheoradec-1.dll</div><div>libtheoraenc-1.dll</div><div>libtiff-3.dll</div><div>libtiffxx-3.dll</div><div>libvorbis-0.dll</div><div>libvorbisenc-2.dll</div><div>libvorbisfile-3.dll</div><div>libx264-116.dll</div><div>libz-1.dll</div><div>msvcr71.dll</div><div>pthreadGC2.dll</div><div><br></div><div><br></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><hr id="stopSpelling">From: chakekatzil@gmail.com<br>Date: Mon, 11 Jul 2016 13:49:37 -0400<br>Subject: Re: [PD] w32 Deken package issues.<br>To: lucarda27@hotmail.com<br>CC: pd-list@lists.iem.at<br><br><div dir="ltr">On Mon, Jul 11, 2016 at 12:53 PM, Lucas Cordiviola <span dir="ltr"><<a href="mailto:lucarda27@hotmail.com" target="_blank">lucarda27@hotmail.com</a>></span> wrote:<br><div class="ecxgmail_extra"><div class="ecxgmail_quote"><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr"><span><blockquote style="border:none;padding:0px;"><div><i>I see that in the svn repository, externals/Makefile calls for pthreadGC2 when building with MinGW, while Miller's pd-0.47-1 makefile.mingw calls for pthread. And the last pd-extended for Windows has only pthreadVC.dll in its bin directory.</i></div></blockquote><div><br></div></span><div>Surely extended installer placed pthreadGC2 in the system32 folder or its equivalent sysWOW64</div><span><div><br></div></span></div></div></blockquote><div><br></div><div>Yes you're right. I have pthreadGC2.dll and libpthread-2.dll in C:\Windows\SysWOW64. (On a Windows10 machine that was upgraded from Windows7).<br></div><div>I wonder if compiling the externals with VC would use the pthreadVC.dll in pd/bin. There seems to be no other copy of pthreadVC.dll on my system. As I understand it, vanilla is built with VC. In the past I built my own externals with VC. Extended used MinGW but I was never able to get a working setup myself.<br><br></div><div>Martin<br></div></div></div></div></div> </div></body>
</html>