xcode compile_commands generation improvements and issues

[diemoschwarz]

Hi, this project looks great! I'm trying it on a large 25y+ code base on Mac and of course there are some issues.

But first, I can suggest two improvements to this blog section (that's not on some git repo?):

1. "the compilation command is repeated twice for some reason": that's because of the intel/arm universal build. One can use these options for a fully specified repeatable generation:

   xcodebuild -arch arm64 -target "mytarget" -project myproject.xcodeproj clean build
   

2. the sed command to filter out -ivfsstatcache only works for compile_commands.json with one single entry. This is more robust:

   sed -E 's/\-ivfsstatcache [^ ]*\.sdkstatcache//g' 
   

Now I'm stuck at a clang-tidy error: LLVM ERROR: unknown module format
I don't know if this is referring to the compile_commands.json format or to the disabling of the C++ modules features that is mentioned (however I can only find C module options to disable in xcode), or something else. FWIW, here's the compile_commands.json.zip.

Thanks!

[bkryza]

@diemoschwarz Thanks for the improvements for the blog post - I'll try to update it...

As to the error you're getting - the issue is related to the fact that C++ modules are probably enabled somehow in XCode (even if your project doesn't use them), and you're running clang-tidy and clang-uml using LLVM from Homebrew/Macports, and the LLVM versions are likely different and have different module formats. Can you try runnig clang-uml with the following flags --add-compile-flag "-fno-implicit-modules" --add-compile-flag "-fno-modules"?

You could also try to disable modules in XCode (it's in the IDE somewhere) and rebuild the entire project...

Unless of course you can just build the project outside of XCode (e.g. using CMake and using the same LLVM that is linked to clang-uml), then that would definitely solve this issue.

[diemoschwarz]

Thanks for the valuable hints, adding -fno-implicit-modules and -fno-modules to the xcode compile flags did it (there is no build setting in the IDE for disabling C++ modules!).
Then, I managed to guess --query-driver clang (there is no hint as to what a "driver" is supposed to be) and needed a few --add-compile-flag -I$PWD/....
Now the fun starts...