He will be back on Monday, I’ll ask him to post this here. Unfortunately I don’t know how it works, but Fabian does. I believe there is another way of “saving” your custom schemes and re-applying them after you re-saved the project, something involving exporting and importing schemes. The reason is that in JUCE 4.2, the Projucer needs to create multiple targets for your audio plug-in, and for every new target Xcode will generate a new scheme. And yes, any such custom scheme will be overwritten next time you save the project from the Projucer. If you want your custom scheme to have even less clicks, then yes you have to create it yourself. It also works for the “Build all” scheme so if you want to build all formats (VST, AAX, …) at once you do not have to switch debug/release for all of their schemes, just the “Build all” one. Open Xcode Go to Xcode preferences (CMD+,) Find the Location tab In the last drop down (Command line tools), select the appropriate Xcode version. It’s exactly four clicks that take me about 5 seconds. But many of my beta-testers (including myself) are still running OS 3.1.x (the last version) and may not upgrade to iOS4 because it slows down their phone to a crawl (mostly for those with 3G. Open your Xcode up, head to the menu bar, and select Xcode > About Xcode. The way I always switched between debug and release in Xcode, for my whole developer life, was like this: click on the scheme, Edit scheme…, Run, Info Build configuration. I upgraded to Xcode 3.2.3 with the latest iPhone SDK version 4 and I know that in order to publish in the App Store, your app has to be iOS (SDK 4) ready.
0 kommentar(er)
