You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working with both XcodeGen and Tuist for testing my Xcode projects. During my setup, I've observed that the incremental builds are handled differently between these two tools. Specifically, I've noticed that:
Xcodegen: Produces serial incremental builds. Tuist: Produces parallel incremental builds for the same setup.
It's possible that it may not be an issue with Xcodegen but with this llbuild issue. However, given that Tuist-generated projects benefit from parallel incremental builds, it suggests that the issue might not lie with llbuild itself or maybe tuist generated projects have some workaround(potentially few settings that Xcode requires) that can also be applied to XcodeGen generated projects.
Are there any known differences in how Xcodegen and Tuist configure project settings that could explain this discrepancy in incremental builds parallelism?
I've been working with both XcodeGen and Tuist for testing my Xcode projects. During my setup, I've observed that the incremental builds are handled differently between these two tools. Specifically, I've noticed that:
Xcodegen: Produces serial incremental builds.
Tuist: Produces parallel incremental builds for the same setup.
It's possible that it may not be an issue with Xcodegen but with this llbuild issue. However, given that Tuist-generated projects benefit from parallel incremental builds, it suggests that the issue might not lie with llbuild itself or maybe tuist generated projects have some workaround(potentially few settings that Xcode requires) that can also be applied to XcodeGen generated projects.
Are there any known differences in how Xcodegen and Tuist configure project settings that could explain this discrepancy in incremental builds parallelism?
Repro: https://github.com/chiragramani/Xcode-Serial-Incremental-Builds
The text was updated successfully, but these errors were encountered: