• 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: Setting up target dependency
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Setting up target dependency


  • Subject: Re: Setting up target dependency
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Wed, 7 May 2008 02:45:14 +0200


Le 7 mai 08 à 00:23, Jerry Krinock a écrit :


On 2008 May, 06, at 7:57, Jean-Daniel Dupas wrote:

You have to use the items that are in the "Products" folder in the Xcode tree. Drag and drop them into your Copy build step.
Like this, Xcode will copies debug tools when your configuration is debug and release tools when your configuration is release :-)

Jean-Daniel, does this also work for dragging in private frameworks from a different project?


I've never been able to get Debug►Debug and Release►Release private frameworks using a Copy Files Build Phase.

What do you mean by "Xcode tree"? Does not seem to fit with "source tree" and if you mean the "Products" at the bottom of "Groups and Files", that's what I've always used and not been able to get private frameworks from a different project properly copied. Actually, Copy Files won't accept a drag of a product from another project directly, so I have to do it in two steps, (1) drag product from other project into Groups & Files and then (2) drag from Groups & Files into Copy Files. But then during building it copies Release►Debug and Release►Release :-(

In fact, Copy Files accepts a drag and drop of a product from another project, but the copy operation will failed saying that to file xxx is not found. AFAK, it can work but only if your framework and your product are built in the same directory (Xcode searchs your private framework next to the application you are building, generaly in build/ Debug or build/Release and not in the dependent target build dir). If you plan to use this framework in only one project, you can edit the build settings of the framework project and set the build dir to the same directory for both projects, but if you plan to use this framework in many project, I'm not aware of any simple way to workaround this limitation.
Maybe I'm missing something, but actually, I'm using a script build step that create a symlink of my private framework into the target build dir.



_______________________________________________ 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: 
 >Setting up target dependency (From: Hugh Sontag <email@hidden>)
 >Re: Setting up target dependency (From: Jean-Daniel Dupas <email@hidden>)
 >Re: Setting up target dependency (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: Clean all targets
  • Next by Date: Re: Help: multiple warnings objc[x]:.....class XY is implemented in both....
  • Previous by thread: Re: Setting up target dependency
  • Next by thread: Inspecting Obj-C method parameters from gdb
  • Index(es):
    • Date
    • Thread