🚘 A simple tool for updating Carthage script phase

What did you do?

brew upgrade carting

What did you expect to happen?

• Successfully upgrade to v1.3.3

What happened instead?

Error: An exception occurred within a child process:
  ChecksumMismatchError: SHA256 mismatch

Thanks for the great tool!

I have a (pre-existing) project, a framework, that uses Carthage. I clone it out, do carthage update --platform ios and then carting update.

🤷‍♂️ Nothing to update.

Hm...there's no Carthage script, no xcfilelists or anything. Building the project errors because the frameworks are missing. It seems like carting update is a complete no-op.

carting info

I get some results, for example:

SwiftSoup.framework dynamic i386, x86_64, armv7, arm64

Okay, so Carting knows that the frameworks are there, why is update not doing anything?

In fooling around, I tried the --target flag giving the name of my framework target within the project, and I get Error: There is no target with <argument> name.

I feel like I may be doing something wrong or have some rather large misconception; I'm used to carthage update, drag the frameworks into Frameworks and Libraries, and carting update to finish it off. I confess to be fairly ignorant as to the deep inner workings of linking frameworks and such business. Any help would be appreciated and if there's a bug I can do a PR.

Totally disrelated, but I spotted it whilst fooling around:

~/g/project> carting help update
OVERVIEW: Adds a new script with input/output file paths or updates the script named `Carthage`.

USAGE: carting update [--script <script>] [--path <path>] [--format <format>] [--target <target>] [--project-names <project-names> ...]

OPTIONS:
  -s, --script <script>   The name of Carthage script. (default: Carthage)
  -p, --path <path>       The project directory path. (default: nil)
  -f, --format <format>   Format of input/output file paths: file - using simple paths, list - using xcfilelists (default: list)
  -t, --target <target>   The project directory path. (default: nil)
  -n, --project-names <project-names>
                          The names of projects.
  -h, --help              Show help information.

The description for the --target flag seems wrong! It's the same as the --path flag.

.xcodeproj exists in the current directory, so I'm not sure how to fix this error. Previous versions worked, but since updating to 2.0 today, I get this error.

==> Installing carting from artemnovichkov/projects ==> Downloading https://github.com/artemnovichkov/Carting/archive/1.3.5.tar.gz ==> Downloading from https://codeload.github.com/artemnovichkov/Carting/tar.gz/1.3.5 ######################################################################## 100.0% ==> make install PREFIX=/usr/local/Cellar/carting/1.3.5 Last 15 lines from /Users/jombay/Library/Logs/Homebrew/carting/01.make: 2019-04-23 12:17:29 +0530

make install PREFIX=/usr/local/Cellar/carting/1.3.5

swift build --disable-sandbox -c release dyld: Library not loaded: @rpath/llbuild.framework/Versions/A/llbuild Referenced from: /Library/Developer/CommandLineTools/usr/bin/swift-build Reason: image not found make: *** [build] Abort trap: 6

Hey,

I just wanted to ask if the behavior of carting is as expected. I updated every piece of software on our CI-Machine and carting had a change in behavior, to be precise when no dependency was added it now returns an error code in the command line when reporting "Nothing to update.". Because of this we had to change the way the dependencies are handled in the CI-Pipeline by checking in the xcfilelists which we until now hadn't checked in into version control. So we now have to run the command when adding a dependency on the developer's machine. This is absolutely no issue for us, was just a change that we didn't expect.

So to reiterate my question: Is it expected behavior that carting reports an error on the command line when there's nothing to update?

Environment

Carting version: 1.3.2 macOS version: 10.15.7 Xcode version: 12.1 Installed via (mint, brew): brew + mint What did you do?

Mint

mint run artemnovichkov/carting

Brew

brew tap artemnovichkov/projects brew install carting

What did you expect to happen?

successful installation of Carting

What happened instead?

Mint

🌱 Finding latest version of carting 🌱 Cloning carting 2.1.4 🌱 Resolving package 🌱 Building package 'Carting' /private/var/folders/cw/zks9qq_527l82gdr79kyl_zm0000gn/T/mint/github.com_artemnovichkov_carting: warning: ignoring duplicate product 'Carting' 'XcodeProj' /private/var/folders/cw/zks9qq_527l82gdr79kyl_zm0000gn/T/mint/github.com_artemnovichkov_carting/.build/checkouts/xcodeproj: error: Source files for target XcodeProj should be located under 'Sources/XcodeProj', or a custom sources path can be set with the 'path' property in Package.swift 🌱 Encountered error during "swift build -c release -Xswiftc -target -Xswiftc x86_64-apple-macosx10.15". Use --verbose to see full output

Brew

==> Installing carting from artemnovichkov/projects ==> Downloading https://github.com/artemnovichkov/Carting/archive/2.1.4.tar.gz ==> Downloading from https://codeload.github.com/artemnovichkov/Carting/tar.gz/2.1.4 #=#=#
==> make install PREFIX=/usr/local/Cellar/carting/2.1.4 Last 15 lines from /Users/alexanderpuchta/Library/Logs/Homebrew/carting/01.make: Cloning https://github.com/kylef/PathKit Resolving https://github.com/kylef/PathKit at 1.0.0 Cloning https://github.com/apple/swift-argument-parser Resolving https://github.com/apple/swift-argument-parser at 0.0.1 Cloning https://github.com/tadija/AEXML Resolving https://github.com/tadija/AEXML at 4.4.0 Cloning https://github.com/JohnSundell/ShellOut.git Resolving https://github.com/JohnSundell/ShellOut.git at 2.2.0 Cloning https://github.com/tuist/xcodeproj.git Resolving https://github.com/tuist/xcodeproj.git at 7.0.1 Cloning https://github.com/JohnSundell/Files.git Resolving https://github.com/JohnSundell/Files.git at 3.1.0 'Carting' /private/tmp/carting-20201109-11556-urgg2r/Carting-2.1.4: warning: ignoring duplicate product 'Carting' 'XcodeProj' /private/tmp/carting-20201109-11556-urgg2r/Carting-2.1.4/.build/checkouts/xcodeproj: error: Source files for target XcodeProj should be located under 'Sources/XcodeProj', or a custom sources path can be set with the 'path' property in Package.swift make: *** [build] Error 1

When I launch carting update on my project it creates a new "Carthage" build phase for unit tests target too. The Carthage tutorial says that copy-frameworks action is not needed for unit tests and it's very annoyable to deleting this script each time. Or maybe I doing something wrong?

I am using carting 1.3.2. After dragging new carthage frameworks to the project and adding them to the targets, I run carting update to update the build script. The xcfilelists are updated correctly, but carting returns "🤷‍♂️ Nothing to update.".

Hey @artemnovichkov!

I’m looking at using Carting for a project I’m working on. However I’d like to be able to have Carting only update the xcfilelist. This is because I don’t want or need any scripts to update the build phase. I’ve added it already for our current Carthage integration, it’s also a bit custom where we perform some additional work. So I need to keep maintain that manually.

What do you think about such an option to disable changing the Xcode project file? And just read the Xcode project and Carthage output to update the xcfilelist. If you’re open to it I’d be willing to make the necessary changes.

Hi, since last update I am experiencing a problem, that everytime I run carting update -f file (it doesn't matter if I use file or list format), I end up with all custom build phases removed.

I was trying to create a minimal project which has this issue but in clean project it worked just fine. Our project template has this issue.

Do you have an idea what might be the problem? The 1.2.15 version works just fine.

carting update or carthage list hang if there is space in project folder

For carthage list I see in FrameworkInformationService

        let fileOutput = try shellOut(to: "file", arguments: [path])
        let lipoOutput = try shellOut(to: "lipo", arguments: ["-info", path])

By escaping path

        let fileOutput = try shellOut(to: "file", arguments: ["'\(path)'"])
        let lipoOutput = try shellOut(to: "lipo", arguments: ["-info", "'\(path)'"])

I have no more issue

If path must be escaped, a lot of shellOut must be edited and I do not know If this could add new issues.

Hi,

This looks like a great tool, and very keen to use it. Only problem right now is it doesn't include the contents of Cartfile.private, so currently have to manually add these.

Carting saves filelists to Carthage folder by default. But often this folder is in gitignore. Just think about paths or at least info in readme about this case.

Paths for debugging frameworks like Hyperion-iOS should not be added. So I need a simple approach to mark these frameworks for ignoring, for example in Cartfile: github "willowtreeapps/Hyperion-iOS" #carting.ignore

Use case: I updated Carthage with only one new framework, RxSwift for example. Because I know the name of the framework, I don't want to link it to the target manually, I want to run:

carting update RxSwift

This command will check the framework with the name in Carthage folder, link it to the target and update the script