Re: "Build Failed" Message But Successful Compile and Link
Re: "Build Failed" Message But Successful Compile and Link
- Subject: Re: "Build Failed" Message But Successful Compile and Link
- From: Frank Reiff <email@hidden>
- Date: Mon, 22 Dec 2003 21:01:14 +0100
Dear Sean,
I am new to XCode myself and have only just migrated from CodeWarrior
and I thus experience many of the same problems as you do.
I am not sure whether all of this is exactly relevant to you, but I'll
try to communicate what I've found.
1) How to see what has gone wrong with the build?
When the build goes wrong you can see the details by double clicking on
the error "hammer/build" symbol; this open the "Build Details" window.
You will probably see something in red towards the bottom of this.
Note the resize panel at the bottom. Pull this up to see the real build
log. "Native Build of Target", etc.
2) What has gone wrong?
This is only a guess based on my own experiences.
CodeWarrior does "Dead code stripping" when it links, ie. it removes
all the code that is compiled but can never be called. This means you
get a lot of errors that already existed in your CodeWarrior code, but
that you didn't see because the code causing them was dead-stripped.
There is documentation on what to do at
http://developer.apple.com/tools/switchtoxcode.html
The other thing I discovered today is that the ResMerger tool that
merges all the resource forks of your resource files has changed in
1.1. Previously, it behaved like CodeWarrior: You get a warning that a
resource (say DITL,128) is defined twice, but it will simply appends it
to the output and the program will link and build properly anyway. With
version 1.1 a duplicated resource will "reliably fail" your build.
You can get the old behavior by setting the OTHER_RESMERGERFLAGS in the
Build tab of the target inspector to -a (for append).
I hope this helps. I am only a newbie myself..
Best regards,
Frank
---
Frank Reiff
publispace.net
On Dec 22, 2003, at 6:40 PM, Sean Flaherty wrote:
I have a converted PowerPlant project that we're testing in XCode, but
we've run into a build problem with it. All of the source code
compiles and seems to link correctly, but there is a "Build Failed"
message generated at the end. The application seems to run when
"Debug" is chosen. I suspect the problem is with resource merging and
packaging because that is the last thing changed, but even when I
change things back it still generates a "Build Failed" message.
I saw some similar posts in the archives, but none of the solutions
worked for me. The only one I haven't tried is rebuilding the project
from scratch; it is a big enough project that I don't want to try
that except as a last resort.
Is there any way to get more information on what is failing? Does
anyone have other suggestions? I am using XCode 1.0.1 and 1.1 with
the same problem.
Best Regards,
Sean
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.