Re: Adding auxiliary executables
Re: Adding auxiliary executables
- Subject: Re: Adding auxiliary executables
- From: "Alexander v. Below" <email@hidden>
- Date: Thu, 2 Nov 2006 10:43:19 +0100
There must be something else wrong with your project. Maybe you are
not building the executable as a dependency before you copy it?
Everything should work just like you described it:
- Use a copy phase to copy the auxiliary product to Executables (this
will put it into the "MacOS" folder)
- Use pathForAuxiliaryExecutable: to find it
Check your built product: Is the auxiliary executable in Contents/
MacOS ? Is it executable?
Alex
On 02.11.2006, at 09:21, Andrew Ebling wrote:
The Problem:
I can't seem to manage to create an auxiliary executable from an
existing target within a project. I've tried adding a "copy files"
build phase and adding the product executable to be added to the
"Executables" section, but when this line of code runs ("Evaluator"
is the name of the auxiliary executable):
NSBundle *currentExecDir = [NSBundle mainBundle];
path = [currentExecDir pathForAuxiliaryExecutable:@"Evaluator"];
currentExecDir points to the right place, but path is null - it
can't seem to find the auxiliary executable. Hence my project falls
in a big heap.
The Questions:
- where does NSBundle pathForAuxiliaryExecutable look inside
the .app folder? The documentation does not make this clear.
- how do I make XCode put the build product in the right place?
_______________________________________________
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