Re: Can Xcode 'Run' deployed/installed product instead of a symlink?
Re: Can Xcode 'Run' deployed/installed product instead of a symlink?
- Subject: Re: Can Xcode 'Run' deployed/installed product instead of a symlink?
- From: Chris Espinosa <email@hidden>
- Date: Thu, 19 Mar 2009 14:06:23 -0700
On Mar 19, 2009, at 7:45 AM, Jerry Krinock wrote:
I'm building a helper tool for my application. To get desired
behavior from certain API when I click "Build and Run", it must be
running from within my app's package and not my default Build
directory. By setting DEPLOYMENT_LOCATION, INSTALL_PATH, and
INSTALL_PATH, I am able to get the actual product installed into the
app package.
However, these settings cause Xcode to put a symbolic link to the
actual product in my default Build directory, and when I click "Run"
it runs the symlink instead of the actual product. Since the
relevant API calls in my tool, for example
[NSBundle mainBundle]
[[[NSProcessInfo processInfo] arguments] objectAtIndex:0]
do not follow symlinks, I'm still "back at square one".
I understand that I could write a little script which would run the
actual product and supply the needed command-line arguments, and use
this instead Xcode's "Build and Run". But since these neat features
are available in Xcode, I'm surprised that they don't work when I
put them all together. Am I missing something?
You could (and should) create a Custom Executable to point at the
installed product.
Chris
_______________________________________________
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