Re: Universal Cocoa plug-in
Re: Universal Cocoa plug-in
- Subject: Re: Universal Cocoa plug-in
- From: Chuck Soper <email@hidden>
- Date: Fri, 17 Feb 2006 22:42:58 -0800
Title: Re: Universal Cocoa plug-in
At 9:45 PM -0800 2/17/06, Chris Espinosa wrote:
On Feb 17, 2006, at 9:28 PM, Chuck Soper
wrote:
I have a Cocoa
plug-in for a Dashboard widget. Recently, I rebuilt it as a Universal
Binary. Or, I thought I did. I changed the settings for the Deployment
configuration for the project as follows:
Architectures: ppc
i386
SDK Path:
/Developer/SDKs/MacOSX10.4u.sdk
I re-built the
plug-in, tested it on Intel and it ran fine. I thought that was it. At
WWDC, I remember hearing that that ppc widget plug-ins didn't have
access to Rosetta and wouldn't run on Intel-based Macs. Today, I did a
'Get Info' on the Unix Executable File within the widget plug-in
bundle and discovered that it shows PowerPC not
Universal.
I assumed that
since I built my target using the Deployment configuration that it
would reflect the 'Architectures' setting I had just made, but that
wasn't the case. I had to change the 'Architectures' setting in the
target as well. I thought the point of having a build configuration
was to be able to change build settings in one place instead of having
to change settings for every target. Is that
correct?
I believe that I
have it building correctly yet, now I'm not sure if my widget runs
natively on Intel or not. more testing...
If you'd already had Architectures set in
the Deployment configuration of the target, that setting overrides
whatever you did at the project level.
To avoid this, find Project >
Edit Active Target > Build tab, select Architectures, and
either
a) delete it, allowing the project
setting to "shine through" or
b) set it to "ppc i386"
explicitly.
Chris
This seems logical. Thanks for the explanation. It looks like I
had been modifying my target settings instead of my configuration
settings. Now, I think I should carefully migrate the target settings
to the appropriate configuration then delete the corresponding target
settings.
I'm not sure if there's a way to avoid this kind of confusion.
Would the following enhancements make sense?
1. In the Target Info dialog, indicate which settings override a
configuration.
2. When changing a setting in the Project Info dialog, show an
alert sheet that informs the user which targets already have values
for that setting (so the user knows that the setting won't be applied
to those targets). Ideally, they could replace the project setting in
the target(s) if desired.
I know that lists are not the place to make suggestions. If these
suggestions seem workable then I can file them.
Chuck
_______________________________________________
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