Closed edwardgeorge closed 13 years ago
I've also noticed - albeit a separate issue - that the jack formula doesn't build the JackRouter driver which is fairly important for usage of jack with standard OSX CoreAudio applications. - mxcl/homebrew#3119
The new jack formula still doesn't seem to be preferable over the JackOSX binaries (I seem to remember it originally being removed from Homebrew in favour of the JackOSX binary distribution) and I guess is only here for build dependencies of other formulas?
added to mxcl/homebrew#3119:
For reference, I've changed my local jack formula to install from the binary packages instead: https://gist.github.com/667674
This gives me the jackrouter device, as well as the plugins, and third-party apps such as Ardour work again.
$ brew uses jack
darkice
fluxus
I guess Jack is only here for these brews; what should we do here? The "easiest" for us would be to remove all 3 but I don't use any of them to know what the best course of action is.
Moreover, the latest jack version on brew (1.9.6) won’t build with the latest CELT version on brew (8.1) because of an API change. Updating to 1.9.7 does it and is awfully easy, but does not seem to solve the issues listed here. I would fill a pull request, but these issues seem to make it kind of pointless, especially as they prevent me to do any kind of easy testing.
Update log for jack 1.9.7: http://jackaudio.org/node/53 Which includes:
I'll let you Jack users have a discussion, possibly on the mailing list, and then reopen some pull requests with the decisions. Thanks.
Using the jack formula I end up with the following libraries - libjack.dylib.0, libjack.dylib.0.1.0, libjackserver.dylib.0, libjackserver.dylib.0.1.0 - instead of libjack.0.dylib, libjack.0.1.0.dylib etc.
This causes problems with app binaries such as Ardour which will not run as the expected library files are not found.
I'm not familiar with waf so not sure where in the install process the files are named at present.