Dynamically generated Info.plist files with Tuist 0.15.0
Tuist 0.15.0 has been been released; just in time for WWDC. On this blog post, I’d like to go through the major updates that come with this version.
If you are in San Jose during WWDC and would like to meet to chat about Tuist and Xcode at scale, let us know. Understanding how other projects use Xcode and structure their project is very valuable to improve the tool and abstract you from Xcode intricacies. I’ll also be speaking at AltConf on Thursday so come and say hola 👋.
Default settings ⚙️
Tuist used to generate the projects and targets with some default build settings. Although that worked for most of the projects, some projects wanted to have more control over that. The new version of Tuist supports passing a new attribute to the
defaultSettings. It can take any of the following values:
- .recommended: Recommended settings including warning flags to help you catch some of the bugs at the early stage of development.
- .essential: A minimal set of settings to make the project compile without any additional settings for example
This change is backwards-compatible by defaulting to
.recommended. If you want Tuist not to generate any build settings, you can pass
As you might already know, targets require an Info.plist file to be set. The content of the Info.plist files is almost identical with the exception of some attributes that are specific to the target, like the launch storyboard or the build and version numbers. Although the cost of maintenance of those files is not that high, we believe Tuist can do that work for the developer and take the opportunity to run some validations to prevent future compilation errors.
In that regard, in the new version of Tuist we’ve turned the
infoPlist attribute of
String into its own model,
InfoPlist. Although the change makes no difference for now, we are working on letting the developers pass some ownership of those files to Tuist. In the next version of Tuist developers will be able to define the Info.plist content by using the following values:
InfoPlist.dictionary(["CFBundleIdentifier", "io.tuist.MyApp"])// Extends a base list of attributesInfoPlist.base(extend: ["CFBundleIdentifier", "io.tuist.MyApp"])
Generation time ⌚️
With developers introducing Tuist into their workflows, the generation of projects must be fast. If you would like to know how much it takes, the new version of Tuist prints the total generation time:
$ tuist generateGenerating workspace App.xcworkspaceGenerating project App✅ Success: Project generated.Total time taken: 0.605s
Until this version, developers were not able to customize the list of generated schemes. That has changed and now schemes are configurable. When schemes are not passed, Tuist generates a default scheme for each target that is part of the project. The example below shows how schemes are initialized and used from a project:
let scheme = Scheme(name: "MyScheme",shared: true,buildAction: BuildAction(targets: ["App"]),testAction: TestAction(targets: ["AppTests"]),runAction: RunAction(executable: "App"))let project = Project(name: "App",schemes: [scheme])
Compiler flags 🚩
Although it’s not a commonly-used feature in Xcode, Tuist didn’t support setting compiler flags to source files. With this new version, you can now pass flags alongside the source files:
let target = Target(sources: [.init("Sources/**/*.m", compilerFlags: "my flag")])
Minor fixes and improvements 🧪
- We fixed a bug that caused the generation of projects to output Xcode projects with different format.
- Code sign on copy is now set to true by default for the frameworks in the “Embed Frameworks” build phase.
- We fixed a bug that caused files being added as folders.
- We fixed the template that we use to initialize projects so that it doesn’t throw warnings.
- We fixed an issue that caused localized resources to be duplicated in the project.
- We fixed the lint check that raised warnings when targets linked static products.
- We ensured that bundle dependencies are properly configured for Xcode to build them beforehand.
- We added support for bundle dependencies that are part of other projects.
- We added a check to make sure that only headers are being added to the generated headers build phase.
What’s next 🤔
At WWDC, Xcode support for Swift Package Manager was announced. We are excited to see Apple taking those steps and we’d like Tuist to embrace the change and integrate with it. We started working on supporting the changes to the Xcode project format with the goal of supporting defining packages as dependencies of your Tuist projects. This is how the integration might look:
let target = Target(dependencies: [.package("https://github.com/tuist/xcodeproj", .exact("1.2.3"))])