Posts

Post marked as solved
6 Replies
4.1k Views
Hey All,I'm wondering if someone could give me some help on something somewhat complex.To start, I need to run you through the current project structure.We have a CPP project which is built via clang via xcodebuild which is included as a submodule in the top-level iOS repo.Initially, if you were to clone the repo and open it in Xcode (11.3.1), you'd notice that the CPP xcodeproj is broken.That is because there is a pre-build run-phase script which initialises the submodule, then runs CMake on it and generates that broken xcodeproj (it has other submodule dependencies of it's own, of course!) - if it hasn't already been, or if there is some force-rebuild flag set.In Xcode, besides the slightly strange UX of no progress indicator without going to the Report Navigator, The CMake command executes just fine, but then the xcodebuild command that was kicked off does not build any of this recently added CPP code. However, some amount of restarting XCode and cleaning and clearing derived data generally does the trick and I get a green build.I can, slightly unwillingly, just invoke that CMake command prior to doing anything in Xcode, but I would really like the process to remain as simple as possible (as in, as close to just CMD+B as possible - without complicating the workflow and jumping into a terminal process to run a bunch of stuff).Does anyone know if it is possible to achieve a CMD+B with metabuild tools generating xcodeproj stuff as it goes?
Posted Last updated
.