it's funny it's the same nested thing that overwhelmed me in CGMBLEKit that I joked about above - and I missed it here!
@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?
or it really shouldn't matter?
anyway let me just try.
well, now dragging is nice. I always took the long way uphill and used the menus. just tried it. lol
had to still use menu for those
hmm. Was looking promising all the way through step 6. Carthage build ran. But step 7 build failed. Are you supposed to build from Loop or from the workspace? I ran from the workspace. Building from Loop works, but I'm not sure that proves anything unless I make changes to frameworks and see whether they are incorporated? and, is it necessary to re-run
carthage build after changing framework code? if so, almost no time saving. OK so I will try changing something in a framework and see whether it updates without reruning carthage build
should the workspace look like that?