Re: Resource forks
Re: Resource forks
- Subject: Re: Resource forks
- From: Nicolas Zinovieff <email@hidden>
- Date: Sun, 25 Apr 2004 11:34:09 +0200
On 25 Apr, 2004, at 07:25, Chris Espinosa wrote:
Yes, "legacy" targets default to resource fork, and you have to add
the -useDF flag to use the data fork. Native targets default to
-useDF and there is no override to return it to the resource fork.
Just for the sake of descending AND ascending compatibility.
I don't quite understand what you want to be compatible with. Mach-O
binaries shouldn't have resource forks, and Xcode can't create CFM
binaries, so I don't understand the need for Xcode to create binaries
with resource-fork data.
I don't know about the "shouldn't". I have this project that comes from
a long way and uses resource forks in the executable. I maintain it and
the fact that xcodes changes such a simple behavior without any way of
getting back on my feet is just a pain in the neck.
Nothing I can't handle, but still...
If you want to move resource data to the resource fork of a file, you
can always add a shell script build phase that copies the data fork
resource file into the resource fork of any file by using the named
fork notation, e.g. cp foo.rsrc bar.rsrc/..namedfork/rsrc
Or using resmerger...
OK, but I honestly don't see the reason behind this crippling...
--
Nicolas
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.