After 2.2.1: 'AliasRecord' has no member named 'aliasSize'. UNTRUE!!
After 2.2.1: 'AliasRecord' has no member named 'aliasSize'. UNTRUE!!
- Subject: After 2.2.1: 'AliasRecord' has no member named 'aliasSize'. UNTRUE!!
- From: Jerry Krinock <email@hidden>
- Date: Wed, 18 Jan 2006 19:20:38 -0800
- Thread-topic: After 2.2.1: 'AliasRecord' has no member named 'aliasSize'. UNTRUE!!
I have two projects which A and B which include many of the same files. One
of the common files declares an AliasRecord, from Apple's Alias Manager.
AliasRecord is a struct of two members. As you can see in your
documentation, one member is declared as:
unsigned short aliasSize ;
Well, after updating Xcode to 2.2.1 today, Project B started spewing an
error with the following falsehood:
'AliasRecord' has no member named 'aliasSize'
Xcode is using gcc 4.0, and the error causes compiling to fail, regardless
of whether architecture is "ppc i386" or just "ppc".
Now, I am reading this AliasRecord out of a file, decoding it, and then
casting the resulting NSData to an AliasRecord. Here is the snippet that
triggers the error:
AliasRecord aliasHeader = *(AliasPtr)[decodedData bytes];
nBytesAliasRecord = aliasHeader.aliasSize ;
I shipped both projects with this code several weeks ago, and it still
compiles in Project A.
I worked on this for 3 hours today. I went and re-made my project from the
Assistant, made sure that both projects include exactly the same frameworks
in the same order, and I even compiled it on a different Mac with a fresh
copy of Xcode. No matter what I do, Project B spews the same nonsense.
Any ideas?? Thanks!
Jerry Krinock
Another detail:
Ironically, a few weeks ago, after creating Project B in CodeWarrior,
CodeWarrior starting giving me this same error, and this was my motivation
to finally give up on CodeWarrior. Like I've learned so many times: You
can run away from things you don't understand, but THEY'LL BE BACK!
However both Project A and Project B were re-created by the Assistant in
Xcode, because as usual the CodeWarrior imports were train wrecks. So, this
issue nothing to do with CodeWarrior.
_______________________________________________
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