• 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
dependent target "Copy files" build phase fails
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

dependent target "Copy files" build phase fails


  • Subject: dependent target "Copy files" build phase fails
  • From: Tommy Knowlton <email@hidden>
  • Date: Mon, 26 Apr 2004 15:12:58 -0600

Hello,

I'd like to make an XCode project that depends on a target of an external XCode project, such that the dependent target includes a "copy files" build phase that copies the product of the precedent target to the Executables folder of the dependent target's bundle.

If that isn't clear and concise enough, here's how to see what I'm trying to do:
1) Create a new XCode project that has, e.g., a target called "precedent". I don't think it matters what kind of target, but I'm using a shell tool.
2) Create some minimal C sources and get that target to build, e.g., a minimal "Hello, world."
3) Close the project and create a new project that produces an application bundle (.app) target.
4) Find the first "Hello, world" project in the Finder and drag its project file (.xcode) to the new project inside XCode: make the new project depend on the old project.
5) Add a "copy files" build phase to the new project's target.
6) Open the disclosure triangle on the precedent project in the Groups & Files of the dependent project. Now you should see the precedent project's target.
7) Drag this precedent's target down to the newly-added "copy files" build phase. Note that the build phase now apparently depends on the precedent target.
8) In the Info pane for the "copy files" build phase, change the "Destination" from an absolute path to "Executables" within the target bundle.


Command-B build and watch the "copy files" build phase fail.

Now, maybe I could make this succeed if my Preferences were to send build results to a separate location, but I don't think my whole dev team should have to do that for this to work. By allowing the precedent target to be dropped at the build phase, it ought to be implied that the build phase knows how to locate the build products of the precedent target.

Should I file an enhancement request? I'm obviously treading outside the bounds of what's been well-tested, but I think this use case should work. Else the UI should prevent me setting up the dependent target in this way.

Searching the xcode-users archive (http://search.lists.apple.com/xcode-users? q=dependent+target+"build+phase"+"copy+files") did not produce any relevant results. Am I the only person that thinks this should work?

Thanks,
--
Tommy
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Followup (Re: dependent target "Copy files" build phase fails)
      • From: Tommy Knowlton <email@hidden>
    • Re: dependent target "Copy files" build phase fails
      • From: Heath Raftery <email@hidden>
  • Prev by Date: Integrating gcc-based D compiler
  • Next by Date: # flag used with printf warning
  • Previous by thread: Re: Integrating gcc-based D compiler
  • Next by thread: Re: dependent target "Copy files" build phase fails
  • Index(es):
    • Date
    • Thread