Re: Command-K not compiling
Re: Command-K not compiling
- Subject: Re: Command-K not compiling
- From: Stefan van den Oord <email@hidden>
- Date: Sun, 12 Jun 2005 21:33:10 +0200
Actually, I'm pretty sure that in my specific case it didn't work in
2.0 either. I'll verify this ASAP.
Stefan
On 6/12/05, Chris Espinosa <email@hidden> wrote:
>
>
> On Jun 12, 2005, at 6:29 AM, Stefan van den Oord wrote:
>
>
> 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.
>
> Preprocessing and individually compiling files with "up and over" references
> was broken in 1.5 and earlier. We fixed it in 2.0 but apparently broke it
> again in 2.1, we'll take a look at it. There's a method we use for
> comparing paths, and we're apparently not expanding them to their full
> canonical representation in some places.
>
> Chris
> _______________________________________________
> 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