<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div><div class="h5"><div><blockquote type="cite"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><div><div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Do you have access to an ARM<br> machine? If not, I could probably get one online with ssh access, if that's<br>
useful.<br> </blockquote> <br> I've mailed Joe White with the question if he can patch the code for<br> libpd and check performance on ARM. He has done some extremely popular<br> RjDj apps and needed to optimize for them as well. Think it would be<br>
good anyway to keep in touch with libpd users and app programmers<br> about this topic, even though we're in an early stage with it.<br> </blockquote> <br> <br></div> Yes definitely, we should let everyone who wants to be get involved. I am just saying with need a development platform to start with. Once that's nailed down, we can deal with more issues, like porting to libpd, dealing with externals that could be either 32-bit or 64-bit, etc.<br>
<br> I setup a nightly build on the macosx106-x86_64 and called it pd-double. Andras and r33p, if you are listening, could you run this build on your 64-bit boxes also? All you need to do is:<br> <br> ~pd/auto-build<br>
cp -a pd-extended pd-double<br> <br clear="all"></blockquote></div><br>Listening now.<br>I did:<br>$ cd ~pd/auto-build<br>$ sudo cp -a pd-extended pd-double<br>What's next? Shall I try patching or rather pull IOhannes's sources?<br>
</blockquote></div><div><br></div></div></div>If you have the run-automated-builder script in a cron job, that is all you have to do.<div><br></div><div>.hc<br><div> <span style="border-collapse:separate;border-spacing:0px 0px;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word">
<br></div></span></div></div></div></blockquote><div><br>Ah, so tomorrow a single and double precision build will automatically be made? Cool.<br><br>Also, as I was busy with my life (buying a flat) these days, and I couldn't follow the list as precisely as I wished, could you advise me what's the current best way to roll my own double precision pd? Because I would like to benchmark a fully optimised one.<br>
</div></div></blockquote></div><div><br></div></div></div><div>That would great to have those numbers. [...]<br></div></div></blockquote><div><br>Aaargh. I've arrived to the point where I have almost no functional pd on my box (with the exception of l2ork).<br>
vanilla says: "bash: /usr/bin/pd: No such file or directory" (i remember this is a known issue... for 64bit? can it be fixed by any chance?)<br>extended (latest autobuild), and the fresh-built double keep on saying "watchdog: signaling pd..."<br>
What did I mess up? Will complete removals/reinstalls help?<br></div><div> </div></div> Andras<br>