Go to file
Pedro Piñera f7c2ca7cf9 Bump core version 2018-10-05 16:50:55 +02:00
.circleci Bump xcodeproj to 6.0.0 (#133) 2018-09-19 11:44:31 +02:00
.github Rename project 2018-07-23 07:59:52 -04:00
.vscode Regenerate documentation 2018-04-20 18:09:44 +02:00
Sources Bump core version 2018-10-05 16:50:55 +02:00
Tests Bump core version 2018-10-05 16:50:55 +02:00
assets Improve README 2018-09-12 17:48:06 +02:00
docs Regenerate documentation 2018-09-26 09:43:45 +02:00
peril Add error handling check 2018-09-05 16:39:04 +02:00
script Improve script output 2018-09-20 11:15:24 +02:00
.editorconfig Add some badges 2018-04-17 10:14:48 +02:00
.gitignore Remove tuistenv from the repository (#135) 2018-09-19 18:46:49 +02:00
.jazzy.yaml Regenerate documentation 2018-09-26 09:43:45 +02:00
.prettierrc Add some badges 2018-04-17 10:14:48 +02:00
.ruby-version Add documentation generation and document the release process (#71) 2018-07-21 19:56:49 -04:00
.swift-version Bump xcodeproj to 6.0.0 (#133) 2018-09-19 11:44:31 +02:00
.swiftlint.yml Rename project 2018-07-23 07:59:52 -04:00
CHANGELOG.md Version 0.6.0 2018-09-19 18:48:22 +02:00
LICENSE.md Add LICENSE 2018-06-28 15:00:33 +02:00
Makefile Fix install script 2018-09-19 18:59:44 +02:00
Package.resolved Bump core version 2018-10-05 16:50:55 +02:00
Package.swift Bump core version 2018-10-05 16:50:55 +02:00
README.md Regenerate documentation 2018-09-26 09:43:45 +02:00
RELEASE.md Remove tuistenv from the repository (#135) 2018-09-19 18:46:49 +02:00

README.md



code style: prettier CircleCI codecov Slack

What's Tuist 🕺

Tuist is a command line tool that helps you generate, maintain and interact with Xcode projects.

It's open source and written in Swift.

Defining your projects 💼

With Tuist, projects are defined in a Project.swift, also known as manifest. The manifest format abstracts you from the implementation details of Xcode projects. In your manifest you can define which targets your project has, which sources and resources belong to them, as well as the dependencies with targets in the same and other projects. The advantages of defining the projects in a manifest are:

  • It can catch misconfigurations and fail early. For example, if a target has an invalid dependency, itll let you know before you start compiling the app.
  • Since the manifest doesnt include Xcode implementation details, the likelihood of having git conflicts is significantly lower.
  • It makes the configuration easier. The decision on how the project looks is on you. Tuist processes it and manages the complexity for you. One example of that complexity is setting up dependencies between targets.

The example below shows how projects are defined with Tuist:

import ProjectDescription

let project = Project(name: "App",
                      targets: [
                        Target(name: "App",
                               platform: .iOS,
                               product: .app,
                               bundleId: "io.tuist.App",
                               infoPlist: "Info.plist",
                               sources: "Sources/**",
                               dependencies: [
                                    /* Target dependencies can be defined here */
                                    /* .framework(path: "framework") */
                                ]),
                        Target(name: "AppTests",
                               platform: .iOS,
                               product: .unitTests,
                               bundleId: "io.tuist.AppTests",
                               infoPlist: "Tests.plist",
                               sources: "Tests/**",
                               dependencies: [
                                    .target(name: "App")
                               ])
                      ])

Although we encourage defining the manifests in Swift, Tuist also supports JSON and Yaml formats.

Interacting with your projects 🙇‍♀️

Tuist leverages project generation to provide a simple and convenient set of commands, standard across all the projects. The commands infer most of the necessary information from your projects, requiring you to pass only the arguments that are strictly necessary.

Having a standard command line interface makes it easier to jump between projects since theres an interaction language everyone in the team is familiar with.

  • 👩‍💻 Init: Bootstraps a new project. You can specify the platform and the type of project and itll generate all the necessary artifacts (Info.plist, AppDelegate, Project.swift, Playgrounds…).
  • 💫 Generate: Generates the Xcode workspace and projects to work on a particular project.
  • 📦 Build: (Not available yet) Builds the project in the current directory. It supports all the arguments that xcodebuild supports.
  • Test: (Not available yet) Test the project in the current directory. It supports all the arguments that xcodebuild supports.
  • 📱 Run: (Not available yet) Runs the project. If the project needs a device to run on, itll prompt you to select one.
  • 🚀 Release: (Not available yet) Builds and publishes your project on iTunes Connect.

The list of actions will likely grow as we get feedback from you.

Install ⬇️

Running script:

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/tuist/install/master/install)"

Bootstrap your first project 🌀

tuist init --platform ios --product application
tuist generate # Generates Xcode project

Check out the project "Getting Started" guide to learn more about Tuist and all its features.

Setup for development 👩‍💻

  1. Git clone: git@github.com:tuist/tuist.git
  2. Generate Xcode project with swift package generate-xcodeproj.
  3. Open tuist.xcodeproj.
  4. Have fun 🤖

Shield

If your project uses Tuist, you can add the following badge to your project README:

Tuist Badge

[![Tuist Badge](https://img.shields.io/badge/powered%20by-Tuist-green.svg?longCache=true)](https://github.com/tuist)

Donations

Tuist is a non-profit project run entirely by unpaid volunteers. We need your funds to pay for software, hardware and hosting around continuous integration and future improvements to the project. Every donation will be spent on making Tuist better for our users.

Please consider a regular donation through Patreon:

Donate with Patreon

Open source

Tuist is a proud supporter of the Software Freedom Conservacy

Become a Conservancy Supporter!