Skip to content
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

[iOS, CocoaPods(1.5.3) Installation] Typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs 'enum clockid_t') #82

Closed
dannliu opened this issue Jun 18, 2018 · 5 comments
Labels

Comments

@dannliu
Copy link

dannliu commented Jun 18, 2018

The compiler error is from Folly.
My system is macos 10.13.5 (17F77), Xcode version: 9.4.1 (9F2000). I also installed Xcode 10 beta (10L176w). But I have already use the xcode-select to set the dev path for the Xcode 9.4.1.

@passy
Copy link
Member

passy commented Jun 18, 2018

Folly is a separate project: https://github.com/facebook/folly

@dannliu dannliu changed the title Typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs 'enum clockid_t') [iOS, CocoaPods Installation] Typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs 'enum clockid_t') Jun 19, 2018
@dannliu
Copy link
Author

dannliu commented Jun 19, 2018

@passy Yes, I understood. I updated the issue title. I tried to use CocoaPods to install the Sonar. Is there a way to change Podfile configuration to bypass this compiler error? Do I need to give a specific version of the Folly? The CocoaPods version I used is '1.5.3'

@dannliu dannliu changed the title [iOS, CocoaPods Installation] Typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs 'enum clockid_t') [iOS, CocoaPods(1.5.3) Installation] Typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs 'enum clockid_t') Jun 19, 2018
@passy
Copy link
Member

passy commented Jun 19, 2018

@x4snowman Sorry, what I meant to say was that if this is an error that is within folly, then it should probably be reported and fixed on their GitHub repo.

@dannliu
Copy link
Author

dannliu commented Jun 19, 2018

@passy Yes, it's an issue from Folly. However as you provide a guide on the official sitehttps://fbsonar.com/docs/getting-started.html, I think it's appropriate to make it works. I will report an issue for folly project. I don't have clue that how teams works with each other in Facebook. Maybe you can communicate with each other to make the issue been fixed ASAP. I have spend half my day to setup the Sonar ( By installing all the dependencies manually), but not yet work. By the way, The SonarKit podspec path have updated with iOS prefix #81 , it should be https://raw.githubusercontent.com/facebook/Sonar/master/iOS/SonarKit.podspec?token=ADr9NBuYoodM_NeysQg899hkxXw0WZ7Xks5bJ5OVwA%3D%3D

@dannliu
Copy link
Author

dannliu commented Jun 22, 2018

This is fixed on the master branch.

@dannliu dannliu closed this as completed Jun 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants