CxxBridge, when used with Cocoapods, depends on an older version of "boost" that is also 4x larger than the one downloaded by ios-install-third-party.sh

[almostintuitive]

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Scanning folders for symlinks in /Users/mark/Dev/drops-react-native/node_modules (9ms)

Environment:
OS: macOS High Sierra 10.13
Node: 8.6.0
Yarn: 1.1.0
npm: 5.3.0
Watchman: 4.9.0
Xcode: Xcode 9.0 Build version 9A235
Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
react: 16.0.0-beta.5 => 16.0.0-beta.5
react-native: 0.49.3 => 0.49.3

Steps to Reproduce

1. Install react-native via Cocoapods
2. Add CxxBridge instead of BatchedBridge to your Podfile
3. pod install

Expected Behavior

Download the same version & bundle of the boost library that is used by ios-install-third-party.sh.

Actual Behavior

The boost dependency defined in Folly.podspec points to:
https://github.com/CocoaPods/Specs/blob/master/Specs/9/9/d/boost/1.59.0/boost.podspec.json

Which is:

• Version 1.59.0 instead of boost
• A way larger bundle (83 Mb instead of 16 Mb)

File specified in the boost pod spec:
https://sourceforge.net/projects/boost/files/boost/1.59.0/boost_1_59_0.tar.gz/download

File that ios-install-third-party.sh downloads:
https://github.com/react-native-community/boost-for-react-native/releases/download/v1.63.0-0/boost_1_63_0.tar.gz

[karpov3]

Hi @itchingpixels! I have the same problem. My project now is too large cause of boost library. Did you already resolve your issue?

[almostintuitive]

@karpov3 : not just yet, but I think we're close:
#16381 (comment)
so you can download the podspec from our fork, fix the podspec file according to fishmwei 's instructions, and place it in a folder, where you can reference it I believe.

the relevant podspec file in our fork:
https://github.com/languagedrops/react-native/commit/1c3f1ab55aa8541bde2adbc4c4f25914a5731021

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

[CFKevinRef]

It looks like once this lands, you will be able to include third-party-podspecs/boost.podspec directly and get the appropriate boost-for-react-native build: #16756

[almostintuitive]

This has been resolved by d40db3a