Re: architecture dependant problems with ResMerger
Re: architecture dependant problems with ResMerger
- Subject: Re: architecture dependant problems with ResMerger
- From: Chris Espinosa <email@hidden>
- Date: Thu, 12 Apr 2007 21:34:44 -1000
On Apr 12, 2007, at 2:49 PM, Stefan Werner wrote: I just spend a few hours finding out that ResMerger behaves differently on PPC than on i386, more specifically it does give errors on Intel that it does not on PowerPC:
One of our resources fails when building on Intel with this error:
### /Developer/Tools/ResMerger ERROR: errCoreEndianDataTooShortForFormat (resType 'WIND' ID 5)
Building the same project on PPC does not throw any errors whatsoever. The resulting app will run fine on PPC Macs, but fail the same error message on Intel.
I could find a post in the mailing list archives where this is being explained with the byte swapping mechanism: http://lists.apple.com/archives/xcode-users/2006/Sep/msg00344.html
Is there any way to make the PPC ResMerger complain about that error too? Our main build machine is a PowerMac G5, and it would be very beneficial if it could detect such errors.
Resources are stored in canonical (big-endian) format on disk. So the PPC RezMerger will never flip resources when reading from or writing to disk, and the Intel RezMerger will always flip resources.
So there's no way to prevent the flippers from firing in the Intel side (other that to, say, run RezMerger in Rosetta) and no way to get the flippers to fire on the PPC side. They physically don't exist in the binary code for PPC.
Have you considered fixing your WIND 5 resource?
Chris |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden