• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Adding auxiliary executables [solved]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Adding auxiliary executables [solved]


  • Subject: Re: Adding auxiliary executables [solved]
  • From: Andrew Ebling <email@hidden>
  • Date: Thu, 2 Nov 2006 14:07:35 +0000

Hi Alex,

Many thanks for your help, which has enabled me to solve the problem :-).

For those who are interested and for the benefit of the archives:

In the info pane for the Copy Files Phase, the destination drop down box is used in combination with the path field to set the _destination_ of the copy command. Files to be copied by the build step need to be dragged onto the build step.

I thought that the path field was for specifying the _source_ of the copy command (as was the case with Project Builder I believe), but this is not the case in XCode.

Thanks again for your help - my project is now working as expected.

best regards,

Andrew

On 2 Nov 2006, at 09:43, Alexander v. Below wrote:

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
References: 
 >Adding auxiliary executables (From: Andrew Ebling <email@hidden>)
 >Re: Adding auxiliary executables (From: "Alexander v. Below" <email@hidden>)

  • Prev by Date: Re: Error -1409
  • Next by Date: Re: How to "Jump Back"?
  • Previous by thread: Re: Adding auxiliary executables
  • Next by thread: Re: Error -1409
  • Index(es):
    • Date
    • Thread