One Build System to Rule Them All
summary
Describes how to stop hardcoding an iOS project's build description and instead implement an abstract build system with caching. The proposed system provides a layer that can plug in different concrete builders (for example Tuist or Bazel) so teams can evaluate and switch build tools without rewriting project files.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:57Build system dependency problems
- 10:48Dynamic generation solution
- 20:45Practical: base and cache
- 31:04Results and benchmarks
- 35:23Summary and outlook
related talks
38mHacks and Tips for Incremental Adoption of Bazel for iOS
44mMigrating Lyft-iOS to Bazel + Q&A
19mFeature toggles with BuildConfiguration and type-safe definitions
01h 00m3rd party tools and frameworks you use in your applications and why
08mPërparësitë dhe mangësitë e iOS Dependency Managers
45mfunc inspiration
25mFaster Builds With Xcode Compilation Cache
55mMonorepo: The Journey Back. The Story of Modularization