I am almost embarrased to say, but the problem was not in fact with
NSBundle, but the method in which I was copying my compiled
application from my 10.4 machine to my 10.3 machine. I was using
SMB which was corrupting or at least not copying the symbolic link
of the framework resource files properly. On the face of it, and
via finder, the files appeared to look identical. But a look at
things via the terminal proved otherwise. I am now using AppleTalk
on my local network instead of smb (even though I have a pc in the
mix). This appears to have solved the problem.
Not always obvious, it is.
Wouldn't this actually point out a more subtle problem? Namely that
if your _users_ copy your application on an SMB server, it will stop
working for them? And what about, say, transferring it via a USB
thumbdrive? I know I've seen problems where, because the drive is
actually a DOS formatted disk, that files with "*" in them won't copy
(at least the Finder warned me about it, though - you'd hope it would
do something similar for symbolic links). Perhaps you use an alias
instead of a symbolic link? That should work from the framework
point of view, and hopefully won't get corrupted...
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden