Xcode development, and brief thoughts on targets.

So I've been migrating all my stuff onto my Mac as much as possible, and that means starting to develop code on this thang to*. And that in turn means I should probably learn Xcode, especially since I plan on some iPhone development (everyone wants it these days!). So that means learning a whole new IDE, whole new way of thinking.

Which brings me, tangentially to targets.

See, on other platforms we got stuff like makefiles, that tells the compiler how to make your program. But the thing is, all the various settings for how to build your code can't really be contained in the makefile and the like. So shit started getting mad spread out, to the point where you need a degree in Comp Sci just to BUILD some codebases out there.

Targets are Apple's attempt to simplify it all. You 'target' certian hardward/os/libraries. And it's more powerful than just that! You can make targets that take you iPhone app and make it into a demo version. Really powerful stuff.

Which brings in new problems. See, because they're powerful, it feels like you should be able to export targets, especially since they don't seem (at first!) tied to a paticular project. The idea of useing one makefile for several different projects. But using the same target across multiple projects? Makes a kinda sense, at first. And even now.

The more you give, the more they want.

*Shoutouts to macports! GODLIKE dev tool.

No comments:

Post a Comment