Tuist
XcodeGen
Our great sponsors
- Appwrite - The open-source backend cloud platform
- Onboard AI - Learn any GitHub repo in 59 seconds
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
| Tuist | XcodeGen | |
|---|---|---|
| 13 | 8 | |
| 3,803 | 6,502 | |
| 2.2% | - | |
| 0.0 | 0.0 | |
| 6 days ago | 13 days ago | |
| Swift | Swift | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Tuist
-
🚀 XBase 0.2: Now with Tuist, Swift, and barebone xcodeproj support!
Tuist Projects ('Project.swift'), Swift packages ('Package.swift'), and barebone xcodeproj are now supported.
-
How to manage a huge iOS project written by many teams?
On a project I worked on I transitioned the codebase to a micro framework setup using tuist.io.
-
Why the hate on Xcode?
I think the hate comes from seeing its unresponsiveness and slow builds in large-scale projects. Everything works great in a recently-creates project until your project turns into a complex dependency graph of targets with intricate and inconsistent build settings. That’s the main reason why we are building https://tuist.io
- Evitando conflitos no Xcode
-
How to better structure your Xcode projects
Curious why you guys built XCodeJS instead of going with XcodeGen or Tuist
-
Xcode Project Repository
You can take a look at tuist fixtures for examples of xcode projects https://github.com/tuist/tuist/tree/main/fixtures
XcodeGen
-
How to manage a huge iOS project written by many teams?
There are a lot of tools and solutions that can help manage a large codebase. For example, a good CI/CD system linked to GitHub or your internal source control system can ensure that all of your unit tests and UI tests run on every PR and block PRs from merging if there are test failures. And if the company chooses not to check in the .xcodeproj or .xcworkspace file, but rather rely on project autogeneration tools like xcodegen, then you can eliminate annoying merge conflicts in PRs that happen when two teams happen to touch files that are near each other in the .pbxproj file (but at the cost of developers always having to run xcodegen when checking out a new branch).
-
How to better structure your Xcode projects
Curious why you guys built XCodeJS instead of going with XcodeGen or Tuist
-
The joys of creating Xcode project files
It's such trash. For my personal projects, XcodeGen is a lifesaver.
How Apple thinks that a single god file is a good idea is crazy to me. No other build tool needs this.
What are some alternatives?
SwiftGen - The Swift code generator for your assets, storyboards, Localizable.strings, … — Get rid of all String-based APIs!
R.swift - Strong typed, autocompleted resources like images, fonts and segues in Swift projects
fastlane-plugin-appicon - Generate required icon sizes and iconset from a master application icon.
Struct - Xcode projects on steroids
xcbuild - Xcode-compatible build tool.
xcproj - đź“ť Read, update and write your Xcode projects
SwiftPlate - Easily generate cross platform Swift framework projects from the command line
jazzy - Soulful docs for Swift & Objective-C
amaro
crafter - Crafter - Xcode project configuration CLI made easy.
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
xclint