Probably something you forgot to include in the new target, or a wrong
setting. Why do you create a new target at all, why not simply 'check
the checkbox'?
patrick
Turns out the app was dying because of a failed call to Gestalt. Why
did it fail? Because it was trying to get the Gestalt of selector
'vsys'. Doesn't exist. Actually it's 'sysv'. So I've run aground on
the first of what's likely to be hundreds if not thousands of endian
problems.
Gah! Apple handled Rosetta so nicely, why couldn't they make endian
issues transparent too?
Because this would require either continuing on with a big-endian
processor or requiring everyone to use a high-level language which doesn't
expose the endianness of the CPU to the end user. Merits of the CPU switch
are debatable, but requiring you to switch to a completely different
language should obviously be even worse than making you clean up your
code. Endian-unclean isn't something you can just fix in any C-derived
language.
--
Michael Ash
Rogue Amoeba Software
I'm not sure why you're having that problem. I've got code that calls
Gestalt() on both PPC and Intel and I haven't run into this. I haven't
tried 'sysv', but 'mclk' and 'ramm' seem to work without any trouble.
--
Tom "Tom" Harrington
Macaroni, Automated System Maintenance for Mac OS X.
Version 2.0: Delocalize, Repair Permissions, lots more.
See http://www.atomicbird.com/
> *sigh* and so the nightmare of updating old code begins.
>
> Turns out the app was dying because of a failed call to Gestalt. Why
> did it fail? Because it was trying to get the Gestalt of selector
> 'vsys'. Doesn't exist. Actually it's 'sysv'. So I've run aground on
> the first of what's likely to be hundreds if not thousands of endian
> problems.
So you're not checking the Gestalt() return value, and using invalid
data. Your bad, don't blame Apple. Code defensively...
patrick