GenerateDSYMFile randomly failing when nothing needs compiling
GenerateDSYMFile randomly failing when nothing needs compiling
- Subject: GenerateDSYMFile randomly failing when nothing needs compiling
- From: Rua Haszard Morris <email@hidden>
- Date: Thu, 31 May 2007 16:23:24 +1200
I'll file a bug with the real transcript next time it happens.
For the record we're using Xcode 2.4, gcc 4.0.1 for all projects.
dSYM generation is only in the release configuration(s).
Interestingly, there were no compiles in the transcript - just
"checking dependencies" for all the sub projects and then
GenerateDSYMFile
cd {project folder}
/usr/bin/dsymutil -o {plugin bundle path with dSYM suffix} {path to
executable inside bundle}
ERROR: No debug map or DWARF data was found to link.
** BUILD FAILED **
(you can see why my previous edit was so pitiful)
And on further inspection, this particular product is in the build
config twice, explaining why it didn't need anything compiled.
So I rephrase my issue: is there an expectation that dSYM generation
works when doing just a relink?
cheers
Rua.
On 31/05/2007, at 3:58 PM, Chris Espinosa wrote:
On May 30, 2007, at 4:09 PM, Rua Haszard Morris wrote:
I recently switched to DSYM generation for our release builds, and
have been experiencing occasional build failures due to "No debug
map or DWARF data was found to link".
I had similar problems with unclean builds when setting up, and
assumed it was a quirk that could be ignored and worked around by
doing a full compile. However it's also happening on our nightly
clean release builds in a fairly random manner - for example, one
project of one product broke last night, and re-running that
product build again just now made the problem go away.
Anybody else seen this happening? Any tips on using dSYM? If
anyone could shed any light on why this is happening or how to
work around it I'd be very appreciative.
here's an edited transcript
GenerateDSYMFile
...
ERROR: No debug map or DWARF data was found to link.
** BUILD FAILED **
You edited out all the information that might have been useful to
diagnose this. File a bug with the unedited transcript and we'll
take a look. That said, there are three known cases for this failure:
- One where the build product is a static library, for which a dsym
is inappropriate. This was fixed in Xcode 2.3
- One where the gcc 3.3 compiler is used but dsymutil is invoked
anyway. This is active and may be your case. Ensure you're using
gcc 4.
- One where building debug/release variants overwrites the dsym
file. This may be your case if you are using those variants, but
it's not likely.
There are no known cases where it randomly fails.
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