Closed mdaniel closed 2 years ago
I'm not really familiar with Homebrew (or any of the other package managers) on macOS, but I didn't want to depend on any particular one for setting it up, hence the script building everything from scratch (and not installing any of it system-wide).
I wouldn't be against including an alternate script for Homebrew users, but it might wind up outdated and non-working (like the MSVC stuff currently is).
That makes sense, thanks for your reply. I'm going to close this issue
Currently, the macos dependency script is a lot of shell but the dependencies it wants are currently in Homebrew, which could save potential contributors a lot of CPU time by not downloading and rebuilding them:
I can appreciate that some people have strong feelings about Homebrew, so I thought it best to ask if you were building those deps manually on purpose, or would entertain a patch for a Homebrew-based macOS build