• 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: Command-K not compiling
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Command-K not compiling


  • Subject: Re: Command-K not compiling
  • From: Stefan van den Oord <email@hidden>
  • Date: Sun, 12 Jun 2005 15:29:44 +0200

Indeed, changing the reference type does make it work again. I believe
that this is a bug in Xcode and I will file it as such.

In fact, I think in my case the problem arises because my Xcode
project file is not in the root of the project as it is on disk. We
have a multi-platform app, and the project tree on disk is:

./
./project/win32
./project/Darwin
./src
(etc.)

The Xcode project file is in the project/Darwin subdir. I ran into a
few difficulties because of that, but was able to work around them. I
guess Xcode wasn't designed with this in mind.

On 6/10/05, Paul Sinclair <email@hidden> wrote:
> I think I figured it out.  While I was going to find
> the build transcript that you mentioned, I opened a
> particular file from the project to test with and the
> command-K problem did not happen.  I did a Get Info on
> this file and a file I knew wasn't working and noticed
> that their Path Type was "Relative to Enclosing
> Group".  Relative to Enclosing Group is the default
> "Reference Type" when you are adding files to your
> project from the finder.  Well, I had added a group of
> files from a folder that was at another location on my
> drive and I just used the default reference type when
> including them.
>
> So I guess when you are adding files to your project
> from a separate location (and you don't check "Copy
> items into destination group's folder (if needed)" <--
> I didn't try that, but I figure it would solve the
> problem as well.), you can't use the default reference
> type.  Here's what I found:
>
> Default/Relative to Enclosing Group - failed
> Relative to Project - success
> Absolute Path - success
> Relative to Build Product - failed
>
> I chose Absolute Path and can happily use command-K
> again!  Thanks for the help Markus.  Hope this solves
> it for you too Stefan.
>
>
>
>
>
> __________________________________
> Discover Yahoo!
> Have fun online with music videos, cool games, IM and more. Check it out!
> http://discover.yahoo.com/online.html
>  _______________________________________________
> 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
>
 _______________________________________________
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

  • Follow-Ups:
    • Re: Command-K not compiling
      • From: Chris Espinosa <email@hidden>
References: 
 >Re: Command-K not compiling (From: Markus Hitter <email@hidden>)
 >Re: Command-K not compiling (From: Paul Sinclair <email@hidden>)

  • Prev by Date: Re: Debugging Unit Tests
  • Next by Date: Re: Crash in pthread_mutex_lock
  • Previous by thread: Re: Command-K not compiling
  • Next by thread: Re: Command-K not compiling
  • Index(es):
    • Date
    • Thread