-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Switch from 14 to 17 for 0.69 RN #3326
Comments
Hey! 👋 It looks like you've omitted a few important sections from the issue template. Please complete Description, Snack or minimal code example, Package versions and Affected platforms sections. |
Hey, I have already merged a fix for it, it will be available in the next release. #3347 |
@piaskowyk I think this patch also makes sure to fix this warning when running pod install, besides the jest fix [!] Can't merge user_target_xcconfig for pod targets: ["RNReanimated", "hermes-engine"]. Singular build setting CLANG_CXX_LANGUAGE_STANDARD has different values. |
OK for
For latest React Native it requires that one. Not sure if we can make it dynamic based on version ? |
I got the following waring x4 when I set [!] Can't merge user_target_xcconfig for pod targets: ["RNReanimated", "hermes-engine"]. Singular build setting CLANG_CXX_LANGUAGE_STANDARD has different values.
[!] Can't merge user_target_xcconfig for pod targets: ["RNReanimated", "hermes-engine"]. Singular build setting CLANG_CXX_LANGUAGE_STANDARD has different values.
[!] Can't merge user_target_xcconfig for pod targets: ["RNReanimated", "hermes-engine"]. Singular build setting CLANG_CXX_LANGUAGE_STANDARD has different values.
[!] Can't merge user_target_xcconfig for pod targets: ["RNReanimated", "hermes-engine"]. Singular build setting CLANG_CXX_LANGUAGE_STANDARD has different values. I am sure I've set
|
I am getting same error when i installed the latest version of react-native-reanimated:
Is there any fix or work around for this yet? |
@codeOlam, you can use patch-package as described in the original post as a workaround, and hopefully a new version will be released soon and the patch-package file can be deleted after upgrading. |
Thank you JayFeldman12. I was able to get a fix yesterday. by following this solution: #3305 (comment). I also had to install |
i had the same problem, in npx patch-package react-native-reanimated to patch your new changes diff --git a/node_modules/react-native-reanimated/RNReanimated.podspec b/node_modules/react-native-reanimated/RNReanimated.podspec
index d53cb12..719f813 100644
--- a/node_modules/react-native-reanimated/RNReanimated.podspec
+++ b/node_modules/react-native-reanimated/RNReanimated.podspec
@@ -94,7 +94,7 @@ Pod::Spec.new do |s|
}
s.compiler_flags = folly_compiler_flags + ' ' + boost_compiler_flags
s.xcconfig = {
- "CLANG_CXX_LANGUAGE_STANDARD" => "c++14",
+ "CLANG_CXX_LANGUAGE_STANDARD" => "c++17",
"HEADER_SEARCH_PATHS" => "\"$(PODS_ROOT)/boost\" \"$(PODS_ROOT)/boost-for-react-native\" \"$(PODS_ROOT)/glog\" \"$(PODS_ROOT)/#{folly_prefix}Folly\" \"${PODS_ROOT}/Headers/Public/React-hermes\" \"${PODS_ROOT}/Headers/Public/hermes-engine\"",
"OTHER_CFLAGS" => "$(inherited)" + " " + folly_flags } You can see below my |
After the update to react-reanimated to the 2.10.0 version, I am still getting the warning when running |
please read this #3326 (comment) |
"react-native-reanimated": "^3.0.0-rc.3", just install this version of reac-native-reanimated package, your problem will be solved. |
installed 2.13.0 and problem was solved :) |
Weirdly I'm still getting this problem with version |
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
[email protected]
for the project I'm working on.Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: