You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On our project we have many test targets, and all of them depend on Carthage versions of Quick and Nimble. When we build this with parallel builds enabled a Carthage bug can be hit where two instances of copy-frameworks try to strip the same dSYM (Carthage/Carthage#2531). Since test targets don't really need to strip anything at all, it would be good to be able to specify on a target that we want to embed the Carthage frameworks instead of using copy-frameworks. It can default properly for test targets.
I will add a directlyEmbedCarthageDependencies to Target. Right now it would be true for .macOS platform, and I'll extend it to be true for test targets as well.
The text was updated successfully, but these errors were encountered:
They just said it's a bug on our side. They are correct. Only iOS apps need to use that script, since no other targets need to strip the simulator slice. I have a PR incoming.
On our project we have many test targets, and all of them depend on Carthage versions of Quick and Nimble. When we build this with parallel builds enabled a Carthage bug can be hit where two instances of
copy-frameworks
try to strip the same dSYM (Carthage/Carthage#2531). Since test targets don't really need to strip anything at all, it would be good to be able to specify on a target that we want to embed the Carthage frameworks instead of usingcopy-frameworks
. It can default properly for test targets.I will add a
directlyEmbedCarthageDependencies
toTarget
. Right now it would betrue
for.macOS
platform, and I'll extend it to betrue
for test targets as well.The text was updated successfully, but these errors were encountered: