Project

synx

2.0
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
A command-line tool that reorganizes your Xcode project folder to match your Xcode groups Synx parses your .xcodeproj to build the same group structure out on the file system.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.6
~> 0.9
~> 10.3
~> 2.14

Runtime

~> 0.6
~> 0.7
~> 1.0
 Project Readme

synx logo

Gem Version Build Status

A command-line tool that reorganizes your Xcode project folder to match your Xcode groups.

synx gif

Xcode

synx Xcode

Finder

synx finder before/after

Installation

$ gem install synx

Usage

Basic

⚠️ WARNING: Make sure that your project is backed up through source control before doing anything ⚠️

Execute the command on your project to have it reorganize the files on the file system:

 $ synx path/to/my/project.xcodeproj

It may have confused CocoaPods. If you use them, execute this command:

$ pod install

You're good to go!

Advanced

Synx supports the following options:

  --prune, -p                   remove source files and image resources that are not referenced by the the Xcode project
  --no-color                    removes all color from the output
  --no-default-exclusions       doesn't use the default exclusions of /Libraries, /Frameworks, and /Products
  --no-sort-by-name             disable sorting groups by name
  --quiet, -q                   silence all output
  --exclusion, -e EXCLUSION     ignore an Xcode group while syncing

For example, OCMock could have been organized using this command:

$ synx -p -e "/OCMock/Core Mocks" -e /OCMockTests Source/OCMock.xcodeproj/

if they had wanted not to sync the /OCMock/Core Mocks and /OCMockTests groups, and also remove (-p) any image/source files found by synx that weren't referenced by any groups in Xcode.

Contributing

We'd love to see your ideas for improving this library! The best way to contribute is by submitting a pull request. We'll do our best to respond to your patch as soon as possible. You can also submit a new Github issue if you find bugs or have questions. :octocat:

Please make sure to follow our general coding style and add test coverage for new features!

Contributors