Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subproject Dependencies


On May 20, 2005, at 10:42 AM, Chris Espinosa wrote:

On May 20, 2005, at 8:21 AM, Scott Thompson wrote:

For our application, we've added a project to create a Spotlight importer.  We dragged the importer's project onto the main application project and set up dependencies so that the Spotlight importer is built properly when it is out-of-date.

Now we're trying to set up the project to automatically copy the Spotlight importer into our application bundle.   I've created a "Copy Files" build step and dragged the icon that represents the output of the Spotlight importer project into that copy files step.

The problem is that the application doesn't seem to be able to find the Spotlight importer after it is built.  As far as I can tell, it is trying to find the built importer in the output directory for the application build, and not in the output directory of the Spotlight Importer Project.


In Xcode Preferences, Building tab, click "Customized Location" for "Place Build Products In" and choose a common location for the build projects.  That's the  easiest way.  

Thanks.  It's a good suggestion but doesn't really fit the way we have things set up.

Because of the way that XCode handles other dependencies (like framework search paths) we've run into problems relying on a user-centered setting like the "Build Products" and "Intermediate Files" settings of the preferences dialog.  We complicate matters ourselves by also trying to build the application into separate directories for the Development and Deployment build styles.  As a result, we've found the need to "hard-coded" the project-relative paths for the build products and intermediate files into the build style settings for the application.

I'll change the Spotlight Importer project to hard code a project-relative path that puts its output in the application's output folder. This seems like a really odd limitation to have to work around.  From my (admittedly uninformed) perspective it would seem that XCode has all the information it needs to locate the build products of the sub-project and I find it really odd that it can't do so.  I'll also file a bug :-)

rdar://4125785

Scott

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden
References: 
 >Subproject Dependencies (From: Scott Thompson <email@hidden>)
 >Re: Subproject Dependencies (From: Chris Espinosa <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.