<div dir="ltr"><div dir="ltr"><div>Hi Joseph,</div><div><br></div><div>thanks for testing, your feedback is very much appreciated, as usual. :)<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 14, 2020 at 1:20 PM Linux ROUEN Normandie <<a href="mailto:linux.rouen@free.fr">linux.rouen@free.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>* A side comment regarding, e.g., [image toto.png].<br><div>
Since at least 2.14.0, when you click on an embedded image into my
patches/subpatches there is anymore a surrounding box telling you
this object is selected.<br></div></div></blockquote><div><br></div><div>Yep, I can confirm that issue, but AFAICT it goes back to 2.13.0 at least. Sorry, I'm afraid that I don't have the faintest idea whether that's actually a regression or the intended behavior. ;-) Jonathan, do you know more about this change?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>* I will also test Purr Data 2.15.2 under Windows when it will be
available.<br></div></div></blockquote><div><br></div><div>Yeah, sorry for the delay. I accidentally built my testing branch first, and didn't notice until it was well underway. Right now my Windows 10 VM is still chugging along building the 64 bit package for the 2.15.2 branch. Alas, building Purr on Windows is painfully slow, especially in VirtualBox, but it'll hopefully be ready in the next 1-2 hours. I'll let you know.</div><div><br></div><div>Thanks,</div><div>Albert<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>
<br>
Best, Joseph<br>
- - - - - - - - - -<br>
</div>
<div><br>
Le 14/10/2020 à 10:23, Albert Graef a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Ok, I got that new segfault in zexy sorted out as well.</div>
<div><br>
</div>
<div> Joseph, 2.15.2 is currently building on the OBS, so expect
an update in 1-2 hours. Thanks again for reporting, and it
would be nice if you could give zexy another whirl and check
whether the issues you reported have indeed been fixed in
2.15.2. They should be. ;-) I did my best to also backport the
fixes that we previously had in the 2.2.6 zexy tree.<br>
</div>
<div><br>
</div>
<div> 2.15.2 packages for Mac and Windows should be available at
<a href="https://github.com/agraef/purr-data/releases" target="_blank">https://github.com/agraef/purr-data/releases</a>
in the course of the next 2 hours as well.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Albert</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 13, 2020 at 6:37
PM Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Just a quick heads up, as Gitlab seems to be down
again: There are still some residual issues with the
reworked zexy 2.3.1 implementation in Purr, I'm currently
working on those:</div>
<div><br>
</div>
<div>- zexy/sort not loadable due to a typo in the source. I
wonder how that slipped through IEM quality control? ;-)
Anyway, that's a really trivial issue, I already fixed
that, but still need to upload a new package.</div>
<div><br>
</div>
<div>- On *Windows only*, `make check` (and the CI) gives a
segfault somewhere in zexy (I'm not sure at present which
object causes this, or whether it's related to the
zexy/sort issue). Linux and Mac are unaffected, `make
check` works fine there.</div>
<div><br>
</div>
<div>If Gitlab remains down for an extended period, I'll
just release the fixed up zexy as 2.15.2 on the GitHub
mirror as soon as I've sorted out the Windows `make check`
issue.</div>
<div><br>
</div>
<div>Albert</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 13, 2020 at
11:08 AM Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Yep, that did it. Jonathan, can you please have a
look (i.e., review, test, and merge) <a href="https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/592" target="_blank">https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/592</a>?</div>
<div><br>
</div>
<div>That MR also backports the various bugfixes and the
hexmunger-related changes from the old version. I
*think* that I did this right, but it can't hurt to
have a second pair of eyeballs have a look.</div>
<div><br>
</div>
<div>Joseph, thanks again for reporting the issue,
here's proof that everything is back to normal again:</div>
<div>
<div><img src="cid:175274c9054cb971f161" alt="image.png" width="476" height="393">I'll
toss up a build of 2.15.2 to the preview channel
shortly, so that you can test for yourself. Note
that this will also include Ico's latest (and
somewhat experimental) changes, which are slated to
go into 2.15.2 as well, but I already tested these
myself for a bit and they seem to work ok so far.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Albert<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 13, 2020
at 2:31 AM Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Oct
12, 2020 at 10:53 PM Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">#
make-lib-executable:<br>
</blockquote>
<div><br>
</div>
<div>Oops, I overlooked that one.Thanks, I will
give it a go immediately.<br>
</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
# When this variable is defined 'yes' in your
makefile or as command argument,<br>
# Makefile.pdlibbuilder will try to build all
classes into a single library<br>
# executable (but it will force exit if
lib.setup.sources is undefined).<br>
# If your makefile defines
'make-lib-executable=yes' as the library
default,<br>
# this can still be overriden with
'make-lib-executable=no' as command argument<br>
# to build individual class executables (the
Makefile.pdlibbuilder default.)<br>
<br>
On Mon, Oct 12, 2020 at 4:25 PM Albert Graef
<<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>>
wrote:<br>
><br>
> On Mon, Oct 12, 2020 at 10:14 PM Jonathan
Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>>
wrote:<br>
>><br>
>> Our previous version of Zexy had the
option to produce both types of<br>
>> output, but it didn't use
Makefile.pdlibbuilder. You might skim that<br>
>> file to see if there's an option to
build one-file-per-class.<br>
><br>
><br>
> I already did that, but couldn't find any
such option.<br>
><br>
> Albert<br>
><br>
>><br>
>> -Jonathan<br>
>><br>
>> On Mon, Oct 12, 2020 at 4:03 PM
Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>>
wrote:<br>
>> ><br>
>> > On Mon, Oct 12, 2020 at 8:41 PM
Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>>
wrote:<br>
>> > > Whoa, that is a huge
regression and needs to be fixed.<br>
>> ><br>
>> > The only (quick) fix I see is to
unmerge<br>
>> > <a href="https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/583" rel="noreferrer" target="_blank">https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/583</a>.<br>
>> ><br>
>> > That might work for most people,
but zexy will then be completely<br>
>> > broken in the mingw64 build
again. Which means that I won't be able to<br>
>> > use zexy, because I need to be
able to run pd-faustgen2 (which<br>
>> > requires 64 bit) on Windows in
at least one of my upcoming courses.<br>
>> ><br>
>> > > namespace prefixes like
zexy/date should be supported in all the
default libs, no exceptions.<br>
>> ><br>
>> > Is there a way you can do that
if a collection of externals is<br>
>> > compiled as a library? Do we
have a working example of this in the<br>
>> > libraries that we ship? Then we
could possibly apply the same method<br>
>> > to zexy.<br>
>> ><br>
>> > > Is there a compile-time
option for Zexy to produce one-class-per-file
output, or was that removed in a newer
version?<br>
>> ><br>
>> > Not as far as I can tell -- as
you know if you read the description of<br>
>> > my MR, it uses
Makefile.pdlibbuilder now. It's hopefully
possible to<br>
>> > massage zexy/Makefile so that it
produces separate externals. I can<br>
>> > look into that as soon as I find
the time if you want.<br>
>> ><br>
>> > > Also-- Albert, did you go
through the `git log externals/zexy` to see if
we had any fixes for things that aren't
upstream? The only thing I vaguely recall had
to do with hexloader, but that my have been a
different external lib...<br>
>> ><br>
>> > No, I didn't. Most of those seem
to be about hexmunger, which the<br>
>> > library version doesn't need if
I understand correctly. The others<br>
>> > are:<br>
>> ><br>
>> > <a href="https://git.purrdata.net/jwilkes/purr-data/-/commit/5e9124e9" rel="noreferrer" target="_blank">https://git.purrdata.net/jwilkes/purr-data/-/commit/5e9124e9</a>:
Not<br>
>> > sure, code review is in order.<br>
>> ><br>
>> > <a href="https://git.purrdata.net/jwilkes/purr-data/-/commit/3cf58d708" rel="noreferrer" target="_blank">https://git.purrdata.net/jwilkes/purr-data/-/commit/3cf58d708</a>:
Not<br>
>> > sure, code review is in order.<br>
>> ><br>
>> > <a href="https://git.purrdata.net/jwilkes/purr-data/-/commit/7b3a9f539" rel="noreferrer" target="_blank">https://git.purrdata.net/jwilkes/purr-data/-/commit/7b3a9f539</a>:<br>
>> > Probably still needed, but it
won't apply without ado to the new<br>
>> > version because of code changes.<br>
>> ><br>
>> > <a href="https://git.purrdata.net/jwilkes/purr-data/-/commit/e294b129" rel="noreferrer" target="_blank">https://git.purrdata.net/jwilkes/purr-data/-/commit/e294b129</a>:
Probably<br>
>> > still needed as well, we may
just apply it anyway because it won't do<br>
>> > any harm AFAICT.<br>
>> ><br>
>> > Albert<br>
>> ><br>
>> > ><br>
>> > > -Jonathan<br>
>> > ><br>
>> > >><br>
>> > >><br>
>> > >> HTH,<br>
>> > >> Albert<br>
>> > >><br>
>> > >><br>
>> > >> On Mon, Oct 12, 2020 at
7:03 PM Linux ROUEN Normandie <<a href="mailto:linux.rouen@free.fr" target="_blank">linux.rouen@free.fr</a>>
wrote:<br>
>> > >>><br>
>> > >>> Hello Albert,<br>
>> > >>><br>
>> > >>> I have just updated
Purr Data 2.15.0 towards 2.15.1 with success
(OBS branch). :-)<br>
>> > >>><br>
>> > >>> In my projects the
console now prints out for example:<br>
>> > >>> error: couldn't
create "zexy/date -----------"<br>
>> > >>> ... click the link
above to track it down, or click the 'Find
Last Error' item in the Edit menu.<br>
>> > >>> error: couldn't
create "zexy/makesymbol %s-%s-%s"<br>
>> > >>> error: couldn't
create "zexy/makesymbol %s"<br>
>> > >>> error: couldn't
create "zexy/makesymbol 0%s"<br>
>> > >>> error: couldn't
create "zexy/makesymbol %s"<br>
>> > >>> error: couldn't
create "zexy/makesymbol 0%s"<br>
>> > >>> error: couldn't
create "zexy/time -----------"<br>
>> > >>> error: couldn't
create "zexy/makesymbol %s:%s:%s"<br>
>> > >>><br>
>> > >>> So now the new Zexy
library 2.3.0 as of 2020/02/20 is not totally
functional:
/opt/purr-data/lib/pd-l2ork/extra/zexy with
only 145 elements!<br>
>> > >>> In Purr Data
2.15.0, the Zexy library was v.2.2.6 as of
2016/01/22 with 241 elements.<br>
>> > >>><br>
>> > >>> After checking the
content of this folder (which is not empty),
it seems to be missing at least:<br>
>> > >>> - "date.pd_linux"
[ISOdata] when "date-help.pd" is present,<br>
>> > >>> - "time.pd_linux"
[ISOtime] when "time-help.pd" is present, and<br>
>> > >>> -
"makesymbol.pd_linux" when
"makesymbol-help.pd" is present.<br>
>> > >>><br>
>> > >>><br>
>> > >>><br>
>> > >>> * Any idea if this
is due to this new Zexy library 2.3.0 and/or
something else ?<br>
>> > >>><br>
>> > >>> Thanks.<br>
>> > >>> Best, Joseph<br>
>> > >>>
_______________________________________________<br>
>> > >>> L2Ork-dev mailing
list<br>
>> > >>> <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
>> > >>> <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
>> > >><br>
>> > >><br>
>> > >><br>
>> > >> --<br>
>> > >> Dr. Albert Gr"af<br>
>> > >> Computer Music Research
Group, JGU Mainz, Germany<br>
>> > >> Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
web: <a href="https://agraef.github.io/" rel="noreferrer" target="_blank">https://agraef.github.io/</a><br>
>> > >>
_______________________________________________<br>
>> > >> L2Ork-dev mailing list<br>
>> > >> <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
>> > >> <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
>> > ><br>
>> > >
_______________________________________________<br>
>> > > L2Ork-dev mailing list<br>
>> > > <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
>> > > <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Dr. Albert Gr"af<br>
>> > Computer Music Research Group,
JGU Mainz, Germany<br>
>> > Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
web: <a href="https://agraef.github.io/" rel="noreferrer" target="_blank">https://agraef.github.io/</a><br>
>> >
_______________________________________________<br>
>> > L2Ork-dev mailing list<br>
>> > <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
>> > <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
>>
_______________________________________________<br>
>> L2Ork-dev mailing list<br>
>> <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
>> <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
><br>
><br>
><br>
> --<br>
> Dr. Albert Gr"af<br>
> Computer Music Research Group, JGU Mainz,
Germany<br>
> Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
web: <a href="https://agraef.github.io/" rel="noreferrer" target="_blank">https://agraef.github.io/</a><br>
>
_______________________________________________<br>
> L2Ork-dev mailing list<br>
> <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
> <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">Dr. Albert Gr"af<br>
Computer Music Research Group, JGU
Mainz, Germany<br>
Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">Dr. Albert Gr"af<br>
Computer Music Research Group, JGU Mainz,
Germany<br>
Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">Dr. Albert Gr"af<br>
Computer Music Research Group, JGU Mainz, Germany<br>
Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">Dr. Albert Gr"af<br>
Computer Music Research Group, JGU Mainz, Germany<br>
Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
L2Ork-dev mailing list
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Dr. Albert Gr"af<br>Computer Music Research Group, JGU Mainz, Germany<br>Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>, web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div></div></div></div></div></div></div>