AGAIN! -> Re: Fatal PBXHeaderMap alert while building
AGAIN! -> Re: Fatal PBXHeaderMap alert while building
- Subject: AGAIN! -> Re: Fatal PBXHeaderMap alert while building
- From: Allen Cronce <email@hidden>
- Date: Sat, 25 Mar 2006 09:19:07 -0800
I'm now seeing this same "headermap" error with a brand new project I
created this morning. This really isn't funny anymore.
I have to assume that since only a handful of people have run into this
that there is something unusual in my work patterns that leads to this
problem. But the only "unusual" things that come to mind are the fact
that 1) I always change the default build directory to one shared by all
our projects, and 2) I always have dependencies to subprojects that
provide static libraries to link against.
Does anyone have any ideas as to how to either correct or avoid this
incredibly irritating problem? I really want to just develop my
products, not screw around endlessly with nonsense like this.
At the risk of ranting, I have to say that since moving the majority of
our code from CodeWarrior to Xcode, the amount of time that our
engineers spend with tool related problems is way up. That means that
coding productivity is down.
And it's not just due to an unfamiliarity with Xcode. We've all been
using Xcode for over a year and I think we know what we're doing.
It's due to oddball Xcode problems like this where there's no visibility
into the nature of the issue and no real support. Sometimes we get
answers on this list, and sometimes not. And it just isn't practical or
possible to fire off a DTS incident every time we hit an Xcode brick wall.
And of course the fact that the linker is just so primitive compared to
CW doesn't help. We had to totally change how we organize our
sublibraries in order to deal with the single pass nature of the linker.
When was the last time you had to actually worry about the order of your
static libraries to get a clean link? Makes me feel like it's the '70's
again ;-)
CodeWarrior was far from perfect. And there are lot's of things that I
really love about Xcode. But in general CW allowed us to concentrate on
the development job at hand, and not on the underlying build mechanics.
Xcode has really got to improve in this area or it's going to affect our
ability to execute.
Best,
--
Allen Cronce
Allen Cronce wrote:
This same error started happening when attempting to drive the build
of the problem project from the command line. Ultimately the work
around was to rebuild the problem project from scratch.
I have the original problem project and the rebuilt working one in
case anyone from the Xcode team is interested in what caused this
problem.
Best regards,
--
Allen Cronce
Allen Cronce wrote:
Hi all,
One of my projects started showing the following scary alert yesterday
when building:
--snip--
File:
/SourceCache/DevToolsBase/DevToolsBase-660/pbxcore/Target.subproj/PBXTarget.m
Line: 5665
Object: <PBXNativeTarget:0x0d8a42f0>
Method: workQueueForBuildingWithBuildOperation:
headermap should be an instance inheriting from PBXHeaderMap, but it
is nil
--snip--
The options provided are to continue or quit Xcode. Continuing just
displays additional error alerts.
I narrowed the issue down to a dependency on a certain subproject. When
I remove the subproject, the problem goes away. But that's not a good
work around for me.
I've seen a couple of other people on this list mentioning this problem,
but I haven't seen any responses. Any ideas for a solution?
Best regards,
--
Allen Cronce
_______________________________________________
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