obakit
XcodeGen
| obakit | XcodeGen | |
|---|---|---|
| 2 | 8 | |
| 3 | 6,797 | |
| - | - | |
| 0.0 | 8.0 | |
| about 3 years ago | 10 days ago | |
| Swift | Swift | |
| GNU General Public License v3.0 or later | 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.
obakit
-
The joys of creating Xcode project files
I cannot imagine working on an iOS application that is meant to be maintained by multiple people that does not use Xcodegen.
Additionally, it is the only sane way I've found of handling whitelabel application development. Here's an example for anyone who wants to see it in action: https://github.com/onebusaway/obakit
- OBAKit – A total rewrite of the OneBusAway transit app in Swift
XcodeGen
-
Would creating a new Xcode project cause significant merge conflicts?
Worth noting if project file changes would be pretty common in the development flow then maybe using a regen tool would be useful to prevent major conflicts, I’d recommend https://github.com/yonaskolb/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).
-
brew install xcodegen
`git clone https://github.com/yonaskolb/XcodeGen.git cd XcodeGen make install`
-
Do Xcode from command line
Parent comment is right, but check out XcodeGen and get away from the project file. It’s an abomination.
- missing project.pbxproj file, how to restore it?
-
The project ‘Project-Name’ is damaged and cannot be opened due to a parse error
I don't see anything wrong with your gitignore. If this is causing too many problems, have you considered using a tool that will generate xcodeproj files for you, like XcodeGen?
-
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.
https://github.com/yonaskolb/XcodeGen
What are some alternatives?
cordova-node-xcode - Apache cordova
Tuist - 🚀 Create, maintain, and interact with Xcode projects at scale
objc-lisp-bridge - A portable reader and bridge for interacting with Objective-C and Cocoa
SwiftGen - The Swift code generator for your assets, storyboards, Localizable.strings, … — Get rid of all String-based APIs!
Xcodeproj - Create and modify Xcode projects from Ruby.
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.
jazzy - Soulful docs for Swift & Objective-C
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
Awesome-Design-Tools - The best design tools and plugins for everything 👉