Do you use Carthage? Are you feel tired of adding special script and the paths to frameworks (point 4, 5 and 6 in Getting Started guide) manually? Me too. Carting does it for you. It scans Carthage folder and linked frameworks, gets framework names and updates the script.
Run carting update
in project folder. That's all.
By default Carting searches a script named Carthage
, but you can set a name of your script via command line arguments:
$ carting update -s MyBestScript
If there is no script with the name, Carting will add a new one.
🚨Note: be sure to have no uncommitted changes in project file to prevent project parsing errors 😱.
Run carting help
to see available commands:
Usage: carting [command] [options]
update:
Adds a new script with input/output file paths or updates the script named `Carthage`.
-s, --script:
Updates input/output file paths for the script with passed name.
-p, --path:
The project directory path.
list:
Prints Carthage frameworks list with linking description.
help:
Prints this message.
$ brew install artemnovichkov/projects/carting
$ git clone https://github.com/artemnovichkov/carting.git
$ cd Carting
$ make
let package = Package(
dependencies: [
.Package(url: "https://github.com/artemnovichkov/carting", majorVersion: 1)
]
)
- Install Marathon.
- Add Carting to Marathon using
$ marathon add git@github.com:artemnovichkov/carting.git
. Alternatively, addgit@github.com:artemnovichkov/carting.git
to yourMarathonfile
. - Write your script, then run it using
$ marathon run <path-to-your-script>
.
- Add option for adding new script
- Add support of multiple targets
- Add check of linked frameworks
- Unify errors
- Add support of tvOS and watchOS platforms
- Check correct work with workspaces
- Write tests
Artem Novichkov, novichkoff93@gmail.com
Carting is available under the MIT license. See the LICENSE file for more info.