Post #2135899
2026-04-28 23:02 UTC
Adopting building folders in my Xcode projects means that adding or removing source files does not touch the project file. And adopting xcconfig files means modifying build setting does not touch the project file either. Now the only times I get merge conflicts in the project file are when two branches add swift packages at the same time, which is pretty rare. So for me, project generation tools (XcodeGen, Tuist, etc) don’t have a strong ROI, but maybe I’m missing something.
Replies (2)
-
@ScottBerrevoets@hachyderm.io 2026-04-28 23:47
@calicoding@mastodon.social feeling the same, although I think with more modules the pains of managing those also becomes greater and that’s something tuist may still be able to help with
-
@mattiem@mastodon.social 2026-04-29 09:26
@calicoding@mastodon.social i use a slightly modified version of this technique. It’s imperfect, but does the job. https://kean.blog/post/swiftpm-and-xcode