ReactNative-application.cmake links autolinked libraries to common_flags with the plain target_link_libraries signature, so a library that uses PRIVATE fails the app's CMake configure
維護者通常 2 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 70/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- cmake, react-native
- 領域
- build-system
研究方向
開啟ReactAndroid/cmake-utils/ReactNative-application.cmake,找出第 97 行(0.88.1)/第 108 行(nightly)附近的foreach(autolinked_library ...)區塊,以及其正下方的${APP_CODEGEN_TARGET}連結;兩者都使用target_link_libraries的簡單形式,這會與透過PRIVATE/PUBLIC自行連結的程式庫衝突。閱讀重現儲存庫中的modules/keyword-linking/android/CMakeLists.txt,查看會失敗的組合,接著在重現儲存庫中執行./reproduce.sh,在編輯前確認設定錯誤。完成條件是迴圈一律使用帶關鍵字的簽章,且./gradlew :app:configureCMakeDebug[arm64-v8a]以結束碼 0 結束,同時不連結任何內容或使用簡單形式連結的程式庫仍能正常設定。
由索引模型根據 Issue 內容生成。
描述
Description
ReactNative-application.cmake links every autolinked library to common_flags with the plain signature:
foreach(autolinked_library ${AUTOLINKED_LIBRARIES})
target_link_libraries(${autolinked_library} common_flags)
endforeach()
CMake refuses to mix the plain and the keyword signatures on one target, so an autolinked library whose own CMakeLists.txt links its target with PRIVATE, PUBLIC or INTERFACE fails the configure of every app that installs it. The app-level codegen target is linked the same way (target_link_libraries(${APP_CODEGEN_TARGET} common_flags)).
Steps to reproduce
-
Clone the reproducer and run
./reproduce.sh(react-native 0.88.1) or./reproduce.sh nightly.ReproducerAppdepends on a local library,modules/keyword-linking, whosereact-native.config.jsgives AndroidlibraryName: 'keywordlinking'andcmakeListsPath: 'CMakeLists.txt', and whoseandroid/CMakeLists.txtis:add_library(react_codegen_keywordlinking SHARED keyword-linking.cpp) target_link_libraries(react_codegen_keywordlinking PRIVATE fbjni jsi reactnative) -
The script runs
npm install, then./gradlew :app:configureCMakeDebug[arm64-v8a] -PreactNativeArchitectures=arm64-v8ainReproducerApp/android.
Expected: the app's CMake build configures, as it does when the library drops PRIVATE.
Seen: the configure fails at ReactNative-application.cmake:97 on 0.88.1 and at :108 on 0.90.0-nightly-20261113-6d587e873. The script exits 1 while this shows and 0 once the configure passes.
React Native Version
0.88.1
Affected Platforms
Runtime - Android, Build - Windows
Output of npx @react-native-community/cli info
System:
OS: Windows 11 10.0.26300
CPU: "(32) x64 AMD Ryzen 9 9950X3D 16-Core Processor "
Binaries:
Node:
version: 26.12.1
npm:
version: 12.2.1
Languages:
Java:
version: 17.0.20.1
npmPackages:
"@react-native-community/cli":
installed: 20.2.0
wanted: 20.2.0
react:
installed: 19.3.0
wanted: 19.3.0
react-native:
installed: 0.88.1
wanted: 0.88.1
Android:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
react-native 0.90.0-nightly-20261113-6d587e873
$ ./gradlew :app:configureCMakeDebug[arm64-v8a] -PreactNativeArchitectures=arm64-v8a
gradle exit 1
C/C++: CMake Error at ReproducerApp/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:108 (target_link_libraries):
C/C++: The keyword signature for target_link_libraries has already been used with
C/C++: the target "react_codegen_keywordlinking". All uses of
C/C++: target_link_libraries with a target must be either all-keyword or
C/C++: all-plain.
C/C++: The uses of the keyword signature are here:
C/C++: * ReproducerApp/node_modules/keyword-linking/android/CMakeLists.txt:7 (target_link_libraries)
C/C++: Call Stack (most recent call first):
C/C++: CMakeLists.txt:31 (include)
SUMMARY: defect: the app's CMake configure fails, as ReactNative-application.cmake links react_codegen_keywordlinking with the plain signature and its own CMakeLists uses PRIVATE (react-native 0.90.0-nightly-20261113-6d587e873)
MANDATORY Reproducer
https://github.com/YevheniiKotyrlo/react-native-autolinked-keyword-link-signature
Screenshots and Videos
No response
- 主要語言
- C++
- 星號
- 127k
- 分支
- 25.5k
- 平均合併
- 4 天 47 分鐘
- 30 天內合併 PR
- 217
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
react/react-native 的其他 Issue
-
ConcreteShadowNode::getConcreteSharedProps() returns a reference to a temporary可能已有人在做 @lazerg 於 1 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 82/100
react/react-native#59944 · 1 則留言 ·
維護者通常 2 天內回覆
-
`yarn test-ios` exits before building RNTester: `objc-test.sh` launches the WebSocket server script #59433 deleted可能已有人在做 @lazerg 於 1 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 76/100
react/react-native#59939 ·
維護者通常 2 天內回覆
-
iOS Fabric pointer-handler reset leaves the next lone touch non-primary可能已有人在做 @alleneubank 於 3 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 68/100
react/react-native#59919 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 70/100
react/react-native#59722 ·
維護者通常 2 天內回覆
-
Android: new WebSocket() crashes the app for a URL that OkHttp or java.net.URI rejects可能已有人在做 @sorinc03 於 11 天前認領。 未關閉🌐Networking Needs: Author Feedback Needs: Repro Platform: Android
難度 2/5 1-3 小時 新手友好度 72/100
react/react-native#59704 · 1 則留言 ·
維護者通常 2 天內回覆
查看 react/react-native 的全部 Issue
相似的 Issue
-
enhancement frontend
難度 2/5 1-3 小時 新手友好度 66/100
-
Spot Capacity Round Trips tests accept the two largest rising runs可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
intel/torch-xpu-ops#6197 ·
維護者通常 1 天內回覆
-
project: hipblaslt
難度 2/5 1-3 小時 新手友好度 62/100
ROCm/rocm-libraries#15746 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆