-
Notifications
You must be signed in to change notification settings - Fork 137
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
Error adding "apple_core_data_model" dependency to "swift_library" #1160
Comments
You want to put |
Thank you Keith, that worked and the core data swift files are now part of the project.
However, it seems there were some compile problems for those generated core data swift classes, wonder if you've seen this issue before? Thanks for your help!
|
Interesting, I haven't seen this one, if you pass |
Unfortunately no :(. I'll dig into this a little further, thanks for helping
|
it seems like this must be a bug in the rules, if you provide a repro case someone might be able to debug further |
That would be awesome. Here's how to reproduce:
This should produce the error, thanks again! |
Thanks for the repro, that is very helpful! Turns out the problem is the same as this: #969 |
A quick hack workaround is to pass |
Yea I think you'd have to pipe those flags to rules_xcodeproj too, you probably should just add them to your |
Hi @keith , I am facing the same issue when I use the latest version of I forked @cs2be 's repo and created a new branch
|
The latest rule versions where it worked was: swift: 1.18.0 |
Do we have any plan to fix this issue on swift 2.x? |
@xuzhaocheng maybe you could create a new issue since this one is closed |
Hi, I'm trying to add core data build dependencies to my swift project, however I got an error when trying to run the build rule:
Running "bazel build //:lib", I get the following errors:
I suspect the build rule apple_core_data_model is missing SwiftInfo dictionary. The swift_library code that pulls SwiftInfo from deps is here.
I'm using these versions of rules_apple and rules_swift:
Thanks!
The text was updated successfully, but these errors were encountered: