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
[SR-15935] Resource files created by build tool plugins aren't handled properly #4345
Comments
@swift-cicreate |
I have asked this question too on the forum Can the pluginWorkingDirectory contain an asset catalog - Development / Package Manager - Swift Forums Would love this to be solved! Any update? |
This should work as long as tools-version 5.7 or newer is used. Was fixed in #4306 |
Ok will try again and check the tools version. But xcode 14.3 gives me a warning now that it has no rule applied for the json files in my asset catalog. Maybe an Xcode thing then. |
Right, I believe that's the tools-version < 5.7 behavior. If this isn't the issue, please report back, this should be working in both SwiftPM CLI and Xcode at this point. |
Ok so I have tested it and it works with version 5.7! Thanks a lot for your detailed help @neonichu ! This will help me a lot thank you. |
@neonichu I did discover via #4306 that you need to use a |
Additional Detail from JIRA
md5: ff3606a8574b3b65ab897c084d6bb004
Issue Description:
In SwiftPM 5.6 and later, package plugin build tools can generate source files by defining build commands that have `.swift` source files as outputs. It is supposed to be possible to generate any of the kinds of output files that SwiftPM can handle, such as resources.
But specifying .strings files or .lproj directories as outputs does not seem to work in SwiftPM 5.6 — `swift` `build` emits a warning that it doesn't know what to do about that kind of file.
This bug report tracks making this work so that for example .strings files can be generated by built too plugins.
The text was updated successfully, but these errors were encountered: