Re: Placing a spotlight importer into a Applications bundle
Re: Placing a spotlight importer into a Applications bundle
- Subject: Re: Placing a spotlight importer into a Applications bundle
- From: Fritz Anderson <email@hidden>
- Date: Mon, 23 Jul 2007 14:36:40 -0500
On 23 Jul 2007, at 12:28 PM, Eric Gorr wrote:
I have an application Xcode project and a related spotlight importer
project.
What I want to do is to have the importer copied into the
Application's bundle ('Contents/Library/Spotlight') when the
application is built.
...
The problem I am having is that the Copy Files build phase is not
able to find the Spotlight importer at it's default build location,
which is just the ./build/${CONFIGURATION} directory inside of the
Spotlight importer project folder.
Instead, it is looking for the Spotlight importer product inside of
the build location for the application.
...
Now, I can change the build location of the Spotlight importer to
the build location of the application at which point the Copy Files
build phase will do the right thing, but this does not seem like the
right way to do things.
This is a well-known limitation of Xcode. When one project depends on
the product of another, the product must be found in the same build
folder.
The usual workaround is to have the two projects share a build folder.
The practical way to do this is to set a default build folder
("Building" in the preferences window) for all projects to share.
Elegant in the sense of providing a simple workaround; inelegant in
that a workaround is necessary.
Be sure that the project's build location (select project icon in its
Xcode window, double-click / get info, see the General tab) is set to
"Default build products location."
— F
_______________________________________________
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