Closed ian-mcdowell closed 6 years ago
Yes, zapcc was last updated from LLVM trunk on 2017-07-03 before D39050. Patches are welcome for a newer merge... did you build a MacOS version of zapcc? you'd be the first.
Closing this as duplicate of #5.
I built it by disabling the memcpy wrapping. This issue occurs when building a project using Xcode using zapcc, which is a separate issue from zapcc not building on macOS.
Yes, threw the memcpy thing away in c74f82da81b310dace3e1b53046d7dac12d8d676. -index-store-path will be added if/when zapcc is re-merged with newer LLVM.
I'm attempting to use zapcc inside of Xcode 9.2 on Mac. Xcode 9 and above pass the "-index-store-path /some/path" argument to clang, which causes errors with zapcc, since the arguments are unrecognized.
It looks like this project forked clang before support for this argument was added.
What are your plans for keeping up to date with upstream clang?