Closed SpectralDragon closed 2 years ago
This is a Swift Package Manager issue. You should file a bug with https://github.com/apple/swift-package-manager. I assume you get the same results if you run swift build
on the command line?
I assume you get the same results if you run
swift build
on the command line?
I'll check it
Yeah, you was right, the problem is swift package running on xcode and on SPM will shipping two different products. In first scenario where swift package builds on Xcode the bundles contains typical macos/ios NSBundle with Contents
folders. In second scenario swift compiler builds a product with simple Bundle. And also, SPM wasn't process a metal libs =/
Thanks!
Describe the bug I working on project with few targets and each target contains specific resources. But when I compile SPM package from VS Code, then resources copied only from executable target. When I build it from Xcode, all resources copied correctly.
To Reproduce Steps to reproduce the behavior:
Bundle.current.url(forResource: descriptor.shaderName, withExtension: "metallib")!
Expected behavior All resources copied correctly.
Environment
swift-driver version: 1.45.2 Apple Swift version 5.6 (swiftlang-5.6.0.323.62 clang-1316.0.20.8) Target: x86_64-apple-macosx12.0
Additional context Readme file with instructions is not correct right now, Vulkan isn't needed.