Re: Dissociation between PRODUCT_NAME and EXECUTABLE_NAME causes debugger problems
Re: Dissociation between PRODUCT_NAME and EXECUTABLE_NAME causes debugger problems
- Subject: Re: Dissociation between PRODUCT_NAME and EXECUTABLE_NAME causes debugger problems
- From: Alexander von Below <email@hidden>
- Date: Sat, 5 Aug 2006 18:08:56 +0200
Thanks for your reply.
I know the option to create a custom executable, but this sound like
a kludge to me. Xcode is well aware what the executable in the bundle
is, and it does not seem logical to me that the debugger does not.
But I probably will go ahead and file a bug report on it, unless I
simply omitted a step
Alex
On 05.08.2006, at 17:35, James Bucanek wrote:
Alexander von Below wrote on Saturday, August 5, 2006:
Say, the product is to be named "foo" and the bundle executable is to
be named "bar" By setting the EXECUTABLE_NAME in the foo Target build
settings to "bar", I can achieve this result. If I click foo.app in
the finder now, it is launched using the bar Bundle executable.
However, if I try to use "run" or "debug" from within Xcode, I am
told that there is "no lauchable executable present at path "/Users/
below/dev/Example/build/Debug/foo.app/Contents/MacOS/foo".
Create a custom executable. You can get set your build settings to
build any target, then set the executable to launch your renamed
binary for testing and debugging. The executable can be anything
and doesn't even have to be a product of your project. The
canonical example is a project that produces a plug-in, but to
debug it one must launch the host application that loads the plug-in.
_______________________________________________
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