how a universal package/bundle/binary looks on disk
how a universal package/bundle/binary looks on disk
- Subject: how a universal package/bundle/binary looks on disk
- From: Mark Sanvitale <email@hidden>
- Date: Tue, 28 Mar 2006 18:38:04 -0800
| In doing some experiments with building a project for multiple architectures (i.e. universal binary), I had this feeling that something had changed. Using Xcode 2.2 and the "10.4u" SDK, I built a simple app (using Carbon) for both ppc and i386 architectures. The resulting application package contained a single executable file ("Unix Executable File (Universal)") inside the "MacOS" directory.
For some reason, I expected the app package to contain two directories for the two different architectures with each directory containing one, arch-specific executable. Did things ever used to be this way (and, thus, explain my feelings of change)?
It is very possible that my brain done broke and I am mixing things up (i.e. the separation by architecture that happens within the build results directory (e.g. i386 and ppc) has seeped into my thoughts of app packaging which has separation-by-platform (e.g. MacOS, MacOSClassic)).
extra credit: if my brain has done broke, what can be done?
Mark Sanvitale Electrical Geodesics, Inc.
|
_______________________________________________
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