status-im
/
react-native
mirror of https://github.com/status-im/react-native.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
react-native/third-party-podspecs/Folly.podspec

36 lines
1.6 KiB
Plaintext
Raw Normal View History

BREAKING - Update podspecs to support and default to the C++ bridge Summary: This will require people who use CocoaPods to update their Podfiles. You can see an example of a Podfile set up to use the Cxx bridge here: https://github.com/mhorowitz/native-navigation-boilerplate/blob/master/ios/Podfile If this doesn't work, you can continue to use the old bridge by adding a dependency of 'BatchedBridge' to the React subspecs in your Podfile, but this will stop working once the old bridge is removed. Reviewed By: javache Differential Revision: D4981920 fbshipit-source-id: 7c4f3bf1c3f9af3f934f03ec003a05d0cd3cb259
2017-05-03 21:31:35 +00:00
Pod::Spec.new do |spec|
spec.name = 'Folly'
spec.version = '2016.09.26.00'
spec.license = { :type => 'Apache License, Version 2.0' }
spec.homepage = 'https://github.com/facebook/folly'
spec.summary = 'An open-source C++ library developed and used at Facebook.'
spec.authors = 'Facebook'
spec.source = { :git => 'https://github.com/facebook/folly.git',
:tag => "v#{spec.version}" }
spec.module_name = 'folly'
spec.dependency 'boost'
spec.dependency 'DoubleConversion'
spec.dependency 'GLog'
spec.compiler_flags = '-DFOLLY_NO_CONFIG -DFOLLY_MOBILE=1 -DFOLLY_USE_LIBCPP=1'
Work around the broken way CocoaPods/Xcode deals with header maps Summary: See https://github.com/facebook/react-native/issues/14326 for the bug this fixes. This is a pretty ugly hack to work around what I think is a CP bug. Since the C++ dependencies are only needed to build RN itself, and not applications, don't the conflicting headers as source files. Instead, use preserve_paths to get them unpacked into the source tree under Pods/<Pod>, and arrange for them to get used with HEADER_SEARCH_PATHS. This keeps them out of the project, so they don't get included in the header map, and other (badly structured) projects don't get confused. Reviewed By: javache Differential Revision: D5254716 fbshipit-source-id: cf33dcbcc71b5247843650c33ccf4fb08378e584
2017-06-15 19:47:42 +00:00
spec.source_files = 'folly/Bits.cpp',
BREAKING - Update podspecs to support and default to the C++ bridge Summary: This will require people who use CocoaPods to update their Podfiles. You can see an example of a Podfile set up to use the Cxx bridge here: https://github.com/mhorowitz/native-navigation-boilerplate/blob/master/ios/Podfile If this doesn't work, you can continue to use the old bridge by adding a dependency of 'BatchedBridge' to the React subspecs in your Podfile, but this will stop working once the old bridge is removed. Reviewed By: javache Differential Revision: D4981920 fbshipit-source-id: 7c4f3bf1c3f9af3f934f03ec003a05d0cd3cb259
2017-05-03 21:31:35 +00:00
'folly/Conv.cpp',
'folly/Demangle.cpp',
'folly/StringBase.cpp',
'folly/Unicode.cpp',
'folly/dynamic.cpp',
Make OSS CocoaPods build work with or without use_frameworks! Reviewed By: javache Differential Revision: D5361624 fbshipit-source-id: c2e5e8985827208a43e06932f746c6b9ccb146ad
2017-07-07 00:33:30 +00:00
'folly/json.cpp',
'folly/portability/BitsFunctexcept.cpp',
'folly/detail/MallocImpl.cpp'
Work around the broken way CocoaPods/Xcode deals with header maps Summary: See https://github.com/facebook/react-native/issues/14326 for the bug this fixes. This is a pretty ugly hack to work around what I think is a CP bug. Since the C++ dependencies are only needed to build RN itself, and not applications, don't the conflicting headers as source files. Instead, use preserve_paths to get them unpacked into the source tree under Pods/<Pod>, and arrange for them to get used with HEADER_SEARCH_PATHS. This keeps them out of the project, so they don't get included in the header map, and other (badly structured) projects don't get confused. Reviewed By: javache Differential Revision: D5254716 fbshipit-source-id: cf33dcbcc71b5247843650c33ccf4fb08378e584
2017-06-15 19:47:42 +00:00
# workaround for https://github.com/facebook/react-native/issues/14326
Make OSS CocoaPods build work with or without use_frameworks! Reviewed By: javache Differential Revision: D5361624 fbshipit-source-id: c2e5e8985827208a43e06932f746c6b9ccb146ad
2017-07-07 00:33:30 +00:00
spec.preserve_paths = 'folly/*.h',
'folly/detail/*.h',
'folly/portability/*.h'
Fix some issues with the React podspec for the Cxx bridge Summary: Trying to fix the RN Travis CI tests Splitting off from https://github.com/facebook/react-native/pull/14100 Closes https://github.com/facebook/react-native/pull/14132 Reviewed By: ericvicenti Differential Revision: D5112077 Pulled By: javache fbshipit-source-id: cf030b927b0f28f2b494471498f1ddb2c0a5c1df
2017-05-30 18:10:20 +00:00
spec.libraries = "stdc++"
BREAKING - Update podspecs to support and default to the C++ bridge Summary: This will require people who use CocoaPods to update their Podfiles. You can see an example of a Podfile set up to use the Cxx bridge here: https://github.com/mhorowitz/native-navigation-boilerplate/blob/master/ios/Podfile If this doesn't work, you can continue to use the old bridge by adding a dependency of 'BatchedBridge' to the React subspecs in your Podfile, but this will stop working once the old bridge is removed. Reviewed By: javache Differential Revision: D4981920 fbshipit-source-id: 7c4f3bf1c3f9af3f934f03ec003a05d0cd3cb259
2017-05-03 21:31:35 +00:00
spec.pod_target_xcconfig = { "USE_HEADERMAP" => "NO",
Fix some issues with the React podspec for the Cxx bridge Summary: Trying to fix the RN Travis CI tests Splitting off from https://github.com/facebook/react-native/pull/14100 Closes https://github.com/facebook/react-native/pull/14132 Reviewed By: ericvicenti Differential Revision: D5112077 Pulled By: javache fbshipit-source-id: cf030b927b0f28f2b494471498f1ddb2c0a5c1df
2017-05-30 18:10:20 +00:00
"CLANG_CXX_LANGUAGE_STANDARD" => "c++14",
BREAKING - Update podspecs to support and default to the C++ bridge Summary: This will require people who use CocoaPods to update their Podfiles. You can see an example of a Podfile set up to use the Cxx bridge here: https://github.com/mhorowitz/native-navigation-boilerplate/blob/master/ios/Podfile If this doesn't work, you can continue to use the old bridge by adding a dependency of 'BatchedBridge' to the React subspecs in your Podfile, but this will stop working once the old bridge is removed. Reviewed By: javache Differential Revision: D4981920 fbshipit-source-id: 7c4f3bf1c3f9af3f934f03ec003a05d0cd3cb259
2017-05-03 21:31:35 +00:00
"HEADER_SEARCH_PATHS" => "\"$(PODS_TARGET_SRCROOT)\" \"$(PODS_ROOT)/boost\" \"$(PODS_ROOT)/DoubleConversion\"" }
# Pinning to the same version as React.podspec.
Apple TV Cocoapods support Summary: **Motivation** Support Apple TV for people adding React Native to their projects using Cocoapods. **Test plan** Working test project at https://github.com/dlowder-salesforce/react-native-tvos-cocoapods-test Closes https://github.com/facebook/react-native/pull/15065 Differential Revision: D5443791 Pulled By: javache fbshipit-source-id: dc46a72df0d73a0049f1c3f9368658e5f3d1ecb8
2017-07-18 22:03:37 +00:00
spec.platforms = { :ios => "8.0", :tvos => "9.2" }
BREAKING - Update podspecs to support and default to the C++ bridge Summary: This will require people who use CocoaPods to update their Podfiles. You can see an example of a Podfile set up to use the Cxx bridge here: https://github.com/mhorowitz/native-navigation-boilerplate/blob/master/ios/Podfile If this doesn't work, you can continue to use the old bridge by adding a dependency of 'BatchedBridge' to the React subspecs in your Podfile, but this will stop working once the old bridge is removed. Reviewed By: javache Differential Revision: D4981920 fbshipit-source-id: 7c4f3bf1c3f9af3f934f03ec003a05d0cd3cb259
2017-05-03 21:31:35 +00:00
end