"-project", "/path/to/your/project.xcodeproj", "-alltargets", "-configuration", "Debug", "SYMROOT=~/Library/Developer/Xcode/DerivedData" I want xcodebuild to use the same path as xcode. otherwise it will put its temporary build files in the project directory. note that I set a SYMROOT that matches xcode's default derived data path, Compiling the Debug configuration is fast. UPDATE: xcodebuild was only slow because I was compiling the Release configuration. For now I will keep using Xcode for compiling For example, if I make a minor code change then the project will recompile in Xcode in a second or two, but xcodebuild seems to do a full recompile, which takes 20-30 seconds. Unfortunately xcodebuild’s build times are much slower than Xcode’s, and I don’t know why. This lets you compile without leaving VS Code It uses xcodebuild on the command line, which is equivalent to compiling from the Xcode application. I have also configured a build task as described here. The C/C++ plugin required some minor configuration to let it find Juce’s modules, so that Intellisense works, as described here. Seems good to me, but I’m not very experienced with C++ so I’m afraid I can’t give a detailed comparison with Xcode. I have been using the C/C++ plugin for vscode mentioned above.
Until now I have been using Xcode, but I am so used to VS Code that it is a pain switching back and forth. I have been using VS Code for about 6 months for my day job (front end web dev), and am trying it out for Juce/C++ projects.
0 kommentar(er)
