title: Resource files not updating with Xcode 5
body: <p>I have some binary files with a proprietary extension that don't get updated in a build when I compile.  In previous versions of Xcode with this same project, it would detect the file was changed, and rarely would I have to perform a 'Clean' as I have to do with this version.  Of course this is consuming a lot more time -- I would appreciate it if someone could let me know what's changed with Xcode 5 and/or what I could do about this.</p>
  
  <p>I didn't include any project specifics because it's really just a proprietary binary file with a custom extension in a resource folder, which, used to update automatically upon it being changed since last compile. If you need any specific project settings I would be glad to offer it.</p>
  
  <p>It's using the sort of 'blue' resource folder that is a reference to the folder it's in, and isn't just copied into the project directory.  I apologize since I forget what this particular resource folder type is called (I'm guessing Reference).</p>
  
  <p>Version: Xcode 5 (5A1413)</p>
  
  <p>UPDATE:</p>
  
  <p>This only happens when I'm referencing a file that I modify programmatically with fopen,fwrite,etc, and upon using a file editor in OSX to resave the file (without really changing it) Xcode will then see it as changed.</p>
  
  <p>I'm now looking into FSEvents to see if this underlying API is something I need to use, although I'm not exactly sure how to set flags with this just yet.</p>
  
  <p>UPDATE:</p>
  
  <p>Well, just as a simple test, I take the same file and resave it via:
  <code></p>
  
  <pre><code>NSData* data = [[NSData alloc] initWithContentsOfFile: @"/location/file.dat"];
  [data writeToFile:@"/location/file.dat" atomically:YES];
  </code></pre>
  
  <p></code></p>
  
  <p>Sure enough, after I call that and then run the app that uses the resource, it is updated via Xcode during the build.  So it would seem that Xcode 5 relies on some special flags not set by the standard io functions.  At this point I can either patch what I've got with that 2 line thing or figure out what the flagging mechanism is, and how to write to it.  (FSEvents?  I don't see a writing mechanism there..)</p>