I noticed that when linking with llvm's libc++, the system's libc++ was still included, probably linked to other libraries that we depend on?
It caused crashes, so I rolled back to using the system's libc++, and "upped" the github action image to macos-13.
We still have to compile using llvm from homebrew, bacause the clang from macos chokes on std::format and the "automatic constructor" stuff (not sure what it's called).
However, compiling using homebrew llvm, and linking to macos's libc++ (libSystem?) works, but only on macos 13 and up.
I noticed that when linking with llvm's libc++, the system's libc++ was still included, probably linked to other libraries that we depend on?
It caused crashes, so I rolled back to using the system's libc++, and "upped" the github action image to macos-13.
We still have to compile using llvm from homebrew, bacause the clang from macos chokes on
std::format
and the "automatic constructor" stuff (not sure what it's called).However, compiling using homebrew llvm, and linking to macos's libc++ (libSystem?) works, but only on macos 13 and up.
I guess this is the best solution for now.