• 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: Single file compile oddity
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

re: Single file compile oddity


  • Subject: re: Single file compile oddity
  • From: Paul Miller <email@hidden>
  • Date: Thu, 30 Sep 2004 17:39:45 +0100

What would prevent XCode from being able to compile a single file in a
native target?

It worked.. I made a bunch of changes... it no longer works. When I hit
command-K, it opens the build window and immediately says "Build
succeeded".


Is your file inside the directory containing the project or outside it?
I get this behaviour in Xcode 1.5 if I try to compile a file which is located outside of the project directory and is referenced by a relative path (i.e. the path to the file has '../' in it). If you move the file inside the project directory, or change the reference style to absolute then command-K should work as normal again.


Paul.


_______________________________________________ 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
  • Prev by Date: Re: Files still dirty after build
  • Next by Date: Re: Emacs save buffer habit causing pain in Xcode
  • Previous by thread: Single file compile oddity
  • Next by thread: Apple distcc protocol extensions
  • Index(es):
    • Date
    • Thread