Re: Launching 32- vs 64- bit custom executables
Re: Launching 32- vs 64- bit custom executables
- Subject: Re: Launching 32- vs 64- bit custom executables
- From: Chris Hanson <email@hidden>
- Date: Mon, 20 Oct 2008 21:13:17 -0700
On Oct 20, 2008, at 8:25 AM, Jonathan del Strother wrote:
When I have a fat custom executable (eg /Developer/Tools/otest), what
determines whether it launches in 32 or 64 bit? In my case, ⌘⌥R
launches it in 64 bit mode, so testing debug builds of my framework
fails because they're only 32bit. Oddly, debugging the executable
(⌘⌥Y) launches it in 32 bit.
Since you mentioned 64-bit, I assume you're using Xcode 3.0 or later.
Run and Debug[1] currently behave differently when determining how to
launch a custom executable.
- Run will run your executable in a way similar to the Finder or the
shell, which means that the most specific architecture for your
hardware will be preferred.
- Debug will run the executable using the Active Architecture that you
specify in the Project menu, the Active Architecture pop-up in your
toolbar, or the Active Architecture section of the Overview pop-up in
your toolbar.
This is a known bug.
Note also that you generally won't use "Run" to run unit tests. If
you set up a unit test bundle using the template included with Xcode,
just building your unit test bundle will run its tests.
-- Chris
[1] It's better to refer to these by their name, rather than by their
keyboard equivalent in the default keyboard layout, because not
everybody uses the same keyboard layout.
_______________________________________________
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