Carlo Cabrera
Carlo Cabrera
Oh, I see. My mistake.
Alternatives to the above: 1. Is there a way to customise the value used by `ccls` for `clang -print-resource-directory` at build time? If so, we can set this to a...
> there's that pesky version number at the end to deal with, even if we use `opt_prefix` That's fine; `ccls` always needs to be rebuilt with major version bumps to...
@madscientist sure, that's why neither of my suggestions involved checking the resource directory at runtime.
> https://github.com/MaskRay/ccls/wiki/Build#macos should be up to update (I used Apple m1 few months ago). Yes, that looks right. I've made a small improvement, though.
FYI: we're bumping LLVM to 13.0.1 in Homebrew/homebrew-core#94339. CI caught the stale reference to the old `resource-dir`, which contained a reference to `13.0.0` when it should now point to `13.0.1`....
@rfay's original attempt looks promising. It might just be missing setting `PATH` and `HOME` from @NickHackman's version.
Ah, no, I think we need a way to specify `LaunchOnlyOnce` in the `service` block: ``` LaunchOnlyOnce This optional key specifies whether the job can only be run once and...
Not really, but my understanding is that this is why we want `LaunchOnlyOnce`: we don't really want `launchd` to manage the `colima` daemon (because it's complicated -- my impression is...
We're trying to update Homebrew's version of Boost at Homebrew/homebrew-core#91224, but we're currently blocked on a build failure for libtorrent-rasterbar. I'm looking into backporting patches to fix the build failure,...