Install xcodegen with Homebrew, MacPorts, Nix

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• xcodegen

Project history

Yonas Kolb created the XcodeGen repository on 2017-07-19, and the first 0.1 release followed on 2017-07-28. The README has consistently positioned the tool around generating an Xcode project from a folder structure and project spec, with sensible defaults for common targets, schemes, configurations, build settings, and source references.

Across the 2.x series, XcodeGen became a maintained part of the Swift/Xcode automation ecosystem rather than a one-off generator. Its changelog shows ongoing adaptation to newer Xcode project formats, Swift Package Manager integration, local packages, visionOS/watchOS destinations, string catalogs, privacy manifests, and Xcode 16 synchronized folders.

Adoption history

The repository's long-running contributor base and thousands of GitHub stars show broad adoption among iOS and macOS developers who prefer a text source of truth over hand-edited .xcodeproj files. Articles and community comparisons commonly place XcodeGen beside Tuist as one of the main answers to generated Xcode projects, with XcodeGen favoring declarative YAML or JSON configuration.

The project is also distributed through multiple developer package channels, including Homebrew, MacPorts, Nix, Mint, and Swift Package Manager. That spread matters because XcodeGen is often run on CI or developer bootstrap scripts before Xcode itself opens the generated project.

How it is used

Typical use starts with a project.yml or project.json file checked into the repository. Running xcodegen generate reads that spec, scans source directories, and writes an .xcodeproj. Teams may then omit generated project files from version control or regenerate them in CI to avoid pbxproj churn.

Advanced usage includes splitting specs into included files, sharing build setting groups, generating multiple schemes, defining multi-platform frameworks, using cache support to avoid unnecessary regeneration, and dumping the resolved spec for inspection or automation.

Why package nerds care

XcodeGen is package-nerd significant because it treats an opaque IDE project file as a generated artifact. That makes Xcode projects more like other language ecosystems where build configuration is text, diffable, and reproducible, while still targeting Apple's native .xcodeproj format.

Timeline

• 2017-07-19: Repository created on GitHub.
• 2017-07-28: 0.1 release published.
• 2024-06-03: 2.39.0 added support for artifact bundles, string catalogs, and visionOS defaults.
• 2025-07-17: 2.44.0 added basic support for Xcode 16 synchronized folders.
• 2026-04-14: 2.45.4 released with fixes for generated project path and synchronized folder behavior.

Related projects

• Tuist is the most common point of comparison: both generate or manage Xcode projects, but Tuist centers more of the workflow in Swift manifests and a broader project automation platform, while XcodeGen stays close to YAML/JSON project specifications.
• XcodeGen depends conceptually on the same Xcode project-file automation niche as libraries such as XcodeProj, which parse and write pbxproj structures.

Sources

• https://github.com/yonaskolb/XcodeGen
• https://github.com/yonaskolb/XcodeGen/blob/master/CHANGELOG.md
• https://github.com/yonaskolb/XcodeGen/releases
• https://tuist.dev/blog/2025/02/25/project-generation
• https://yonaskolb.github.io/XcodeGen