开发者

Should I duplicate an xcode project or #define sections?

I have an iPad app that can come in several different releasable flavors, and I'm trying to decide how to best make these alternate releases. They have only a few differences source-code wise, and primarily differ in 开发者_C百科resource data files (xml and a very large amount of binary files).

1) Should I duplicate the project and branch the handful of source files and include the appropriate resources separately for each? This seems more of a maintenance hassle as I add files to the project and do other basic things other than edit shared files.

2) Or should I use #defines to build the appropriate flavor I want at any time, then ifdef out entire files accordingly? This seems simpler but my suspicion is that I won't be able to find an easy way to exclude/include resource files, and that would be a deal breaker.

Any suggestions on how to deal with the resource issue in option 2, or if there is an alternate approach altogether that is better?


What about creating separate targets within a single XCode project?

Make each target include the files that are appropriate for that app; no need for ifdefs that way.

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜