Build mysteriously excludes G3s
Build mysteriously excludes G3s
- Subject: Build mysteriously excludes G3s
- From: James Bucanek <email@hidden>
- Date: Thu, 18 Mar 2010 16:35:19 -0700
I got a call the other day (does anyone still use the
telephone?) from a customer who can't run my application. It
turns out they have a G3 running Tiger. I investigated and found
that the latest release of my application's not-so-universal fat
binary only contained code for i386 and ppc7500 (i.e. G4/G5).
Here's my situation:
I have a project, currently being built using Xcode 3.2.1 and
3.2.2 (although this problem is older than that). The project
has 11 targets and produces 2 Cocoa applications, 3 Foundation
tools, 1 C tool, 1 Contextual menu plug-in, and 1 Spotlight importer.
It's configured to produce 32-bit (only) universal binaries. The
problem is that one Cocoa application (the main client
application) produces a i386+ppc7400 binary (according to 'lipo
-info'). _All_ of the other targets produce i386+ppc binaries.
There's nothing at the target level of the build (that I could
find) that would cause that one Cocoa app to compile differently
than the others. In fact, I tend to migrate many of the default
target settings to project level just to make sure everything
builds the same. They all have the same compiler, optimization,
target SDK, and deployment settings.
Looking at the build transcript, all of the compile and link
commands are passed "-arch ppc".
Does anyone know what would possibly cause one, and only one,
application to generate ppc7400 code while every other target in
the project produces ppc code?
_______________________________________________
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