Mislav Marohnić

Here is the Homebrew PR to bump the version: https://github.com/Homebrew/homebrew-core/pull/201851 It installs the "main" example as the `whisper-cpp` binary. This is the full directory tree of the resulting install: ```...

> Btw, I only now realize that the `libggml` binaries from the `llama.cpp` package are symlinked into `/opt/homebrew/lib`. I wonder if this is a good idea due to the explanation...

> * If there is a single executable, which I believe is the case for the whisper.cpp brew package, then a static build should also work. This can be done...

Update: Homebrew v1.7.3 formula has been merged and the original issue in this thread fixed, so as far as I'm concerned, this can be closed and followup work tracked in...

Okay, I am preparing the change to the Homebrew formula to adjust it to the latest build system in this repo. I've reenabled BUILD_SHARED_LIBS and this is what I got...

@slaren To enable dylibs but to place them in a different location than "lib", I've tried this: 1. `-DCMAKE_INSTALL_LIBDIR=libinternal` 2. `-DCMAKE_INSTALL_RPATH=@loader_path/../libinternal` - this syntax is apparently macOS-specific but I'll figure...

Thanks; the Homebrew PR is up: https://github.com/Homebrew/homebrew-core/pull/202270

@AnyCPU Not sure exactly what you are asking, but the Homebrew formula for whisper-cpp does not include header files because they would conflict with same-named header files from llama.cpp (another...

@AnyCPU I'm not sure if the developers of these projects have plans for publishing header files together with their Homebrew formulae, but I'm guessing that's all dependent on https://github.com/ggml-org/ggml/issues/1333 shipping...

Hi, the backtick in that script is escaped and therefore harmless. How exactly are you running the installer script and what is your version of bash?