Move resource generation below framework vfs #880
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This moves resource generation (and being added to
deps
) below theframework_vfs
creation which uses thedeps
With the change in #879 to add the vfs to the
swiftc_inputs
instead of thedeps
of theswift_library
theframework_vfs
was now also forwarding the resources (because it gets added todeps
after generation) to other rules (likerules_xcodeproj
) which collect extra files from this theswiftc_inputs
attr. This led to duplicated resources in the project as they're collected fromresources
and now the transitivedeps
of theframework_vfs
AFAIK resources aren't needed for the
framework_vfs
rules and so this change should resolve the newrules_xcodeproj
incompatibility while making thedeps
to theframework_vfs
more scoped.