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: James Bucanek <email@hidden>
- Date: Sat, 5 Aug 2006 08:35:58 -0700
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.
James Bucanek
____________________________________________________________________
Author of Beginning Xcode ISBN: 047175479X
<http://www.beginningxcode.com/>
_______________________________________________
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