<div dir="ltr"><div>Hi Jonathan,</div><div><br></div>The Ubuntu 20.04 LTS (Emscripten) build guide which you have merged (<a href="https://git.purrdata.net/jwilkes/ci-runner-setup/-/merge_requests/1">https://git.purrdata.net/jwilkes/ci-runner-setup/-/merge_requests/1</a>) is outdated and should be updated after step 7.<div><br><div>It should be like the following:</div><div><br></div><div>7. git clone <a href="https://github.com/emscripten-core/emsdk.git">https://github.com/emscripten-core/emsdk.git</a><br>8. cd emsdk<br>9. git pull<br>10. ./emsdk install latest<br>11. ./emsdk activate latest<br>12. source ./emsdk_env.sh<br>13. ./emsdk update-tags<br>14. ./emsdk install tot<br>15. ./emsdk activate tot<br>16. cd ..<br></div><div>17. git clone <a href="https://git.purrdata.net/jwilkes/purr-data.git">https://git.purrdata.net/jwilkes/purr-data.git</a></div><div>18. cd purr-data<br>19. git checkout emscripten<br>20. make emscripten</div><div><br></div><div>Best,</div><div>Zack</div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2020년 10월 8일 (목) 오후 10:51, <<a href="mailto:l2ork-dev-request@disis.music.vt.edu">l2ork-dev-request@disis.music.vt.edu</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send L2Ork-dev mailing list submissions to<br>
<a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank">l2ork-dev@disis.music.vt.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<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>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:l2ork-dev-request@disis.music.vt.edu" target="_blank">l2ork-dev-request@disis.music.vt.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:l2ork-dev-owner@disis.music.vt.edu" target="_blank">l2ork-dev-owner@disis.music.vt.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of L2Ork-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Linux dependencies in README.md build guide (Jonathan Wilkes)<br>
2. Re: Linux dependencies in README.md build guide (Albert Graef)<br>
3. Re: Linux dependencies in README.md build guide (Jonathan Wilkes)<br>
4. Re: Linux dependencies in README.md build guide (Jonathan Wilkes)<br>
5. Re: Linux dependencies in README.md build guide (Ivica Bukvic)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 8 Oct 2020 17:12:14 -0400<br>
From: Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>><br>
To: l2ork-dev <<a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank">l2ork-dev@disis.music.vt.edu</a>><br>
Subject: [L2Ork-dev] Linux dependencies in README.md build guide<br>
Message-ID:<br>
<CAOA7yC7gprMaDeyi4Sxg5=<a href="mailto:SWxf4aJ0%2BtQUsnjirj76r4kUF6Uw@mail.gmail.com" target="_blank">SWxf4aJ0+tQUsnjirj76r4kUF6Uw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Hi list,<br>
<br>
1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?<br>
What does LV2 support in Jack have to do with Purr Data?<br>
<br>
2. What is python-dev doing in there? If it is actually needed, is the<br>
dependency on Python 2 or Python 3?<br>
<br>
-Jonathan<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 8 Oct 2020 23:54:39 +0200<br>
From: Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>><br>
To: "An open mailing list for a world-wide network of aspiring<br>
L2Orkists, L2Ork developers contributors, and supporters."<br>
<<a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank">l2ork-dev@disis.music.vt.edu</a>><br>
Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide<br>
Message-ID:<br>
<CA+rUic0-ONc-x3MnsisrYywU9-hN3yMzNa=<a href="mailto:MrKZh_7jqwASkrQ@mail.gmail.com" target="_blank">MrKZh_7jqwASkrQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>><br>
wrote:<br>
<br>
> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?<br>
> What does LV2 support in Jack have to do with Purr Data?<br>
><br>
<br>
I assume that you're talking about the Debian packaging stuff in<br>
purr-data/packages/linux_make/debian, which is probably severely outdated<br>
(those slv2 deps certainly are). Maybe you want to have a look at my<br>
debuild control file (purr-data/debuild/debian/control) and update the<br>
control file in linux_make/debian accordingly. The debuild stuff is always<br>
up-to-date and known to work with every Debian/Ubuntu version younger than<br>
Stretch and Xenial, because I'm using it to build packages on the OBS.<br>
<br>
2. What is python-dev doing in there? If it is actually needed, is the<br>
> dependency on Python 2 or Python 3?<br>
><br>
<br>
That's needed to build one of the DISIS externals, I forgot which one it<br>
was, but Ico should know. And yes, that's really the Python2 version that<br>
it needs, which causes quite some headaches if you want to build Purr on<br>
both old and new Debian/Ubuntu versions. But you can have a look at<br>
purr-data/debuild/debian/control to see how I solved this in the OBS<br>
builds. It would be good if we could just get rid of that Python2<br>
dependency, since Python2 is pretty much on its way out.<br>
<br>
Albert<br>
<br>
<br>
> -Jonathan<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20201008/fe83c96e/attachment-0001.html" rel="noreferrer" target="_blank">http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20201008/fe83c96e/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 8 Oct 2020 18:16:37 -0400<br>
From: Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>><br>
To: l2ork-dev <<a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank">l2ork-dev@disis.music.vt.edu</a>><br>
Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide<br>
Message-ID:<br>
<<a href="mailto:CAOA7yC6x_8kTrxBEC66Sb2p0Yo-3BHLYh-HBWkfePeof568muw@mail.gmail.com" target="_blank">CAOA7yC6x_8kTrxBEC66Sb2p0Yo-3BHLYh-HBWkfePeof568muw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Thu, Oct 8, 2020 at 5:55 PM Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>> wrote:<br>
><br>
> On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>> wrote:<br>
>><br>
>> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?<br>
>> What does LV2 support in Jack have to do with Purr Data?<br>
><br>
><br>
> I assume that you're talking about the Debian packaging stuff in purr-data/packages/linux_make/debian, which is probably severely outdated (those slv2 deps certainly are). Maybe you want to have a look at my debuild control file (purr-data/debuild/debian/control) and update the control file in linux_make/debian accordingly. The debuild stuff is always up-to-date and known to work with every Debian/Ubuntu version younger than Stretch and Xenial, because I'm using it to build packages on the OBS.<br>
<br>
Ah, I see. Hm, rather than the old hard-coded deps I should just put a<br>
line to fetch those deps from that file.<br>
<br>
><br>
>> 2. What is python-dev doing in there? If it is actually needed, is the<br>
>> dependency on Python 2 or Python 3?<br>
><br>
><br>
> That's needed to build one of the DISIS externals, I forgot which one it was, but Ico should know. And yes, that's really the Python2 version that it needs, which causes quite some headaches if you want to build Purr on both old and new Debian/Ubuntu versions. But you can have a look at purr-data/debuild/debian/control to see how I solved this in the OBS builds. It would be good if we could just get rid of that Python2 dependency, since Python2 is pretty much on its way out.<br>
<br>
Ok, my list vs. your "Build-Depends":<br>
<br>
1. I've got libjack-jackd2-dev while you have libjack-dev. Any benefit<br>
to one or the other?<br>
<br>
2. I've got libglu1-mesa-dev while you do not. Any reason I still need that one?<br>
<br>
3. I have libgmerlin-avdec-dev while you do not. But we both have<br>
libgmerlin-avdec-dev.<br>
<br>
4. I have dssi-dev while you do not. But you have dssi-utils under "Depends"<br>
<br>
5. As mentioned I have slv2-jack and libslv2-dev, you don't.<br>
<br>
6. I have libgsl0-dev, you have libgsl-dev<br>
<br>
7. I have portaudio19-dev, you don't.<br>
<br>
8. I have libsmpeg0, you don't.<br>
<br>
9. I have libjpeg62-turbo, you have libjpeg-dev.<br>
<br>
10. I have git, you don't<br>
<br>
11. I have byacc, you don't.<br>
<br>
Hm... wonder why we have libgtk2.0-dev-- was that added for nw.js?<br>
<br>
-Jonathan<br>
<br>
<br>
><br>
> Albert<br>
><br>
>><br>
>> -Jonathan<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>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 8 Oct 2020 18:25:59 -0400<br>
From: Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>><br>
To: l2ork-dev <<a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank">l2ork-dev@disis.music.vt.edu</a>><br>
Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide<br>
Message-ID:<br>
<<a href="mailto:CAOA7yC6zOBqEodnM-hdyRcJzyrowA9_6E2LbRxjQzABknR66_A@mail.gmail.com" target="_blank">CAOA7yC6zOBqEodnM-hdyRcJzyrowA9_6E2LbRxjQzABknR66_A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Also-- bullseye (testing) no longer has a "python" package, just<br>
python2 and python3.<br>
<br>
So if we can just get rid of the python dependency altogether that<br>
would be ideal. (Unless this is some kind of pdpython external...)<br>
<br>
-Jonathan<br>
<br>
On Thu, Oct 8, 2020 at 6:16 PM Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>> wrote:<br>
><br>
> On Thu, Oct 8, 2020 at 5:55 PM Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>> wrote:<br>
> ><br>
> > On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>> wrote:<br>
> >><br>
> >> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?<br>
> >> What does LV2 support in Jack have to do with Purr Data?<br>
> ><br>
> ><br>
> > I assume that you're talking about the Debian packaging stuff in purr-data/packages/linux_make/debian, which is probably severely outdated (those slv2 deps certainly are). Maybe you want to have a look at my debuild control file (purr-data/debuild/debian/control) and update the control file in linux_make/debian accordingly. The debuild stuff is always up-to-date and known to work with every Debian/Ubuntu version younger than Stretch and Xenial, because I'm using it to build packages on the OBS.<br>
><br>
> Ah, I see. Hm, rather than the old hard-coded deps I should just put a<br>
> line to fetch those deps from that file.<br>
><br>
> ><br>
> >> 2. What is python-dev doing in there? If it is actually needed, is the<br>
> >> dependency on Python 2 or Python 3?<br>
> ><br>
> ><br>
> > That's needed to build one of the DISIS externals, I forgot which one it was, but Ico should know. And yes, that's really the Python2 version that it needs, which causes quite some headaches if you want to build Purr on both old and new Debian/Ubuntu versions. But you can have a look at purr-data/debuild/debian/control to see how I solved this in the OBS builds. It would be good if we could just get rid of that Python2 dependency, since Python2 is pretty much on its way out.<br>
><br>
> Ok, my list vs. your "Build-Depends":<br>
><br>
> 1. I've got libjack-jackd2-dev while you have libjack-dev. Any benefit<br>
> to one or the other?<br>
><br>
> 2. I've got libglu1-mesa-dev while you do not. Any reason I still need that one?<br>
><br>
> 3. I have libgmerlin-avdec-dev while you do not. But we both have<br>
> libgmerlin-avdec-dev.<br>
><br>
> 4. I have dssi-dev while you do not. But you have dssi-utils under "Depends"<br>
><br>
> 5. As mentioned I have slv2-jack and libslv2-dev, you don't.<br>
><br>
> 6. I have libgsl0-dev, you have libgsl-dev<br>
><br>
> 7. I have portaudio19-dev, you don't.<br>
><br>
> 8. I have libsmpeg0, you don't.<br>
><br>
> 9. I have libjpeg62-turbo, you have libjpeg-dev.<br>
><br>
> 10. I have git, you don't<br>
><br>
> 11. I have byacc, you don't.<br>
><br>
> Hm... wonder why we have libgtk2.0-dev-- was that added for nw.js?<br>
><br>
> -Jonathan<br>
><br>
><br>
> ><br>
> > Albert<br>
> ><br>
> >><br>
> >> -Jonathan<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>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 8 Oct 2020 22:51:29 -0400<br>
From: Ivica Bukvic <<a href="mailto:ico@vt.edu" target="_blank">ico@vt.edu</a>><br>
To: "An open mailing list for a world-wide network of aspiring<br>
L2Orkists, L2Ork developers contributors, and supporters."<br>
<<a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank">l2ork-dev@disis.music.vt.edu</a>><br>
Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide<br>
Message-ID:<br>
<<a href="mailto:CAJrgGbY9tqFWePbc9ZwTvo_fxqvr5s0uON9feYhD8PHOi81XnQ@mail.gmail.com" target="_blank">CAJrgGbY9tqFWePbc9ZwTvo_fxqvr5s0uON9feYhD8PHOi81XnQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I believe that is/was for pyext which requires flext. I thought we were not<br>
building flext externals anymore? There may be also a requirement for<br>
building the libcwiid since it has some gtk and/or python demo apps that<br>
get built with it and which we do not need.<br>
<br>
Best,<br>
<br>
Ico<br>
<br>
-- <br>
Ivica Ico Bukvic, D.M.A.<br>
Director, Creativity + Innovation<br>
Institute for Creativity, Arts, and Technology<br>
<br>
Virginia Tech<br>
Creative Technologies in Music<br>
School of Performing Arts – 0141<br>
Blacksburg, VA 24061<br>
(540) 231-6139<br>
<a href="mailto:ico@vt.edu" target="_blank">ico@vt.edu</a><br>
<br>
<a href="http://www.icat.vt.edu" rel="noreferrer" target="_blank">www.icat.vt.edu</a><br>
<a href="http://www.performingarts.vt.edu" rel="noreferrer" target="_blank">www.performingarts.vt.edu</a><br>
<a href="http://l2ork.icat.vt.edu" rel="noreferrer" target="_blank">l2ork.icat.vt.edu</a><br>
<a href="http://ico.bukvic.net" rel="noreferrer" target="_blank">ico.bukvic.net</a><br>
<br>
On Thu, Oct 8, 2020, 18:26 Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>> wrote:<br>
<br>
> Also-- bullseye (testing) no longer has a "python" package, just<br>
> python2 and python3.<br>
><br>
> So if we can just get rid of the python dependency altogether that<br>
> would be ideal. (Unless this is some kind of pdpython external...)<br>
><br>
> -Jonathan<br>
><br>
> On Thu, Oct 8, 2020 at 6:16 PM Jonathan Wilkes <<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>><br>
> wrote:<br>
> ><br>
> > On Thu, Oct 8, 2020 at 5:55 PM Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>> wrote:<br>
> > ><br>
> > > On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <<br>
> <a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>> wrote:<br>
> > >><br>
> > >> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?<br>
> > >> What does LV2 support in Jack have to do with Purr Data?<br>
> > ><br>
> > ><br>
> > > I assume that you're talking about the Debian packaging stuff in<br>
> purr-data/packages/linux_make/debian, which is probably severely outdated<br>
> (those slv2 deps certainly are). Maybe you want to have a look at my<br>
> debuild control file (purr-data/debuild/debian/control) and update the<br>
> control file in linux_make/debian accordingly. The debuild stuff is always<br>
> up-to-date and known to work with every Debian/Ubuntu version younger than<br>
> Stretch and Xenial, because I'm using it to build packages on the OBS.<br>
> ><br>
> > Ah, I see. Hm, rather than the old hard-coded deps I should just put a<br>
> > line to fetch those deps from that file.<br>
> ><br>
> > ><br>
> > >> 2. What is python-dev doing in there? If it is actually needed, is the<br>
> > >> dependency on Python 2 or Python 3?<br>
> > ><br>
> > ><br>
> > > That's needed to build one of the DISIS externals, I forgot which one<br>
> it was, but Ico should know. And yes, that's really the Python2 version<br>
> that it needs, which causes quite some headaches if you want to build Purr<br>
> on both old and new Debian/Ubuntu versions. But you can have a look at<br>
> purr-data/debuild/debian/control to see how I solved this in the OBS<br>
> builds. It would be good if we could just get rid of that Python2<br>
> dependency, since Python2 is pretty much on its way out.<br>
> ><br>
> > Ok, my list vs. your "Build-Depends":<br>
> ><br>
> > 1. I've got libjack-jackd2-dev while you have libjack-dev. Any benefit<br>
> > to one or the other?<br>
> ><br>
> > 2. I've got libglu1-mesa-dev while you do not. Any reason I still need<br>
> that one?<br>
> ><br>
> > 3. I have libgmerlin-avdec-dev while you do not. But we both have<br>
> > libgmerlin-avdec-dev.<br>
> ><br>
> > 4. I have dssi-dev while you do not. But you have dssi-utils under<br>
> "Depends"<br>
> ><br>
> > 5. As mentioned I have slv2-jack and libslv2-dev, you don't.<br>
> ><br>
> > 6. I have libgsl0-dev, you have libgsl-dev<br>
> ><br>
> > 7. I have portaudio19-dev, you don't.<br>
> ><br>
> > 8. I have libsmpeg0, you don't.<br>
> ><br>
> > 9. I have libjpeg62-turbo, you have libjpeg-dev.<br>
> ><br>
> > 10. I have git, you don't<br>
> ><br>
> > 11. I have byacc, you don't.<br>
> ><br>
> > Hm... wonder why we have libgtk2.0-dev-- was that added for nw.js?<br>
> ><br>
> > -Jonathan<br>
> ><br>
> ><br>
> > ><br>
> > > Albert<br>
> > ><br>
> > >><br>
> > >> -Jonathan<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20201008/6d37fe89/attachment.html" rel="noreferrer" target="_blank">http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20201008/6d37fe89/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<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>
End of L2Ork-dev Digest, Vol 84, Issue 19<br>
*****************************************<br>
</blockquote></div>