-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors when building against iOS 15 #616
Comments
Update: tried to build oclint from source and still doesn't work. |
Another update: Created empty Xcode 13. Here is the result of
|
We usually have this type of error during Xcode major releases. To solve it, OCLint needs to be built with the same LLVM version as the Xcode. This year, Xcode 13 requires LLVM 13.0.0, which is not officially released to date. We'll have to wait until that happens first. |
When is it expected to be resolved? |
@Davidxiaoshuo I can't control when LLVM releases 13.0.0, their website https://llvm.org/ says two days ago, but I am not seeing it happening now. If you can't wait, please manually change the llvm path to their 13.0.0-rc3 version, and build it locally yourself. |
use something like this : xcodebuild -workspace "XXXX.xcworkspace" -scheme "YYYY-scheme" COMPILER_INDEX_STORE_ENABLE=NO |
Just an update: while LLVM 13.0.0 is tagged, I am not seeing the artifacts available for macOS and Linux just yet. Will pay attention to its updates. In the meanwhile, 1) please try the |
|
I believe the master branch should have this addressed. But you need to make sure 1) you have an Intel mac; 2) you are running macOS Monterey; and 3) you have Xcode 13.1. If you meet all requirements, download the latest release binary, clean your archived folder, delete and re-generate the If you don't meet the above requirement, you need to manually build oclint locally, so that it is correctly compiled using your arch/os/xcode. Once you have a local build, then clean your archived folder, re-generate the I am not sure the status of building oclint on an M1 based mac yet, my order of the new macbook pro is expected to ship in early December, so I can only verify it probably for the next release, not this one. |
i find this oclint source code in oclint-driver/lib/driver.cpp at line 156
which shows the reson is in my case |
the file "oclint-driver/lib/Driver.cpp" checkout commit to 2d1ee18 ""
"" |
@guzuqing could you please elaborate your use case a little more? The commit you found was a temporary workaround to support checking CUDA code for GPU offloading, where multiple architectures are supported. However, your initial compilation builds your target in both i386 and x86_64 architectures. Allowing multiple invocation would, from my understanding, just run the same static analysis twice, as they are all CPU targets. I have been thinking if it makes sense to introduce a flag that allows multiple jobs. But I seem not to find a good justification to allow this. |
Is this problem solved? I had the same problem |
Issue Summary
A lot of errors like 'could not build module 'UIKit' or 'could not build module 'Foundation' after updating to Xcode 15
Environment
Sample code
Command to run OCLint with the code above.
Expected Behavior
Generated report.
Actual Behavior
A lot of compiler errors and no analysis
I found one issue from 2015 and version 0.9, which is basically the same:
#240
Is this possible to be the case?
The text was updated successfully, but these errors were encountered: