On 12/13/21 10:53, Dan Wilcox wrote:
FYI IOhannes:
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.
hmm, which dmg?
my plan was:
- download the .tgz
- extract the .pkg from the .tgz
- run
installer -pkg ./*.pkg -target /
afaict, there's no way to tell installer to extract to a specific
directory (as opposed to (disk) volume).
but anyhow: for somewhat unrelated reasons i like this more that installing "jack" via homebrew (given that with homebrew you quickly end up rebuilding your entire system if you are not running the very latest macOS - something that is rather detrimental to the idea of a CI)
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. :)
but isn't this what i'm seeing (as described in my previous mail): JACK being "somehow" weekly linked.
i somehow have the feeling i'm looking at the wrong places for the issue you seem to be having.
how can i quickly test whether my builds work as expected?
gf,msdrt IOhannes