Comments on: Xcode, Folders and the File System – Part 2 http://iPhoneDeveloperTips.com/xcode/xcode-folders-and-the-file-system-part-2.html Tips and Tricks for iPhone developers Fri, 12 Mar 2010 20:00:00 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: moole http://iPhoneDeveloperTips.com/xcode/xcode-folders-and-the-file-system-part-2.html/comment-page-1#comment-5188 moole Thu, 24 Sep 2009 01:23:15 +0000 http://iPhoneDeveloperTips.com/?p=2393#comment-5188 There is a way to overcame it - add a run shell script as the first build phase which touches all of your resource folders, which then xcode founds out as updated and copies them to the application package bundle again within every build: http://majicjungle.com/blog/?p=123 There is a way to overcame it – add a run shell script as the first build phase which touches all of your resource folders, which then xcode founds out as updated and copies them to the application package bundle again within every build:
http://majicjungle.com/blog/?p=123

]]> By: Brad http://iPhoneDeveloperTips.com/xcode/xcode-folders-and-the-file-system-part-2.html/comment-page-1#comment-2900 Brad Thu, 11 Jun 2009 19:25:21 +0000 http://iPhoneDeveloperTips.com/?p=2393#comment-2900 Yes, thanks for clarifying what I meant... When I change a resource (eg a text file) on the file system, and do a build, it doesn't show up in my app unless I do a "Build | Clean Target", then a standard build. To work around it for the time being, I've been using some conditional code to look for the files on the local file system if I'm building for the iPhone simulator, and look for them in the resources if I'm not, since alot of the time I'm working using the simulator, this works pretty good....But having it work as it should for both device and simulator builds would be great... Yes, thanks for clarifying what I meant… When I change a resource (eg a text file) on the file system, and do a build, it doesn’t show up in my app unless I do a “Build | Clean Target”, then a standard build. To work around it for the time being, I’ve been using some conditional code to look for the files on the local file system if I’m building for the iPhone simulator, and look for them in the resources if I’m not, since alot of the time I’m working using the simulator, this works pretty good….But having it work as it should for both device and simulator builds would be great…

]]> By: John Muchow http://iPhoneDeveloperTips.com/xcode/xcode-folders-and-the-file-system-part-2.html/comment-page-1#comment-2898 John Muchow Thu, 11 Jun 2009 18:28:50 +0000 http://iPhoneDeveloperTips.com/?p=2393#comment-2898 If you are referring to updating content within a folder (on the file system) and then having to do a "clean" for the changes to be recognized, yes, I've experienced the same. Seems the build system should be able to detect such changes... Any suggestions out there? If you are referring to updating content within a folder (on the file system) and then having to do a “clean” for the changes to be recognized, yes, I’ve experienced the same. Seems the build system should be able to detect such changes…

Any suggestions out there?

]]> By: Brad http://iPhoneDeveloperTips.com/xcode/xcode-folders-and-the-file-system-part-2.html/comment-page-1#comment-2890 Brad Thu, 11 Jun 2009 12:40:51 +0000 http://iPhoneDeveloperTips.com/?p=2393#comment-2890 I've been using this same approach for some time, but have been finding that as of late, I have to clean my builds before I can see the changes in resources managed like this. Have you come across this problem? If so, did you find a solution? I googled it and saw that it was an issue for older versions of XCode, but none of the solutions I saw for it worked for me.... I’ve been using this same approach for some time, but have been finding that as of late, I have to clean my builds before I can see the changes in resources managed like this. Have you come across this problem? If so, did you find a solution? I googled it and saw that it was an issue for older versions of XCode, but none of the solutions I saw for it worked for me….

]]>