Closed zoul closed 7 years ago
CwlSignal has never built properly using Carthage. It is something that I will address as part of the tidy up for CwlSignal 2.0 – some time this week, I hope.
Specifically, your problem occurs because the child CwlUtils project is pulled automatically by CwlSignal (which uses the Swift Package Manager internally as part of the "FetchDependencies" target) and the pulled project is built using xcodebuild (in the "CwlUtils" target). This child CwlUtils project is not using the same parameters that the parent CwlSignal uses and this is causing a conflict.
There are two issues here:
I will address during the version 2 beta phase and make testing with Carthage a standard part of my build testing.
Great explanation, thank you! If someone stumbles into this issue in the meantime, a temporary workaround is to add the CwlUtils Xcode project from the Carthage Checkout
folder into the Xcode workspace with the app and build against that.
FWIW, 2.0.0-beta.13 now builds for me using Carthage. Didn’t try the betas in between.
Yes, the fixes should be in CwlSignal beta 10 and CwlUtils beta 6 and onwards. I'm leaving the two issues open at the moment while I complete some tidy ups and testing but it should work in most cases.
And then I clicked the "Close and comment" button instead of the "Comment" button. Whoops.
Okay, I implemented my planned target restructuring in CwlSignal 2.0.0-beta.18 and it looks like Carthage is still building correctly. It looks like the solution here is stable so I'm going to close this now.
Trying to install 2.0.0-beta.8 through Carthage with Xcode 8.3.3:
Am I doing something wrong? I tried 1.x, but that also fails to install through Carthage for a different reason.