XcodeGen is a command line tool written in Swift that generates your Xcode project using your folder structure and a project spec.
The project spec is a YAML or JSON file that defines your targets, configurations, schemes, custom build settings and many other options. All your source directories are automatically parsed and referenced appropriately while preserving your folder structure. Sensible defaults are used in many places, so you only need to customize what is needed. Very complex projects can also be defined using more advanced features.
- ✅ Generate projects on demand and remove your
.xcodeprojfile from git, which means no more merge conflicts!
- ✅ Groups and files in Xcode are always synced to your directories on disk
- ✅ Easy configuration of projects which is human readable and git friendly
- ✅ Easily copy and paste files and directories without having to edit anything in Xcode
- ✅ Share build settings across multiple targets with build setting groups
- ✅ Automatically generate Schemes for different environments like test and production
- ✅ Easily create new projects with complicated setups on demand without messing around with Xcode
- ✅ Generate from anywhere including on CI
- ✅ Distribute your spec amongst multiple files for easy sharing and overriding
- ✅ Easily create multi-platform frameworks
- ✅ Integrate Carthage frameworks without any work
Given a very simple project spec file like this:
name: MyProject options: bundleIdPrefix: com.myapp targets: MyApp: type: application platform: iOS deploymentTarget: "10.0" sources: [MyApp] settings: debug: CUSTOM_BUILD_SETTING: my_debug_value release: CUSTOM_BUILD_SETTING: my_release_value dependencies: - target: MyFramework - carthage: Alamofire MyFramework: type: framework platform: iOS sources: [MyFramework]
A project would be created with 2 connected targets, with all the required configurations and build settings. See the Project Spec documentation for all the options you can specify, and Usage for more general documentation.
Make sure Xcode 9.3 is installed first.
mint install yonaskolb/xcodegen
git clone https://github.com/yonaskolb/XcodeGen.git cd XcodeGen make
brew install xcodegen
Swift Package Manager
Use as CLI
git clone https://github.com/yonaskolb/XcodeGen.git cd XcodeGen swift run xcodegen
Use as dependency
Add the following to your Package.swift file's dependencies:
.package(url: "https://github.com/yonaskolb/XcodeGen.git", from: "1.0.0"),
And then import wherever needed:
This will look for a project spec in the current directory called
xcodegen --help to see the list of options:
- --spec: An optional path to a
- --project: An optional path to a directory where the project will be generated. By default this is the directory the spec lives in.
- --quiet: Suppress informational and success messages.
git clone https://github.com/yonaskolb/XcodeGen.git cd XcodeGen swift package generate-xcodeproj
This use Swift Project Manager to create an
xcodeproj file that you can open, edit and run in Xcode, which makes editing any code easier.
If you want to pass any required arguments when running in Xcode, you can edit the scheme to include launch arguments.
- See Project Spec documentation for all the various properties and options that can be set
- See Usage for more specific usage and use case documentation
- See FAQ for a list of some frequently asked questions
- See Examples for some real world XcodeGen project specs out in the wild
This tool is powered by:
Inspiration for this tool came from:
Pull requests and issues are welcome
XcodeGen is licensed under the MIT license. See LICENSE for more info.
Help us keep the lights on
1.11.1 - Aug 22, 2018
1.11.0 - Aug 19, 2018
showEnvVarsto build scripts to disable printing the environment 351 @keith
aggregateTargets353 381 @yonaskolb
- Added ability to specify
copyFilesbuild phase for sources 345 @brentleyjones
- Added ability to specify a
- Sort files using localizedStandardCompare 341 @rohitpal440
- Use the latest
xcdatamodelwhen sorted by version 341 @rohitpal440
- Fixed compiler flags being set on non source files in mixed build phase target sources 347 @brentleyjones
options.xcodeVersionnot being parsed 348 @brentleyjones
- Fixed non-application targets using
carthage copy-frameworks361 @brentleyjones
xccurrentversionif available 364 @rpassis
- XPC Services are now correctly copied 368 @brentley
.metalfiles being added to resources 380 @vgorloff
- Improved linking for
static.librarytargets 352 @brentleyjones
- Changed default group sorting to be after files 356 @yonaskolb
Productstop level groups to bottom 356 @yonaskolb
modulemapfiles are automatically copied to the products directory for static library targets 346 @brentleyjones
- Public header files are automatically copied to the products directory for static library targets 365 @brentleyjones
- Swift Objective-C Interface Header files are automatically copied to the products directory for static library targets 366 @brentleyjones
FRAMEWORK_SEARCH_PATHSare adjusted for
frameworkdependencies 373 @brentley
- Copy files phases have descriptive names 360 @brentley
- Moved brew formula to homebrew core
1.10.2 - Jul 5, 2018
transitivelyLinkDependenciesto false by default