<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 8 Oct 2013, at 16:12, Jamie Bullock <<a href="mailto:jamie@jamiebullock.com">jamie@jamiebullock.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 8 Oct 2013, at 15:37, Thomas Grill <<a href="mailto:gr@grrrr.org">gr@grrrr.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi Jamie,<div>thanks for the effort! - would you mind sending me the binary?</div><div style="">Please also let me know whether it works for your task.</div><div style=""></div></div><div class="gmail_extra"><br></div></blockquote><div><br></div><div>Hi,</div><div><br></div><div>I've uploaded the binary here: <a href="http://d.pr/f/UkwJ">http://d.pr/f/UkwJ</a></div><div><br></div><div>We're using readanysf~ for now since there are ready-built binaries for both Mac and Windows we can just drop into our deployment builds with curl.</div></div></div></blockquote><br></div><div>Just to clarify, the advantage of readanysf~ here is that it is "packaged" with the requisite dependencies. I find this very helpful, and I don't think it would take much to package up fsplay~ in a similar way i.e. with libsndfile, libvorbis or whatever zipped up in the same directory as fsplay~ with the "rpaths" in the binary modified accordingly.</div><div><br></div><div>Of course, I also appreciate you are maintaining a massive amount of externals, not just this one, so the above approach may be unfeasible. </div><div><br></div><div>Jamie</div><br></body></html>