-
Notifications
You must be signed in to change notification settings - Fork 38
fix: precompiled resource bundle warnings #1566
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
base: main
Are you sure you want to change the base?
fix: precompiled resource bundle warnings #1566
Conversation
Resolves #1010 as well |
Head branch was pushed to by a user without write access
193497d
to
4e01cab
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@sebastianv1 It looks like one of the examples is failing with this PR. The |
@cgrindel Hmm i ran And I ran |
Head branch was pushed to by a user without write access
4e01cab
to
9f94389
Compare
I am doing that in #1568. It should merge in a few minutes. |
@Mergifyio queue |
🟠 Waiting for conditions to match
|
@Mergifyio queue |
🟠 Waiting for conditions to match
|
For SPM modules that use precompiled resource bundles (i.e `.bundle` files), Bazel throws the warning ``` WARNING: input 'Sources/Down/Resources/DownView (macOS).bundle' is a directory; dependency checking of directories is unsound ``` Instead of just referencing the `.bundle` path directly we should wrap it in a `apple_bundle_import` for the prebuilt bundle and then add it into the `resources` attr.
62729d6
to
03b60e8
Compare
@Mergifyio queue |
🟠 Waiting for conditions to match
|
@Mergifyio queue |
🟠 Waiting for conditions to match
|
For SPM modules that use precompiled resource bundles (i.e
.bundle
files), Bazel throws the warningInstead of just referencing the
.bundle
path directly we should wrap it in aapple_bundle_import
for the prebuilt bundle and then add it into theresources
attr.