@tuistio
Tuist
4 years
Scaling Xcode projects being like without Tuist. We start a thread ๐Ÿ‘‡
1
3
17

Replies

@tuistio
Tuist
4 years
I need to share code across targets: Solution: I extract code into frameworks
1
0
0
@tuistio
Tuist
4 years
But now I have many projects containing frameworks. I have no idea of what depends on what and inconsistencies cause sporadic errors. Solution: I describe my projects in YAML files
1
0
1
@tuistio
Tuist
4 years
But now I have many YAML files instead of many Xcode projects. Solution: I build a tool that generates YAMLs to generate projects
1
0
0
@tuistio
Tuist
4 years
But wait... my compilations are still slow. Solution: I add Carthage and Rome to the mix to have some targets pre-compiled.
1
0
1
@tuistio
Tuist
4 years
But wait again... I really want to use packages instead of that Carthage thing. I want to follow Appleโ€™s way. Solution: compilation times are not that much of a problem if I can have Swift Packages too.
1
0
1
@tuistio
Tuist
4 years
The result: - Projects in generated YAMLs - A tool to generate YAMLs - Carthage, Rome - Swift Packages - Fastlane - A tool that turns Bazel files into YAMLs. ๐Ÿคฆ
1
0
2
@tuistio
Tuist
4 years
Scale shouldnโ€™t mean a complex setup. With Tuist you just need Tuist. You take care of building your apps - we take care of the rest.
0
0
5