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

dyld: Library not loaded: @rpath/libswiftSwiftOnoneSupport.dylib #175

Open
toshi0383 opened this issue Apr 9, 2017 · 5 comments
Open

dyld: Library not loaded: @rpath/libswiftSwiftOnoneSupport.dylib #175

toshi0383 opened this issue Apr 9, 2017 · 5 comments
Labels

Comments

@toshi0383
Copy link

Maybe this is a rare case, but building inside xcworkspace ends-up with runtime crash.
See: toshi0383/TVMLKitchen#142
I confirmed this happens with Himotoki, too.

I wonder if anybody have alternative work-around for this? Rather than adding ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES on library side?

@ikesyo
Copy link
Owner

ikesyo commented May 27, 2017

I'm not sure about this without an example project. Would you mind providing one?

@toshi0383
Copy link
Author

Here you go! Just Cmd+R on a Simulator to reproduce.
HimotokiCarthageSample.zip

@ikesyo
Copy link
Owner

ikesyo commented May 29, 2017

TL;DR: This should be your project setting issue.

There are two things I'd like to note:

  • Even if you are referencing / linking to and embedding Carthage/Build/iOS/Himotoki.framework, why do you add Himotoki.xcodeproj to HimotokiCarthageSample? Since the framework is supplied as a prebuilt binary, you don't need to add the framework project reference to your project.

  • Due to the fact above and the Find Implicit Dependences Build Options of HimotokiCarthageSample scheme, another Himotoki.framework is built and placed into HimotokiCarthageSample-.../Build/Products/Debug-iphonesimulator. Then the another framework file is somehow loaded from the app and that can't find @rpath/libswiftSwiftOnoneSupport.dylib.

    If Himotoki.framework which is in HimotokiCarthageSample.app/Frameworks are correctly loaded from the app, the framework should successfully find HimotokiCarthageSample.app/Frameworks/libswiftSwiftOnoneSupport.dylib.

@toshi0383
Copy link
Author

Thanks for clarification!

why do you add Himotoki.xcodeproj to HimotokiCarthageSample?

Because I need to sometimes build from source to attach debugger to Himotoki source code.
Do you think of any workaround in this case?

@toshi0383
Copy link
Author

I wrote an article about this use-case in Japanese, FYI.
There are some other libraries which I don't have this issue. (e.g. I tried Ekhoo/Device and it worked fine)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants