Christoffer Lerno
Christoffer Lerno
Sadly a known issue Homebrew producing non-standalone static libraries. One can really ask oneself what the point is of static libraries when the libraries retain dependencies on dynamic libraries.
For now, using Homebrew to get c3c, grab LLVM from homebrew just to get the dependencies or building it yourself are the available solutions. I am very sorry about this.
What we need is a CI similar to https://github.com/c3lang/win-llvm but for MacOS which creates builds for Aarch64 and x64. Then we could use those to build C3 instead.
This is what building a custom version of LLVM could do.
This is in progress but will probably not be fixed quite yet.
Maybe this isn't useful enough given that there are workarounds we discovered?
Copy paste from Discord: --- So compiling this in C: ```c bool call_with_seh(void* context, CallFn call_fn, ExceptFn except_fn) { try { call_fn(context); return true; } except(EXCEPTION_EXECUTE_HANDLER) { except_fn(context); return false;...
Yes, as I think of this, I could actually make a library (.c3l) and put it in vendor which you would include and then on Windows it compiles the C...
Would you be able to test that though? I can write it, but not test it.
The problem here is that whether or not a "break" (or "continue") exists is entirely opaque to the user of the function. At one point in time I was thinking...