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

iOS doesn't seem to copy over the dylib properly? #117

Open
davemackintosh opened this issue Jan 5, 2023 · 5 comments
Open

iOS doesn't seem to copy over the dylib properly? #117

davemackintosh opened this issue Jan 5, 2023 · 5 comments

Comments

@davemackintosh
Copy link

I've tried each example but I always seem to get the same error on running.

I get "Library not loaded .dylib`

I can see that the libname.a and libname.dyld are built and where they should be but when I cargo apple open the libname.a file is red in the file explorer and running errors about the library not being loaded.

I've manually added both to the project and tried to re-run and get the same no matter what I try.

On a side note, the template appears to be wrong as well. Defaulting to a deployment target of iOS 9 which also needs changing.

@Cmdv
Copy link

Cmdv commented Jan 18, 2023

@davemackintosh do you get an error in the lines of:

ld: library not found for -lnameofproj

If so I'm having the same issue 😞

@davemackintosh
Copy link
Author

davemackintosh commented Jan 18, 2023

The particular error I was getting escapes me but it was an error todo with the lib that cargo builds not being where the Xcode project expects it to be. Yours sounds like a linker error which is likely a missing package on your system?

@Cmdv
Copy link

Cmdv commented Jan 19, 2023

the package that's missing is the name of the project prefixed with -l 🤷 not a clue what that means tbh
I can see things named libXXX but nothing else

@davemackintosh
Copy link
Author

-l is a linker argument which combines symbols from multiple output files into one binary file. Sounds like your build is failing whereas my build appears to work but the actual library built isn’t where Xcode is told it is

@Cmdv
Copy link

Cmdv commented Jan 19, 2023

ah ok just that my libname.a file is also red in the file explorer in Xcode and I don't get any other build errors prior to this.
I've also opened an issue related to my scenario in a fork of this project that seems to be more active :)

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

2 participants