On Apr 24, 2004, at 12:44 AM, Nicolas Zinovieff wrote:
As far as I know, ProjectBuilder or Xcode can only create bundled
applications that get rid of the need of resource fork. rsrc files
have their data in the data fork (however, the resource manager can
manage the two types of resource files, old version with data in
resource fork and the new one with data in data fork).
Just take a look at "legacy" target in Xcode, or the target settings
in PB. You can set the resource fork to be separated (in a .rsrc file)
or in the executable.
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.
If I quite understand you, you want to add a resource fork to the
executable (hence the file in the MacOS folder of the application
bundle) but what's your goal ?
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.
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