Re: Endian-ness of "PkgInfo" file
Re: Endian-ness of "PkgInfo" file
- Subject: Re: Endian-ness of "PkgInfo" file
- From: Dirk Stegemann <email@hidden>
- Date: Sat, 14 Jan 2006 14:32:23 +0200
Hello,
Am 13.01.2006 um 23:25 schrieb Douglas Davidson:
The PkgInfo file is independent of processor architecture--for
example, a single bundle structure may be used for universal
binaries capable of running on either architecture.
Still, I encountered an endian-ness issue, although it seems to be
more an AppleEventManager problem than a PkgInfo file problem.
Anyway, the problem *can* be fixed with swapping the PkgInfo file's
Creator value, therefore I'll add my observations to this subject:
We have an Faceless Background Application with a registered Creator
(TJBR), so the PkgInfo file reads APPLTJBR.
Since a long time, we successfully communicate to this application by
sending AppleEvents which were created using the AECreateDesc() API,
something like this:
-----snip-----
#define kFBASignature "TJBR"
AEAddressDesc gFBAAddress;
OSErr myErr = AECreateDesc (
typeApplSignature,
(Ptr)&kFBASignature,
sizeof(long),
&gFBAAddress);
-----snip-----
On the Developer Transition System, the FBA doesn't recognise the
events until we either change its PkgInfo file to APPLRBJT, or change
the kFBASignature macro to "RBJT".
Is this expected behaviour, or should I file a bug report?
Regards,
Dirk Stegemann
_______________________________________________
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