Migrating a multiple-platform game engine to Bazel
summary
NeoX moves from CMake/Conan to Bazel for Windows, iOS and Android with IDE integration for Visual Studio, Xcode, Android Studio and remote execution; a Python remote worker for Windows and macOS is open sourced. Incremental migration keeps CMake projects working while converting libraries, using Conan’s Bazel generator changed to http_archive for reproducible deps. Compilation databases plus a Python fixer correct include paths; circular deps are worked around with stub headers. Real results: Windows full build 27→4 min, iOS/Android ≈2.5 min.
AI-written summary · about
chapters (14)
- 0:00Migration journey overview
- 1:50Multiplatform build challenges
- 3:38Bazel migration milestones
- 5:46Hybrid CMake integration
- 7:11Third-party dependencies in Bazel
- 8:58Include path and circular dependencies
- 11:27Linking model adjustments
- 13:13IDE integration with Bazel
- 14:39Remote caching setup
- 16:46Windows cache sharing issues
- 19:19Remote execution with Build Farm
- 20:50Custom Windows worker
- 22:38Remote execution tips
- 23:19Future plans and closing
related talks
30mA Deep Dive into a Cross-Platform Build Farm
21mA journey to fullstack mobile game development in Rust
36mCrafting Cross-Platform Adventures: Building a Game Engin…
54mOptimizing Game Development Workflows with Visual Studio and AI
38mGrowing a Healthy UE4 Ecosystem
26mFrom Unity to Unreal: Codebase Design for an Indie Mobile VR Game
41mCRYENGINE
24mJourney to Fullstack Mobile Game Development in Rust