Without using Dependencies.swift
once cannot control and embed Swift Packages into targets (mainly apps/tests which might require a certain library to be embedded)
Tuist won't embed SPM packages on its own (which makes sense, it doesn't know if they're dynamic or not) but the problem is we need them embedded. What's the best path forward there short of using Dependencies.swift to define things? Do we have to manually modify the project after generation? Write a custom plugin? Is there a setting I simply can't find in the docs to tell it to embed SPM packages in the app target?
It seems like the these test cases are not covered
Following up on a similar manner. I'm looking into the tests of how Tuist decides to embedded framework - here frameworks and targets, files
I don't see any test cover for how to decide if to embed and sign package(product:...) - is this not supported? Is there a specific way to embed swift packages? Am I looking at the wrong place?
Here is a small project showing what we are facing.
*Note - This issue was opened before - link
'/private/preboot/Cryptexes/OS/Users/danielbac/Library/Developer/Xcode/DerivedData/TuistEmbedTest-ascpuqhqphpbdwezasdvqybunzqv/Build/Products/Debug-iphoneos/PackageFrameworks/SomeSPM.framework/SomeSPM' (no such file), '/System/Library/Frameworks/SomeSPM.framework/SomeSPM' (no such file, not in dyld cache)
Ventura 13.4 (22F66)
3.18.0
14.3 (14E222b)
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too