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

Cocoapods compatibility #3

Closed
almostintuitive opened this issue Oct 15, 2017 · 16 comments
Closed

Cocoapods compatibility #3

almostintuitive opened this issue Oct 15, 2017 · 16 comments

Comments

@almostintuitive
Copy link

There's an issue on react-native I've opened: facebook/react-native#16381
I'm trying to use this version of boost instead of what's currently referred to as 'boost' in Folly.podspec, since the release version that can be downloaded from here is 4-5x smaller.

This is the podspec I've added
https://github.com/languagedrops/react-native/commit/1c3f1ab55aa8541bde2adbc4c4f25914a5731021

which should be the same as:
https://github.com/CocoaPods/Specs/blob/master/Specs/9/9/d/boost/1.59.0/boost.podspec.json

except the download URL.

But when I try to run the project with boost installed from this repo, I get the following error:
image

Are there any plans of making a pod out of this?

Thank you!

@bestander
Copy link
Collaborator

@itchingpixels, thanks for digging the details.
Are you up to send a PR to fix that?

@almostintuitive
Copy link
Author

I'd be happy to do that, but haven't got around making it work just yet - I don't know what the delta is between this and the 1.59.0 release that's on cocoapods, but it's really confusing!

@almostintuitive
Copy link
Author

it seems like there's some magic (at least to me) going on with preserve_paths that I don't understand (why is it needed at all?) in the original podspec. will try a few different things and report back.

@bestander
Copy link
Collaborator

@ide, do you have some context on this to help us out?

@ide
Copy link
Member

ide commented Oct 17, 2017

I don't have a lot of context around this and @mhorowitz set up the third-party pods. If we go in this direction I think we should just add a podspec to this repo to install direct from GitHub but not publish to CocoaPods since we're not going to remember to keep it updated.

@bestander
Copy link
Collaborator

Pinged @mhorowitz, thanks @ide

@mhorowitz
Copy link

When I set up CocoaPods for CxxBridge, boost worked out of the box for me. I never even looked at the original Podspec, so I don't know why it's set up the way it is.

My best guess why it isn't working now is that something in the maze of ifdefs changed, and now type_index.h is being included, but the type_index/ directory isn't included in any of the subspecs in the podspec you linked. Adding it to one of the existing subspecs, or making a new one, would be the next thing to try.

@fishmwei
Copy link

@mhorowitz
I add a subspec to boost.podspec , then pod install again , it works.

#added by hmw
spec.subspec 'type_index-includes' do |cs|
    cs.preserve_paths = 'boost/type_index/**/*.hpp'
 end

@almostintuitive
Copy link
Author

Great!!! Sorry guys that I backed out, had been super busy with a release...
@fishmwei : do you have a PR?

@fishmwei
Copy link

fishmwei commented Nov 8, 2017

@itchingpixels I have a PR in your branch PR

@bestander
Copy link
Collaborator

Anyone wants to send a PR for this repo?
I suppose other people will have a similar problem.

Thanks @fishmwei for finding the solution.

@almostintuitive
Copy link
Author

I've created a PR: facebook/react-native#16756
This is my first PR to react-native, I'm not sure what to do to get it merged in - if you can bump it, that may work?

@bestander
Copy link
Collaborator

Thanks, I'll ping iOS people internally

@almostintuitive
Copy link
Author

@bestander do you have any news regarding this? I'm not sure whom should I be in contact with.

@Pranit-Harekar
Copy link

+1 any update ?

@bestander
Copy link
Collaborator

Trunk is still broken, I'll merge it once it is green: https://circleci.com/gh/facebook/react-native/tree/master.
Someone from RN team is on it but a PR with a fix is welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants