Repository metrics
- Stars
- (3,621 個のスター)
- PR merge metrics
- (PR metrics pending)
説明
Opening an issue for this, as I'm not sure the best way to address it.
The current logic for building the include file search path on macOS results in Posix looking set of directories like /include:/usr/include:/usr/local/include.
On a typical macOS developer installation, the system headers will actually be installed to a path like /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/. If targeting iOS, the header would be in a directory like /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/include/. The same for watchOS or tvOS.
It is not enough to identify the current system; the call must also know the target system to evaluate this call correctly.