[L2Ork-dev] updating cyclone

Alexandre Torres Porres porres at gmail.com
Tue Apr 18 04:14:58 UTC 2017


cool

(got your message now, haha)

2017-04-18 0:48 GMT-03:00 Jonathan Wilkes <jancsika at yahoo.com>:

> I've got a port of your scope~ version up and running now.  Just finished
> getting the color methods
> working.
>
> The port is fairly ugly-- essentially, I just copied the contiguous code
> that has sys_vgui
> calls in it and pasted it into an ifdef.  So there's a section demarcated
> as the "purr data"
> scope.c gui code, followed by another section demarcated as the "vanilla"
> code. On each
> the opposite section doesn't get compiled.
>
> Left to do:
> * replace/remove the stray sys_vgui calls in the "purr data" section
> * refactor the little external dialog api I wrote to add a dropdown list.
> (Essentially, all externals can
> use a simple dialog api so that they don't have to write any dialog code.)
>
> Then it's just a matter of testing it.
>
> Btw-- I replaced all tabs with four spaces and followed the Vanilla style
> guide. I did this because
> I had a hard time reading the code-- a lot of blocks didn't actually line
> up correctly.
>
> -Jonathan
>
> ------------------------------
> *From:* Alexandre Torres Porres <porres at gmail.com>
> *To:* l2ork-dev at disis.music.vt.edu
> *Cc:* Jonathan Wilkes <jancsika at yahoo.com>; "brbrofsvl at gmail.com" <
> brbrofsvl at gmail.com>; Derek Kwan <derek.x.kwan at gmail.com>
> *Sent:* Monday, April 17, 2017 10:07 PM
>
> *Subject:* Re: [L2Ork-dev] updating cyclone
>
> so, how did building cyclone for purr data go?
>
> I have to remind something crazy went on and I didn't get jonathan's
> messages
>
> anyway, in a week or so, we're ready to release 0.3alpha2, which could be
> available in the next Purr Data release. Any plans on when that could come
> out? We can obviously wait and get more things ready into the release, but
> I just don't wanna miss the next release.
>
> cheers
>
> 2017-04-06 16:57 GMT-03:00 katja <katjavetter at gmail.com>:
>
> On Thu, Apr 6, 2017 at 8:36 PM, Jonathan Wilkes <jancsika at yahoo.com>
> wrote:
> > [...]
> >
> >> Important: do not specify or export PD_PATH
> >> or PDDIR in this case, because these assume a tree layout with
> >> pd/bin/pd.dll, and will mess up explicit paths.
> >
> > Btw-- I don't see this documented anywhere.
>
> From description in the makefile:
>
> # PDDIR:
> # Root directory of 'portable' pd package. When defined, PDINCLUDEDIR and
> # PDBINDIR will be evaluated as $(PDDIR)/src and $(PDDIR)/bin.
>
> and:
>
> # PD_PATH:
> # Equivalent to PDDIR. Supported for compatibility with pd-extended central
> # makefile, but deprecated otherwise.
>
> I'm trying to reorganize the order of variable expansion in such a way
> that the more specific variables have precedence. Still puzzling on
> this matter.
>
> >
> > -Jonathan
> >
> >> Katja
> >
> >
> >
> >
> >
> >
> >> I imagine the problem is that we're still using the makefile.mingw
> script
> >> in pd/src, and it puts pd.dll in pd/src instead of pd/bin.  Still, the
> >> variables
> >> above should take care of that.
> >>
> >> -Jonathan
> >>
> >>> Katja
> >
> >
> ______________________________ _________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/ listinfo/l2ork-dev
> <http://disis.music.vt.edu/listinfo/l2ork-dev>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20170418/4eca8266/attachment-0001.html>


More information about the L2Ork-dev mailing list