Re: Again, Why Doesn't XCode Compile a Framework Header Included in theProject?
Re: Again, Why Doesn't XCode Compile a Framework Header Included in theProject?
- Subject: Re: Again, Why Doesn't XCode Compile a Framework Header Included in theProject?
- From: "Kirt Cathey" <email@hidden>
- Date: Wed, 07 Sep 2005 05:27:19 +0000
Chris, Chris, Chris...
Never cease to amaze me. I would send a listing but I have already resigned
to doing a full install and am downloading XCode 2.1 as we speak. The
system is already re-installed.
HOWEVER! The only difference among a variety of hardware spec issues is
that the PowerMac is a 2.7Ghz dual processor. So, what does that have to do
with this run around?
Thank you kindly.
-------------------------
Kirt S. Cathey
http://www.bizolutions.com
-------------------------
From: Chris Espinosa <email@hidden>
To: Kirt Cathey <email@hidden>
CC: email@hidden
Subject: Re: Again,Why Doesn't XCode Compile a Framework Header Included
in theProject?
Date: Tue, 6 Sep 2005 22:21:09 -0700
On Sep 6, 2005, at 9:57 PM, Kirt Cathey wrote:
I am running OS X 10.4.2
XCode 2.1
Don't know what you mean by per-user source trees, but shouldn't
make a difference in this case.
I am trying to compile the SimpleStickie sample code downloaded off
of the Apple developer web site.
The search path is absolute and indicated in my previous posting
/System/Library/Frameworks
And yes I have confirmed paths all the way to the headers.
As for unanswered postings...
http://lists.apple.com/archives/xcode-users/2005/Mar/msg00046.html
That has to do with finding the header by command-double-clicking,
which is a function of indexing, not compiling. It really has
nothing to do with the problem you describe.
So, fine it's not a linking issue.....
So far as you've described it, when you compile you get an error
message saying it cannot find the header file. That means it's not
indexing or project navigation, because it occurs while compiling.
And because compiling fails, it's not a linking issue, because
linking doesn't happen until you have successful compilation.
So it's a problem either with
- the way the paths to the framework are being specified to the
compiler
(which is why I asked for the build log transcript)
- whether the header is actually in the place it is supposed to be
(which you above claim it is, but I'd like to see the ls listing
of the SyncServices.framework/Versions/Current/Headers directory)
- whether the header itself can be read
(can you open SyncServices.h and read its contents?)
It could be something as straightforward as a file not copied on
installation, or directory corruption on the hard disk. It could be
that you are mis-specifying the path, but on the successful machine
there's some fallback path that is working, but not on the broken
one.
Is the machine that fails to open SyncServices.h by any chance a
dual-processor machine?
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
_________________________________________________________________
無料でメールボックス250MBの 「MSN Hotmail」
http://promotion.msn.co.jp/hotmail/fortune/input_un.asp
_______________________________________________
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