I was going to delete my local repos and try starting over - I think I've successfully kept all the remotes updated and all the links are to remotes, so it should work
ah jinx
@jeremybarnum your cartfile for G4ShareSpy points to
github "LoopKit/dexcom-share-client-swift" "carthage-recursive” but your Loop cartfile points to github "jeremybarnum/dexcom-share-client-swift" "carthage-recursive-custom-loopkit”
ok looks like a clean carthage build starting now. I got one before - I have no idea what I did that backed out the change. Thanks Katie.
@jeremybarnum I also run
carthage update in my frameworks individually and commit the result into my repo/branch so that the carthage.resolved is correct too. If you have bootstraps going (which I believe Loop does), the resolved should be updated to reflect the correct commit. I’m not certain of the bootstraping that may/may not happen…but I did avoid/solve some problems awhile ago with that step implemented. Can’t remember what the root issue was that brought me to that, but it’s a regular habit for me now
BUT I’m not a carthage speaker
lol
not by a long shot
but just curious -
my loop cartfile refers entirely to remote repos - both for the standard frameworks and for anything i've customized. So I always assumed that when I ran carthage update, it was downloading those files from the git hub, and building the frameworks somewhere inside the carthage folder in loop or something like that - in other words, that to the extent that I had cloned repos of the frameworks locally that I had used to do modifications, once I pushed those back up, whatever goes on inside those local repos would be irrelevant?
you mean before pushing the local repo of the frameworks back up, you run carthage update inside the local folder - which makes the carthage.resolve file that is uploaded correct?
Interesting
When @ps2 said the workspace thing makes this easier, do you think it includes this sort of thing?
If you look at your cartfile.resolved for the various frameworks, you’ll see different commit SHA for the same “branch” of loopkit calls…so some of your resolved for loopkit resolve to c70d3f5 (which is the right, most current one) and most of the others go to f13026 (an outdated commit from another branch I think…I didn’t look too hard for where it was). So…to keep things as neat and tidy as possible, I run carthage update (or edit the cartfile.resolved) for the frameworks to make sure they are all resolving to the most current commit. Now, this used to be much easier when it was all just one cartfile in rileylink_ios…but now that things are getting distributed more broadly, it’s more headache. So yes, workspace would help this too.
let's see if I can build after this carthage update and if not I'll run it in the frameworks and push those back up and run update again and see
So getting a good Carthage build at least once seems to be sometimes necessary, for reasons I don’t really understand. Be the premise of the workspace setup is that it doesn’t depend on carthage at all. Xcode will build everything and find all the dependencies. It just sometimes has trouble if the Carthage products aren’t in place initially.
Well
I'll see if I can figure out the workspace now...I don't think I can handle going through that again!
fwiw, this page has some good fairly plain language explanations https://github.com/Carthage/Carthage/blob/master/Documentation/Artifacts.md
@ps2 can you recommend any reference sources that are more newbie-friendly than your wiki for workspaces? I'll try now anyway and see - maybe it's not that bad.
should I run carthage update in the local framework folders before dragging them in? No harm I guess?