-
Notifications
You must be signed in to change notification settings - Fork 395
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
build: Import CocoaAsyncSocket using Carthage #350
build: Import CocoaAsyncSocket using Carthage #350
Conversation
oops, I merged #349 |
@KazuCocoa no problems, simple create another PR to revert it |
🆗 |
fix build error
@KazuCocoa Thanks, I merged your PR. It still fails in CI, though
Are you using an older version of Xcode? |
mm, I used Xcode 11.3. Let me try an older one |
I think the error is specific to Xcode 11.4. See this link: https://developer.apple.com/documentation/xcode_release_notes/xcode_11_4_release_notes?language=objc |
quamotion#3 could be a workaround... |
Note: For Xcode 11.4+, we can specify For less than 11.3, we should not specify the flag since clang raises an error, invalid flag. If we found a way to handle the flag dynamically, this PR is ready, I believe. |
Like https://github.com/qmfrederik/WebDriverAgent/pull/3/files , when I added
|
Cannot we simply push a PR to https://github.com/robbiehanson/CocoaAsyncSocket ? I hope @robbiehanson would be happy to merge it ASAP |
I've created robbiehanson/CocoaAsyncSocket#723. Let's see how it goes. |
Updated with the CocoaAsyncSocket fix |
@@ -7,7 +7,11 @@ | |||
* of patent rights can be found in the PATENTS file in the same directory. | |||
*/ | |||
|
|||
#import "GCDAsyncSocket.h" | |||
#if __has_warning("-Watimport-in-framework-header") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say this is not necessary anymore after GCDAsyncSocket bump
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yey
This is an alternative to #349, but as I mentioned it gives a compile-time error and I'm not sure how it can be suppressed (other than fixing it upstream)