SPM Resource Bundle Access

[Ernest0-Production]

SPM targets have a different way of searching for a bundle of resources, unlike regular xcode targets:
https://medium.com/clutter-engineering/supporting-both-swift-package-manager-and-cocoapods-in-your-library-861f00b6b0f9

Example:

class ImageHelper {
    static var resolvedBundle: Bundle {
#if SWIFT_PACKAGE
        return Bundle.module
#else
        return Bundle(for: self)
#endif
    }
    
    static func image(_ name: String) -> UIImage? {
        return UIImage(named: name,
                       in: resolvedBundle,
                       compatibleWith: nil)
    }
}

Given this fact, and the fact that Tuist converts the SPM target into a regular xcode target:
What method of searching for a bundle of resources should be in the sources of the SPM package so that this does not lead to errors during integration through Tuist?

[fortmarek]

We should support resources inside SPM and they should be accessed the same way as if they were in a package. If there's a dependency where we don't generate the resource accessor correctly, would you mind raising an issue with a repro?

[Ernest0-Production]

Note 1: My question is not about the generated bundle accessor for external access, but about the use in the library itself.

Note 2: My question does not about the usual (native) SPM packages, but about integration via Tuist/Package.swift manifest

---

At the moment, I haven't tried to produce such a scenario yet, but in the near future I'm going to wrap some 3rd party xcframework (that has resources) in Package.swift for integration into Tuist.

I know that it is possible to directly connect xcframework to my target as TargetDependency.xcframework(...), but I would like to keep all external features in one place - Tuist/Package.swift.

Since the vendor of the framework only supports Cocoapods, I wanted to see if I could wrap it in SPM myself, given that in the library itself (most likely) the search for a bundle of resources can be implemented in such a way that it will not work through SPM.

---

I would be interested to know how tuist manages to generate an xcode target from package manifest so that the search for the resource bundle, which is described in the source code of the SPM target, is correctly performed from the "xcode-target environment".
Is there some trick by which you managed to set it up?

[fortmarek]

The resources for SPM targets are mapped in this file. We try to copy more-or-less what Apple does during build time when using the vanilla integration.