On Jun 6, 2005, at 9:00 PM, Brian Barnes wrote: All I ever wanted out of XCode was a single set of build settings. While it took moving to a whole new architecture (!!!) it seems I've gotten this ... but I'm not sure. I poured through the docs, but it bugs me a bit that the build settings are still in two places (the target and the project info.) They seem to represent the same list. Edits in one reflect in the other ... yet ... this is ... a bit ... confusing coming from a time when they didn't.
I just want to verify that they are in fact the same list, and maybe suggest removing the editing part from the target and just leaving the picking part (or a button to jump there.)
You can use just the settings in the target inspector if you want. That's all you need.
Build Styles are dead. The model of build styles is gone in Xcode 2.1.
Build Configurations are in 2.1, and they're different. If you want "a single set of build settings" just use the target inspector and the target inspector only and you're fine.
The build settings at the project level are provided as a convenience if you want to share common settings across all targets in a project. They're purely optional and initially empty. Unlike Build Settings, you can ignore them completely if you like. Unlike Build Settings, if you set a project setting it is inherited by all targets, rather than overriding all targets.
We want to make the target, not the project, the centre for editing settings, to make the experience more WYSIWYG. As for a "jump to there" function, you can choose "Edit Project Settings" from the Project menu, or even assign a keybinding for that if you find yourself doing it a lot. But remember that things you set at the project level affect all targets, so you need to make sure that this is what you really want to do.
For those of you at WWDC, you can come to my session at 9 a.m. Tuesday and I'll explain this in painful detail :-)
Chris |