For a project at work which uses JACK, I set up the build system to download the prebuilt JACK dmg and extract it to a local build directory. This seems to work fine for both building *and* distribution as user systems which have (non-homebrew) JACK installed are able to run the program with JACK.
I have a feeling that, like JackOSX before it, the JACK distribution builds do some extra step which makes this "magic" work (weak linking?) while the Homebrew builds do not (linked applications expect same lib path). As to why exactly, I don't know, maybe changing the dylib path? In any case, I think it's easier for most people to run an installer rather than ask them to copy/paste and run command line incantations to use JACK via Homebrew. :)
Message: 3Date: Mon, 13 Dec 2021 10:29:55 +0100From: IOhannes m zm?lnig <zmoelnig@iem.at>To: pd-list@lists.iem.at, William Brent <william.brent@gmail.com>Subject: Re: [PD] [PD-announce] Pd version 0.52-0test3 releasedMessage-ID: <fff79b5d-c70a-27e7-2717-7ff6cefd1ca7@iem.at>Content-Type: text/plain; charset="utf-8"; Format="flowed"On 12/13/21 03:42, Miller Puckette via Pd-list wrote:
As explained in previous emails, I don't use jack from Homebrew for my builds. I use the distribution from jack.org <https://urldefense.proofpoint.com/v2/url?u=http-3A__jack.org_&d=DwIFAg&c=-35OiAkTchMrZOngvJPOeA&r=XprZV3Fxus2L1LCw80hE4Q&m=ycOjZIud6YrWOk_GwSKZQH8UkGH1TeCiVsjsMIlmE_FTvOHrDlkBofF6FsBNUyl-&s=xZhKQcor-5nubxwqw4EU2QFekoO3jau_fkGQI5knM1g&e= > which is equivalent to the old JackOSX distribution:
https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads_&d=DwIFAg&c=-35OiAkTchMrZOngvJPOeA&r=XprZV3Fxus2L1LCw80hE4Q&m=ycOjZIud6YrWOk_GwSKZQH8UkGH1TeCiVsjsMIlmE_FTvOHrDlkBofF6FsBNUyl-&s=bfa_OxtCOIyvpdlj2NL0nPmVqj505twR0xAxEXWncog&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__jackaudio.org_downloads_&d=DwIFAg&c=-35OiAkTchMrZOngvJPOeA&r=XprZV3Fxus2L1LCw80hE4Q&m=ycOjZIud6YrWOk_GwSKZQH8UkGH1TeCiVsjsMIlmE_FTvOHrDlkBofF6FsBNUyl-&s=bfa_OxtCOIyvpdlj2NL0nPmVqj505twR0xAxEXWncog&e= >
You just need to download and run the installer on the build machine, which could also be automated via a script. People needing to use jack installed via Homebrew should build Pd themselves as the those libs doesn't seem to enable weak linking like the ones in the installer AFAICT.
Dan Wilcox
Right ho - Iohannes - I'm hoping this is something you can fix in the CI
builds
yes of course.i'd still like to understand the problem first though.my setup is: macOS X Sierra (10.7) in a VMif i install the dmg file from my CI-scripts (now that they use a non-broken Tcl/Tk) Pd opens up just fine.going to the media menu, i see two options for the audio backend:- standard (portaudio)- jackselecting "jack" i get an error on the Pd-console, saying:Can't open Jack (it seems not to be installed)
this is expected, as i haven't installed jack.i then download JACK-1.9.19 from https://jackaudio.org/downloads/, extract it, and run the jack2.pkg found withing.this should install JACK.i *restart* Pd and select "jack" again, and now i get an errorJACK: couldn't connect to server, is JACK running?
again, tihs is expected, as i haven't started JACK.so i open up qJackCtl (also found in the download from jackaudio.org), and start the JACK server (i use the *dummy* audio backend, as the VM has no soundcard).back in Pd, i again select "jack" as the backend, and - tada - no more warnings *and* Pd shows up in the qjackctl graph.the binary i'm using is this one (Tcl/Tk is universal; but Pd itself is only amd64; this is built with JACK from homebrew):https://git.iem.at/pd/pure-data/-/jobs/33751/artifacts/downloadwilliam: could you tell me where our paths deviate?gfmdsaIOhannes