• 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: Framework in external project; Copy Files not working
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework in external project; Copy Files not working


  • Subject: Re: Framework in external project; Copy Files not working
  • From: Derrick Bass <email@hidden>
  • Date: Tue, 10 Oct 2006 08:40:03 +0000

On Oct 10, 2006, at 5:52 AM, j o a r wrote:

Typically you want Xcode to copy from a particular build configuration directory ("Debug" in this case) in order to avoid mixing up the output from different build configurations. So I would say that Xcode is already looking in the right place.

I don't think it's a build configuration issue. I think maybe I wasn't quite clear about my directory structure. See below.

I think the question is, why is there nothing to copy in the directory where Xcode is looking?
Are you using a shared build location for both projects (recommended when working with project references)?


No, I'm not.

The DataBaseProject is a separate project the happens to to have a useful target (DatabaseBrowser.framework) for the Extractor application, so I just copied the entire directory into the Extractor project directory. So my directory structure looks like this:
Extractor/
-- various files and subdirectories for the Extractor application
build/
Extractor.xcodeproj/
DataBaseProject/
-- various files and subdirectories for the DataBase.framework
build/
DataBaseProject.xcodeproj/


So the DataBaseProject builds into the build/ subdirectory of DataBaseProject, while the Extractor application builds into the build/ subdirectory of Extractor/.

I put a reference to DataBaseProject.xcodeproj in the Extractor project and made the application depend on the framework target and link to the framework. Both those seem to work: building the application (Debug target, let's say) causes the framework to be built in Extractor/DataBaseProject/build/Debug and the application is linked to Extractor/DataBaseProject/build/Debug/ DatabaseBrowser.framework, which is correct. But the Copy Files build phase is not finding it. It's looking in Extractor/build/Debug instead of Extractor/DataBaseProject/build/Debug.

Since DataBaseProject is a separate and independently useful project, I'd like to avoid modifying it in a such a way that it would no longer work well as a stand-alone project directory.

Derrick

_______________________________________________
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: 
 >Framework in external project; Copy Files not working (From: Derrick Bass <email@hidden>)
 >Re: Framework in external project; Copy Files not working (From: j o a r <email@hidden>)

  • Prev by Date: changing extension from .app to .pkg
  • Next by Date: Re: changing extension from .app to .pkg
  • Previous by thread: Re: Framework in external project; Copy Files not working
  • Next by thread: Re: Framework in external project; Copy Files not working
  • Index(es):
    • Date
    • Thread