<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div class="qtdSeparateBR"><br><br></div><div style="display: block;" id="yui_3_16_0_ym19_1_1466459184218_78936" class="yahoo_quoted"> <div id="yui_3_16_0_ym19_1_1466459184218_78935" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_ym19_1_1466459184218_78934" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_ym19_1_1466459184218_78939" dir="ltr"><font id="yui_3_16_0_ym19_1_1466459184218_78938" face="Arial" size="2"> > On Monday, June 20, 2016 5:49 PM, Albert Graef <aggraef@gmail.com> wrote:<br></font></div> <br><br> <div id="yui_3_16_0_ym19_1_1466459184218_78951" class="y_msg_container"><div id="yiv0561753239"><div id="yui_3_16_0_ym19_1_1466459184218_78950"><div id="yui_3_16_0_ym19_1_1466459184218_78949" dir="ltr"><div id="yui_3_16_0_ym19_1_1466459184218_78948" class="yiv0561753239gmail_extra"><div id="yui_3_16_0_ym19_1_1466459184218_78947" class="yiv0561753239gmail_quote">> On Mon, Jun 20, 2016 at 8:05 PM, Jonathan Wilkes <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:jancsika@yahoo.com" target="_blank" href="mailto:jancsika@yahoo.com">jancsika@yahoo.com</a>></span> wrote:<br clear="none"><blockquote id="yui_3_16_0_ym19_1_1466459184218_78946" class="yiv0561753239gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div id="yui_3_16_0_ym19_1_1466459184218_78945"><div id="yui_3_16_0_ym19_1_1466459184218_78944" style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><span></span>This is probably because the nw.js binary/libs are missing. ATM I am manually downloading the nw.js binary for the relevant architecture, un-tarring, then moving the contents into pd/nw/nw.</div></div></blockquote><div id="yui_3_16_0_ym19_1_1466459184218_79051"><br clear="none"></div><div id="yui_3_16_0_ym19_1_1466459184218_79125"><div id="yui_3_16_0_ym19_1_1466459184218_79124">> Oops, I missed that bit. Will give it another whirl. I think that the right place in <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79129">> tar_em_up to pull nw.js is where git init / update is run to fetch the <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79131">> submodules. That shouldn't be very difficult.</div><div id="yui_3_16_0_ym19_1_1466459184218_79152"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_79153">That sounds right.</div><div id="yui_3_16_0_ym19_1_1466459184218_79182"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_81803" dir="ltr">In this process I've been extremely cautious about doing anything whatsoever <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79195" dir="ltr">to the build scripts. It's the most brittle thing I've ever seen, and after more <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79196" dir="ltr">than six months I still don't have a mental model of how it works.</div><br clear="none"><div id="yui_3_16_0_ym19_1_1466459184218_79238">> Creating a proper Debian source package which can be built on the <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79285">> Launchpad servers is another matter, though, since you can't just pull <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79306">> random binary blobs during the build there. And there really doesn't seem <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79307">> to be a package for nw.js on Launchpad, only older versions of node-webkit.</div><div id="yui_3_16_0_ym19_1_1466459184218_79308"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_79309">Someone on the nw.js group said they were working on a ppa a few months <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79330" dir="ltr">back, but I haven't heard anything else about it.</div><div id="yui_3_16_0_ym19_1_1466459184218_79859" dir="ltr"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_79351" dir="ltr">The only mention of a Debian package was from me, and currently there are <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79407" dir="ltr">no takers (including me :)<br></div><div id="yui_3_16_0_ym19_1_1466459184218_79428"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_79494">> So we either need to package nw.js first, or include the nw.js binaries in the <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79495">> Debian source package (IIRC there are ways to do this, but they are a bit <br></div><div id="yui_3_16_0_ym19_1_1466459184218_79861">> awkward).</div><div id="yui_3_16_0_ym19_1_1466459184218_79931"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_81676">If packaging nw.js is something you'd like to investigate further, please do. <br></div><div id="yui_3_16_0_ym19_1_1466459184218_81698">Unfortunately a project that big is beyond my expertise.<br></div><div id="yui_3_16_0_ym19_1_1466459184218_79805"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_81699">> Arch should be easier. For one thing, there's a nw.js package in the Arch User > Repositories. And of course an AUR PKGBUILD can also just pull the <br></div><div>> upstream nw.js package without any ado.</div><div><br></div><div id="yui_3_16_0_ym19_1_1466459184218_81700">Ah, that's great.<br></div> <br clear="none"></div><blockquote class="yiv0561753239gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div><div style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div style="display:block;"><div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div><div><div><div dir="ltr"><div dir="ltr">For OSX, it's not documented at all yet. :(<br clear="none"></div></div></div></div></div></div></div></div></div></div></blockquote><div id="yui_3_16_0_ym19_1_1466459184218_81701"><br clear="none"></div><div id="yui_3_16_0_ym19_1_1466459184218_81722">> Ok, no worries. I'll take a look at the Linux side first.<br clear="none"> <br clear="none"></div><blockquote id="yui_3_16_0_ym19_1_1466459184218_81733" class="yiv0561753239gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div id="yui_3_16_0_ym19_1_1466459184218_81732"><div id="yui_3_16_0_ym19_1_1466459184218_81731" style="color:rgb(0,0,0);background-color:rgb(255,255,255);font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="yui_3_16_0_ym19_1_1466459184218_81730" style="display:block;"><div id="yui_3_16_0_ym19_1_1466459184218_81729" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="yui_3_16_0_ym19_1_1466459184218_81728" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="yui_3_16_0_ym19_1_1466459184218_81727"><div id="yui_3_16_0_ym19_1_1466459184218_81726"><div id="yui_3_16_0_ym19_1_1466459184218_81725"><div id="yui_3_16_0_ym19_1_1466459184218_81724" dir="ltr"><div id="yui_3_16_0_ym19_1_1466459184218_81723" dir="ltr">Additionally, I can't successfully build a 32-bit target on OSX, and Gem needs 32-bit to work on OSX.<br clear="none"></div></div></div></div></div></div></div></div></div></div></blockquote><div id="yui_3_16_0_ym19_1_1466459184218_81754"><br clear="none"></div><div id="yui_3_16_0_ym19_1_1466459184218_81756"><div>> Ouch. :( I think that we should just ignore that issue for now. Having a 64 bit <br></div><div id="yui_3_16_0_ym19_1_1466459184218_81755">> version without Gem on Mac is better than nothing. What's the issue with Gem <br></div><div id="yui_3_16_0_ym19_1_1466459184218_81777">> on 64 bit OSX, does it need Carbon there?</div><div id="yui_3_16_0_ym19_1_1466459184218_81798"><br></div><div id="yui_3_16_0_ym19_1_1466459184218_81799">Yes, that is my understanding.<br></div><br clear="none"></div><div><div>> BTW, maybe you could upload the a0 package for OSX to the new binary <br></div><div>> repo at <a rel="nofollow" shape="rect" target="_blank" href="https://git.purrdata.net/jwilkes/binaries">https://git.purrdata.net/jwilkes/binaries</a>, so that Mac users have at least <br></div><div>> the older version to play with for the time being?</div><div class="yiv0561753239yqt0417650484" id="yiv0561753239yqtfd08216"><div><br clear="none"></div><div>It's available-- go to git.purrdata.net and click "all".</div><div><br></div><div>-Jonathan<br clear="none"></div></div></div></div><div class="yiv0561753239yqt0417650484" id="yiv0561753239yqtfd43596"><br clear="none"></div></div><div class="yiv0561753239yqt0417650484" id="yiv0561753239yqtfd90757"><div id="yui_3_16_0_ym19_1_1466459184218_81829" class="yiv0561753239gmail_extra">Albert<br clear="all"></div><div id="yui_3_16_0_ym19_1_1466459184218_78952" class="yiv0561753239gmail_extra"><br clear="none">-- <br clear="none"><div><div dir="ltr">Dr. Albert Gr"af<br clear="none">Computer Music Research Group, JGU Mainz, Germany<br clear="none">Email: <a rel="nofollow" shape="rect" ymailto="mailto:aggraef@gmail.com" target="_blank" href="mailto:aggraef@gmail.com">aggraef@gmail.com</a><br clear="none">WWW: <a rel="nofollow" shape="rect" target="_blank" href="https://plus.google.com/+AlbertGraef">https://plus.google.com/+AlbertGraef</a></div></div>
</div></div></div></div></div><br><br></div> </div> </div> </div></div></body></html>