This moves resource generation (and being added to deps) below the framework_vfs creation which uses the deps
With the change in #879 to add the vfs to the swiftc_inputs instead of the deps of the swift_library the framework_vfs was now also forwarding the resources (because it gets added to deps after generation) to other rules (like rules_xcodeproj) which collect extra files from this the swiftc_inputs attr. This led to duplicated resources in the project as they're collected from resources and now the transitive deps of the framework_vfs
AFAIK resources aren't needed for the framework_vfs rules and so this change should resolve the new rules_xcodeproj incompatibility while making the deps to the framework_vfs more scoped.
This moves resource generation (and being added to
deps) below theframework_vfscreation which uses thedepsWith the change in #879 to add the vfs to the
swiftc_inputsinstead of thedepsof theswift_librarytheframework_vfswas now also forwarding the resources (because it gets added todepsafter generation) to other rules (likerules_xcodeproj) which collect extra files from this theswiftc_inputsattr. This led to duplicated resources in the project as they're collected fromresourcesand now the transitivedepsof theframework_vfsAFAIK resources aren't needed for the
framework_vfsrules and so this change should resolve the newrules_xcodeprojincompatibility while making thedepsto theframework_vfsmore scoped.