![]() ![]() ![]() I use it at work, so it’s already familiar. If other people like it, that’s awesome, though.Įnter bazel. The short answer is that XCode is too damn complicated for me. Never really figured out how to do proper unit testing with XCode, either. This works OK until you have to make edits to “some massively shared function in a header” and rebuild everything just to test it. So I was working out of one file and using multiple targets. ![]() I don’t want my project folders filled with XCode junk. I believe in XCode, doing this “the right way” means having several interdependent projects and switching between them. If I’m going to build lots of plugins, I might as well share code between them. The reason I switched has more to do with trying to scale to larger projects. Either because that’s the way it is or because I wasn’t following some proper workflow, I never got really comfortable. ![]() I had a tendency to want to make new files in XCode and then I occasionally had to go back and tell Projucer about them. I felt like I was always struggling to keep Projucer in sync with XCode. I’ve never been a big fan of XCode (save it’s debugger) and I never really got the hang of how Projucer and XCode worked together. I started working in Juce in XCode a few years back. Thanks, that actually helps a - This may be a longer answer than you’re looking for. I’ll have to compile them as ObjC++ targets then. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |