On Mar 29, 2006, at 4:19 PM, James W. Walker wrote:
The Build ResourceManager Resources build phase is giving me
fnfErr errors on files that Xcode as a whole clearly knows the
correct location for. I think the problem is that this build phase
cannot cope with references relative to a source tree. A Copy
Files build phase also seems unable to handle source trees. Is
there any workaround other than not using source trees for anything
but source code?
Please post the Rez and ResMerger invocation lines from your source code, and see whether the paths provided to those tools match the locations of your resource files.
If you're getting "File not found" in Xcode (which doesn't use the Carbon file manager, so never should see 'fnfErr' :-) ) it's possible that it's looking in the wrong fork for resource information.
Source Trees are just build settings. Everything can and should handle them if they're used explicitly (they're not like search paths; you have to enter the source tree into the appropriate build settings).
I figured out what the problem was. Apparently, a source tree cannot contain any spaces in its path, even if the spaces are escaped. Once I nuked the spaces, things started working.
