-
-
Notifications
You must be signed in to change notification settings - Fork 235
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 'direct field offset' #108
Comments
Hi Chris, Would you be able to upload a demo project which reproduces the linker error? Just tried setting up a new project integrated with Carthage and didn't get any linker errors (Xcode 8.3.3). Looking back a similar issue was raised in May - #67. If this is a recurring thing on the latest versions of Xcode I'll take steps to remove the lazy properties. 👍 |
Hello Thank you for the quick response. I checked the other link and saw that you asked whether the other user was using a version of Xcode lower than 8.3. I'm using 8.2.1. Could that be the issue? |
@cloudface from what I remember it didn't seem to happen in Xcode 8.3.X. Maybe could be worth a shot? If that doesn't work / you're stuck on 8.2.X or lower for whatever reason, I'll propose a change the library to not use |
Ok thank you :). For now I just manually integrated the library and it works. |
I've now removed all the lazy variables from Tabman, so this should be resolved as of 0.7.3. 🎉 |
Hello
After fetching the Tabman dependency with Carthage and trying to add the framework to my project, i get the following linker error when trying to run my app on a device:
Undefined symbols for architecture arm64: "direct field offset for Tabman.TabmanViewController.(bar.storage in _57F68DA9D23EDB616EF841D0392909A0) : Tabman.TabmanBar.Config?", referenced from: Tabman.TabmanViewController.bar.setter : Tabman.TabmanBar.Config
I read about this error in other frameworks. Apparently it has something to do with lazy variables. Could it be fixed by following the suggestions outlined here: Yalantis/Koloda#229 ?
Thanks for any feedback.
Kind regards
Chris
The text was updated successfully, but these errors were encountered: