[L2Ork-dev] gui port

[Jonathan Wilkes]

    > On Tuesday, June 21, 2016 5:49 PM, Albert Graef <aggraef at gmail.com> wrote:
 

 > On Tue, Jun 21, 2016 at 4:02 AM, Jonathan Wilkes <jancsika at yahoo.com> 
> wrote:
In this process I've been extremely cautious about doing anything whatsoever 
to the build scripts.  It's the most brittle thing I've ever seen, and after more 
than six months I still don't have a mental model of how it works.

> Well, the stuff which does most of the heavy dispatching is in tar_em_up.sh, 
> packages/linux_make/Makefile and externals/Makefile, AFAICT. This could 
> really be tidied up a bit some time, but as it works, I don't consider this a high 
> priority.
There is also packages/Makefile and packages/Makefile.buildlayout.  Plus 
the miXed build nest is incomprehensible.
I agree none of that is a priority.
However, there is one thing-- I ported cyclone/Scope~.c, which uses the new 
gui API that isn't in normal Pd-l2ork.  What's the best way to handle that?

Someone on the nw.js group said they were working on a ppa a few months 
back, but I haven't heard anything else about it.

> They probably read the Ubuntu packaging guide and instantly became Arch 
> converts. :) Seriously, Debian packaging is getting old-school and horribly 
> bloated. It's a breeze for end users and a royal pita for maintainers. Arch's 
> pacman is the other way round, :) but fortunately there are nice frontends like 
> Manjaro's pamac to make it usable for Arch noobs.
Actually, I'm using pacman to build on Windows-- see the build instructions 
in README.md.
 

If packaging nw.js is something you'd like to investigate further, please do.  


> There are better things I can do to waste my time, thank you. :) My idea is to 
> just include the binary nw.js tarballs with the Debian source package and be 
> done with it. I vaguely recall that there are ways to do this, but it's been a 
> while I needed this, so I just need some time to get this sorted out.
That sounds good to me.

> Meanwhile, I modified my Arch PKGBUILD for pd-l2ork so that it works with 
> purr-data. The build goes through fine now, but I noticed that just a few 
> externals and help patches have gone missing in purr-data (see attached 
> purr-missing-externals.diff). Did you exclude these on purpose, or do I need to 
> go digging why these don't get included?
I'll investigate...
-Jonathan
 
It's available-- go to git.purrdata.net and click "all".

> Ah yes, thanks! Still need to find my way around on GitLab. :)

Cheers,
Albert

-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email:  aggraef at gmail.com
WWW:    https://plus.google.com/+AlbertGraef

  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20160621/508cacb2/attachment.html>