Mac package

[carlca]

I'm actually very interested in this app both from a musical point of view and also because I'm intrigued to know about the GUI front end. I have a Mac. Could I help in getting a Mac package together? Let me know!

[sqweek]

Hi Carl! If you just want to play around a bit check out the 0.9.5 release, which included an OSX package: https://github.com/sqweek/sqribe/releases/tag/sqribe-0.9.5

That's probably the best place to start for generating an up to date package too, since my template and packaging scripts are sitting on the hard drive of a VM which (a) no longer wants to boot and (b) lives on a laptop I have limited access to these days.

The only thing that has changed since is the executable (ie. the go code), so in theory you should be able to reuse the dylibs from 0.9.5 and issue a go build from master. cgo will need the header files though, so you'll need to download the dependencies at least (just shouldn't need to recompile them). The packages I had on osx for the 0.9.5 build were:

• ffmpeg (I've lost track of which version unfortunately; I suspect it was a git checkout)
  • yasm-1.3.0.tar.gz
• portaudio (pa_stable_v19_20140130.tgz)
• fluidsynth (fluidsynth-1.1.6.tar.bz2)
  • glib (glib-2.46.2.tar.xz + glib-2.47.4.tar.gz; not sure which I used :S)
    • libffi-3.2.1.tar.gz
    • gettext-0.19.6.tar.xz
• pkg-config-0.29.tar.gz

Ah, but it occurs to me the .pc pkgconfig files get installed when you build the libs. You can mock them up yourself if you're familiar with C compilation, but if you have xcode etc. setup already it might be simpler to build them. It's possible ports/homebrew can provide a shortcut but I'm not familiar with them.

That's a rough outline; I realise this is all very fiddly and so totally understand if you don't have that kind of time to throw at it. But if you do, let me know which approach you prefer and I can offer more guidance (plus I have a few scripts/build configurations which aren't yet in the repo).

[carlca]

Hello, That does sound quite involved and to honest, I’ve already got so many bits of Music software demanding my attention, that I think I will keep this email archived for the moment, and get back to it at a later date! Cheers, Carl

…

On 7 Dec 2017, 11:39 +0000, sqweek ***@***.***>, wrote: Hi Carl! If you just want to play around a bit check out the 0.9.5 release, which included an OSX package: https://github.com/sqweek/sqribe/releases/tag/sqribe-0.9.5 That's probably the best place to start for generating an up to date package too, since my template and packaging scripts are sitting on the hard drive of a VM which (a) no longer wants to boot and (b) lives on a laptop I have limited access to these days. The only thing that has changed since is the executable (ie. the go code), so in theory you should be able to reuse the dylibs from 0.9.5 and issue a go build from master. cgo will need the header files though, so you'll need to download the dependencies at least (just shouldn't need to recompile them). The packages I had on osx for the 0.9.5 build were: • ffmpeg (I've lost track of which version unfortunately; I suspect it was a git checkout) • yasm-1.3.0.tar.gz • portaudio (pa_stable_v19_20140130.tgz) • fluidsynth (fluidsynth-1.1.6.tar.bz2) • glib (glib-2.46.2.tar.xz + glib-2.47.4.tar.gz; not sure which I used :S) • libffi-3.2.1.tar.gz • gettext-0.19.6.tar.xz • pkg-config-0.29.tar.gz Ah, but it occurs to me the .pc pkgconfig files get installed when you build the libs. You can mock them up yourself if you're familiar with C compilation, but if you have xcode etc. setup already it might be simpler to build them. It's possible ports/homebrew can provide a shortcut but I'm not familiar with them. That's a rough outline; I realise this is all very fiddly and so totally understand if you don't have that kind of time to throw at it. But if you do, let me know which approach you prefer and I can offer more guidance (plus I have a few scripts/build configurations which aren't yet in the repo). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.