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

linker error when compiling to ios simulator target #5679

Open
ijsnow opened this issue Nov 18, 2024 · 0 comments
Open

linker error when compiling to ios simulator target #5679

ijsnow opened this issue Nov 18, 2024 · 0 comments

Comments

@ijsnow
Copy link

ijsnow commented Nov 18, 2024

Summary

I have a rust library successfully compiling to ios to use inside an expo/react native app, but when I add libp2p, I get a lot of warnings saying that some object files weren't built for the correct target. After the warnings I get two warnings that don't print any info or description after. I'm not sure how to pass in -v to get more info unfortunately because expo is running the commands to compile/link.

Expected behavior

The module is linked and compiled successfully.

Actual behavior

I get a lot of linker warnings, but more problematically, two linker errors without any info. It might be important to note that I don't get any linker warnings until I try to compile code that uses libp2p.

Relevant log output

⚠  ld: object file (/Users/user/.../myapp/ios/rust/libshared_mobile.a[490](a6a6146597915357-sha256-x86_64-macosx.o)) was built for newer 'iOS-simulator' version (17.2) than being linked (15.1)
... a lot of the same as the line above with different objects
⚠  ld: Could not find or use auto-linked framework 'CoreAudioTypes': framework 'CoreAudioTypes' not found

❌  ld: Undefined symbols:



❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)



› 2 error(s), and 52 warning(s)

CommandError: Failed to build iOS project. "xcodebuild" exited with error code 65.


### Possible Solution

_No response_

### Version

_No response_

### Would you like to work on fixing this bug ?

Maybe
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

1 participant