[L2Ork-dev] L2Ork-dev Digest, Vol 84, Issue 19

Jonathan Wilkes jon.w.wilkes at gmail.com
Sun Oct 11 12:16:04 EDT 2020 

Hi Zack,

I've successfully made it through the emscripten build on Ubuntu 20.04.

I'll be dogfooding the web UI over the next few weeks and trying to
nail down the various UI bugs to get things in a more usable state.

As far as the build system, I have one question-- is there a way to
decouple the build step from the step to run the webapp from a local
web server? I.e., `make emscripten` would build the webapp and some
other recipe like `make emscripten_foo` would be used to run the local
webserver in order for the user to test out what just got built.

Albert-- is there a canonical name for this? `make test` is already
taken for running the regression tests.

-Jonathan

On Fri, Oct 9, 2020 at 5:32 PM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
>
> Just to clarify-- should steps 21 - 27 be completely removed?
>
> Seems like at least step #27 is important to keep.
>
> -Jonathan
>
> On Fri, Oct 9, 2020 at 10:36 AM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> >
> > Thanks, Zack. I'll make those changes today.
> >
> > -Jonathan
> >
> > On Fri, Oct 9, 2020 at 4:49 AM Zack Lee <cuinjune at gmail.com> wrote:
> > >
> > > Hi Jonathan,
> > >
> > > The Ubuntu 20.04 LTS (Emscripten) build guide which you have merged (https://git.purrdata.net/jwilkes/ci-runner-setup/-/merge_requests/1) is outdated and should be updated after step 7.
> > >
> > > It should be like the following:
> > >
> > > 7. git clone https://github.com/emscripten-core/emsdk.git
> > > 8. cd emsdk
> > > 9. git pull
> > > 10. ./emsdk install latest
> > > 11. ./emsdk activate latest
> > > 12. source ./emsdk_env.sh
> > > 13. ./emsdk update-tags
> > > 14. ./emsdk install tot
> > > 15. ./emsdk activate tot
> > > 16. cd ..
> > > 17. git clone https://git.purrdata.net/jwilkes/purr-data.git
> > > 18. cd purr-data
> > > 19. git checkout emscripten
> > > 20. make emscripten
> > >
> > > Best,
> > > Zack
> > >
> > >
> > > 2020년 10월 8일 (목) 오후 10:51, <l2ork-dev-request at disis.music.vt.edu>님이 작성:
> > >>
> > >> Send L2Ork-dev mailing list submissions to
> > >>         l2ork-dev at disis.music.vt.edu
> > >>
> > >> To subscribe or unsubscribe via the World Wide Web, visit
> > >>         https://disis.music.vt.edu/listinfo/l2ork-dev
> > >> or, via email, send a message with subject or body 'help' to
> > >>         l2ork-dev-request at disis.music.vt.edu
> > >>
> > >> You can reach the person managing the list at
> > >>         l2ork-dev-owner at disis.music.vt.edu
> > >>
> > >> When replying, please edit your Subject line so it is more specific
> > >> than "Re: Contents of L2Ork-dev digest..."
> > >>
> > >>
> > >> Today's Topics:
> > >>
> > >>    1. Linux dependencies in README.md build guide (Jonathan Wilkes)
> > >>    2. Re: Linux dependencies in README.md build guide (Albert Graef)
> > >>    3. Re: Linux dependencies in README.md build guide (Jonathan Wilkes)
> > >>    4. Re: Linux dependencies in README.md build guide (Jonathan Wilkes)
> > >>    5. Re: Linux dependencies in README.md build guide (Ivica Bukvic)
> > >>
> > >>
> > >> ----------------------------------------------------------------------
> > >>
> > >> Message: 1
> > >> Date: Thu, 8 Oct 2020 17:12:14 -0400
> > >> From: Jonathan Wilkes <jon.w.wilkes at gmail.com>
> > >> To: l2ork-dev <l2ork-dev at disis.music.vt.edu>
> > >> Subject: [L2Ork-dev] Linux dependencies in README.md build guide
> > >> Message-ID:
> > >>         <CAOA7yC7gprMaDeyi4Sxg5=SWxf4aJ0+tQUsnjirj76r4kUF6Uw at mail.gmail.com>
> > >> Content-Type: text/plain; charset="UTF-8"
> > >>
> > >> Hi list,
> > >>
> > >> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?
> > >> What does LV2 support in Jack have to do with Purr Data?
> > >>
> > >> 2. What is python-dev doing in there? If it is actually needed, is the
> > >> dependency on Python 2 or Python 3?
> > >>
> > >> -Jonathan
> > >>
> > >>
> > >> ------------------------------
> > >>
> > >> Message: 2
> > >> Date: Thu, 8 Oct 2020 23:54:39 +0200
> > >> From: Albert Graef <aggraef at gmail.com>
> > >> To: "An open mailing list for a world-wide network of aspiring
> > >>         L2Orkists, L2Ork developers contributors, and supporters."
> > >>         <l2ork-dev at disis.music.vt.edu>
> > >> Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide
> > >> Message-ID:
> > >>         <CA+rUic0-ONc-x3MnsisrYywU9-hN3yMzNa=MrKZh_7jqwASkrQ at mail.gmail.com>
> > >> Content-Type: text/plain; charset="utf-8"
> > >>
> > >> On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <jon.w.wilkes at gmail.com>
> > >> wrote:
> > >>
> > >> > 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?
> > >> > What does LV2 support in Jack have to do with Purr Data?
> > >> >
> > >>
> > >> 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.
> > >>
> > >> 2. What is python-dev doing in there? If it is actually needed, is the
> > >> > dependency on Python 2 or Python 3?
> > >> >
> > >>
> > >> 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.
> > >>
> > >> Albert
> > >>
> > >>
> > >> > -Jonathan
> > >> > _______________________________________________
> > >> > L2Ork-dev mailing list
> > >> > L2Ork-dev at disis.music.vt.edu
> > >> > https://disis.music.vt.edu/listinfo/l2ork-dev
> > >>
> > >>
> > >>
> > >> --
> > >> Dr. Albert Gr"af
> > >> Computer Music Research Group, JGU Mainz, Germany
> > >> Email: aggraef at gmail.com, web: https://agraef.github.io/
> > >> -------------- next part --------------
> > >> An HTML attachment was scrubbed...
> > >> URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20201008/fe83c96e/attachment-0001.html>
> > >>
> > >> ------------------------------
> > >>
> > >> Message: 3
> > >> Date: Thu, 8 Oct 2020 18:16:37 -0400
> > >> From: Jonathan Wilkes <jon.w.wilkes at gmail.com>
> > >> To: l2ork-dev <l2ork-dev at disis.music.vt.edu>
> > >> Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide
> > >> Message-ID:
> > >>         <CAOA7yC6x_8kTrxBEC66Sb2p0Yo-3BHLYh-HBWkfePeof568muw at mail.gmail.com>
> > >> Content-Type: text/plain; charset="UTF-8"
> > >>
> > >> On Thu, Oct 8, 2020 at 5:55 PM Albert Graef <aggraef at gmail.com> wrote:
> > >> >
> > >> > On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> > >> >>
> > >> >> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?
> > >> >> What does LV2 support in Jack have to do with Purr Data?
> > >> >
> > >> >
> > >> > 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.
> > >>
> > >> Ah, I see. Hm, rather than the old hard-coded deps I should just put a
> > >> line to fetch those deps from that file.
> > >>
> > >> >
> > >> >> 2. What is python-dev doing in there? If it is actually needed, is the
> > >> >> dependency on Python 2 or Python 3?
> > >> >
> > >> >
> > >> > 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.
> > >>
> > >> Ok, my list vs. your "Build-Depends":
> > >>
> > >> 1. I've got libjack-jackd2-dev while you have libjack-dev. Any benefit
> > >> to one or the other?
> > >>
> > >> 2. I've got libglu1-mesa-dev while you do not. Any reason I still need that one?
> > >>
> > >> 3. I have libgmerlin-avdec-dev while you do not. But we both have
> > >> libgmerlin-avdec-dev.
> > >>
> > >> 4. I have dssi-dev while you do not. But you have dssi-utils under "Depends"
> > >>
> > >> 5. As mentioned I have slv2-jack and libslv2-dev, you don't.
> > >>
> > >> 6. I have libgsl0-dev, you have libgsl-dev
> > >>
> > >> 7. I have portaudio19-dev, you don't.
> > >>
> > >> 8. I have libsmpeg0, you don't.
> > >>
> > >> 9. I have libjpeg62-turbo, you have libjpeg-dev.
> > >>
> > >> 10. I have git, you don't
> > >>
> > >> 11. I have byacc, you don't.
> > >>
> > >> Hm... wonder why we have libgtk2.0-dev-- was that added for nw.js?
> > >>
> > >> -Jonathan
> > >>
> > >>
> > >> >
> > >> > Albert
> > >> >
> > >> >>
> > >> >> -Jonathan
> > >> >> _______________________________________________
> > >> >> L2Ork-dev mailing list
> > >> >> L2Ork-dev at disis.music.vt.edu
> > >> >> https://disis.music.vt.edu/listinfo/l2ork-dev
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Dr. Albert Gr"af
> > >> > Computer Music Research Group, JGU Mainz, Germany
> > >> > Email: aggraef at gmail.com, web: https://agraef.github.io/
> > >> > _______________________________________________
> > >> > L2Ork-dev mailing list
> > >> > L2Ork-dev at disis.music.vt.edu
> > >> > https://disis.music.vt.edu/listinfo/l2ork-dev
> > >>
> > >>
> > >> ------------------------------
> > >>
> > >> Message: 4
> > >> Date: Thu, 8 Oct 2020 18:25:59 -0400
> > >> From: Jonathan Wilkes <jon.w.wilkes at gmail.com>
> > >> To: l2ork-dev <l2ork-dev at disis.music.vt.edu>
> > >> Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide
> > >> Message-ID:
> > >>         <CAOA7yC6zOBqEodnM-hdyRcJzyrowA9_6E2LbRxjQzABknR66_A at mail.gmail.com>
> > >> Content-Type: text/plain; charset="UTF-8"
> > >>
> > >> Also-- bullseye (testing) no longer has a "python" package, just
> > >> python2 and python3.
> > >>
> > >> So if we can just get rid of the python dependency altogether that
> > >> would be ideal. (Unless this is some kind of pdpython external...)
> > >>
> > >> -Jonathan
> > >>
> > >> On Thu, Oct 8, 2020 at 6:16 PM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> > >> >
> > >> > On Thu, Oct 8, 2020 at 5:55 PM Albert Graef <aggraef at gmail.com> wrote:
> > >> > >
> > >> > > On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> > >> > >>
> > >> > >> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?
> > >> > >> What does LV2 support in Jack have to do with Purr Data?
> > >> > >
> > >> > >
> > >> > > 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.
> > >> >
> > >> > Ah, I see. Hm, rather than the old hard-coded deps I should just put a
> > >> > line to fetch those deps from that file.
> > >> >
> > >> > >
> > >> > >> 2. What is python-dev doing in there? If it is actually needed, is the
> > >> > >> dependency on Python 2 or Python 3?
> > >> > >
> > >> > >
> > >> > > 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.
> > >> >
> > >> > Ok, my list vs. your "Build-Depends":
> > >> >
> > >> > 1. I've got libjack-jackd2-dev while you have libjack-dev. Any benefit
> > >> > to one or the other?
> > >> >
> > >> > 2. I've got libglu1-mesa-dev while you do not. Any reason I still need that one?
> > >> >
> > >> > 3. I have libgmerlin-avdec-dev while you do not. But we both have
> > >> > libgmerlin-avdec-dev.
> > >> >
> > >> > 4. I have dssi-dev while you do not. But you have dssi-utils under "Depends"
> > >> >
> > >> > 5. As mentioned I have slv2-jack and libslv2-dev, you don't.
> > >> >
> > >> > 6. I have libgsl0-dev, you have libgsl-dev
> > >> >
> > >> > 7. I have portaudio19-dev, you don't.
> > >> >
> > >> > 8. I have libsmpeg0, you don't.
> > >> >
> > >> > 9. I have libjpeg62-turbo, you have libjpeg-dev.
> > >> >
> > >> > 10. I have git, you don't
> > >> >
> > >> > 11. I have byacc, you don't.
> > >> >
> > >> > Hm... wonder why we have libgtk2.0-dev-- was that added for nw.js?
> > >> >
> > >> > -Jonathan
> > >> >
> > >> >
> > >> > >
> > >> > > Albert
> > >> > >
> > >> > >>
> > >> > >> -Jonathan
> > >> > >> _______________________________________________
> > >> > >> L2Ork-dev mailing list
> > >> > >> L2Ork-dev at disis.music.vt.edu
> > >> > >> https://disis.music.vt.edu/listinfo/l2ork-dev
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Dr. Albert Gr"af
> > >> > > Computer Music Research Group, JGU Mainz, Germany
> > >> > > Email: aggraef at gmail.com, web: https://agraef.github.io/
> > >> > > _______________________________________________
> > >> > > L2Ork-dev mailing list
> > >> > > L2Ork-dev at disis.music.vt.edu
> > >> > > https://disis.music.vt.edu/listinfo/l2ork-dev
> > >>
> > >>
> > >> ------------------------------
> > >>
> > >> Message: 5
> > >> Date: Thu, 8 Oct 2020 22:51:29 -0400
> > >> From: Ivica Bukvic <ico at vt.edu>
> > >> To: "An open mailing list for a world-wide network of aspiring
> > >>         L2Orkists, L2Ork developers contributors, and supporters."
> > >>         <l2ork-dev at disis.music.vt.edu>
> > >> Subject: Re: [L2Ork-dev] Linux dependencies in README.md build guide
> > >> Message-ID:
> > >>         <CAJrgGbY9tqFWePbc9ZwTvo_fxqvr5s0uON9feYhD8PHOi81XnQ at mail.gmail.com>
> > >> Content-Type: text/plain; charset="utf-8"
> > >>
> > >> I believe that is/was for pyext which requires flext. I thought we were not
> > >> building flext externals anymore? There may be also a requirement for
> > >> building the libcwiid since it has some gtk and/or python demo apps that
> > >> get built with it and which we do not need.
> > >>
> > >> Best,
> > >>
> > >> Ico
> > >>
> > >> --
> > >> Ivica Ico Bukvic, D.M.A.
> > >> Director, Creativity + Innovation
> > >> Institute for Creativity, Arts, and Technology
> > >>
> > >> Virginia Tech
> > >> Creative Technologies in Music
> > >> School of Performing Arts – 0141
> > >> Blacksburg, VA 24061
> > >> (540) 231-6139
> > >> ico at vt.edu
> > >>
> > >> www.icat.vt.edu
> > >> www.performingarts.vt.edu
> > >> l2ork.icat.vt.edu
> > >> ico.bukvic.net
> > >>
> > >> On Thu, Oct 8, 2020, 18:26 Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> > >>
> > >> > Also-- bullseye (testing) no longer has a "python" package, just
> > >> > python2 and python3.
> > >> >
> > >> > So if we can just get rid of the python dependency altogether that
> > >> > would be ideal. (Unless this is some kind of pdpython external...)
> > >> >
> > >> > -Jonathan
> > >> >
> > >> > On Thu, Oct 8, 2020 at 6:16 PM Jonathan Wilkes <jon.w.wilkes at gmail.com>
> > >> > wrote:
> > >> > >
> > >> > > On Thu, Oct 8, 2020 at 5:55 PM Albert Graef <aggraef at gmail.com> wrote:
> > >> > > >
> > >> > > > On Thu, Oct 8, 2020 at 11:12 PM Jonathan Wilkes <
> > >> > jon.w.wilkes at gmail.com> wrote:
> > >> > > >>
> > >> > > >> 1. Why are slv2-jack and libslv2-dev build dependencies of Purr Data?
> > >> > > >> What does LV2 support in Jack have to do with Purr Data?
> > >> > > >
> > >> > > >
> > >> > > > 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.
> > >> > >
> > >> > > Ah, I see. Hm, rather than the old hard-coded deps I should just put a
> > >> > > line to fetch those deps from that file.
> > >> > >
> > >> > > >
> > >> > > >> 2. What is python-dev doing in there? If it is actually needed, is the
> > >> > > >> dependency on Python 2 or Python 3?
> > >> > > >
> > >> > > >
> > >> > > > 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.
> > >> > >
> > >> > > Ok, my list vs. your "Build-Depends":
> > >> > >
> > >> > > 1. I've got libjack-jackd2-dev while you have libjack-dev. Any benefit
> > >> > > to one or the other?
> > >> > >
> > >> > > 2. I've got libglu1-mesa-dev while you do not. Any reason I still need
> > >> > that one?
> > >> > >
> > >> > > 3. I have libgmerlin-avdec-dev while you do not. But we both have
> > >> > > libgmerlin-avdec-dev.
> > >> > >
> > >> > > 4. I have dssi-dev while you do not. But you have dssi-utils under
> > >> > "Depends"
> > >> > >
> > >> > > 5. As mentioned I have slv2-jack and libslv2-dev, you don't.
> > >> > >
> > >> > > 6. I have libgsl0-dev, you have libgsl-dev
> > >> > >
> > >> > > 7. I have portaudio19-dev, you don't.
> > >> > >
> > >> > > 8. I have libsmpeg0, you don't.
> > >> > >
> > >> > > 9. I have libjpeg62-turbo, you have libjpeg-dev.
> > >> > >
> > >> > > 10. I have git, you don't
> > >> > >
> > >> > > 11. I have byacc, you don't.
> > >> > >
> > >> > > Hm... wonder why we have libgtk2.0-dev-- was that added for nw.js?
> > >> > >
> > >> > > -Jonathan
> > >> > >
> > >> > >
> > >> > > >
> > >> > > > Albert
> > >> > > >
> > >> > > >>
> > >> > > >> -Jonathan
> > >> > > >> _______________________________________________
> > >> > > >> L2Ork-dev mailing list
> > >> > > >> L2Ork-dev at disis.music.vt.edu
> > >> > > >> https://disis.music.vt.edu/listinfo/l2ork-dev
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Dr. Albert Gr"af
> > >> > > > Computer Music Research Group, JGU Mainz, Germany
> > >> > > > Email: aggraef at gmail.com, web: https://agraef.github.io/
> > >> > > > _______________________________________________
> > >> > > > L2Ork-dev mailing list
> > >> > > > L2Ork-dev at disis.music.vt.edu
> > >> > > > https://disis.music.vt.edu/listinfo/l2ork-dev
> > >> > _______________________________________________
> > >> > L2Ork-dev mailing list
> > >> > L2Ork-dev at disis.music.vt.edu
> > >> > https://disis.music.vt.edu/listinfo/l2ork-dev
> > >> -------------- next part --------------
> > >> An HTML attachment was scrubbed...
> > >> URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20201008/6d37fe89/attachment.html>
> > >>
> > >> ------------------------------
> > >>
> > >> Subject: Digest Footer
> > >>
> > >> _______________________________________________
> > >> L2Ork-dev mailing list
> > >> L2Ork-dev at disis.music.vt.edu
> > >> https://disis.music.vt.edu/listinfo/l2ork-dev
> > >>
> > >> ------------------------------
> > >>
> > >> End of L2Ork-dev Digest, Vol 84, Issue 19
> > >> *****************************************
> > >
> > > _______________________________________________
> > > L2Ork-dev mailing list
> > > L2Ork-dev at disis.music.vt.edu
> > > https://disis.music.vt.edu/listinfo/l2ork-dev

More information about the L2Ork-dev mailing list