Re: Specify multi-variant/arch output in custom build rule
Re: Specify multi-variant/arch output in custom build rule
- Subject: Re: Specify multi-variant/arch output in custom build rule
- From: Jonas Maebe <email@hidden>
- Date: Sat, 8 Jul 2006 22:17:31 +0200
On 4 mei 2006, at 10:40, Jonas Maebe wrote:
As noted in my other mail, the "-x assembler" is the culprit. Is
there maybe some sort of CUSTOM_ASSEMBLER_FLAGS setting which I
can modify to add "-x assembler-with-cpp" to that command?
(before the input file, since it doesn't have any effect when it
comes after an assembler file, but after the "-x assembler"
switch, since they override each other)
I would've expected Xcode to pass -x assembler-with-cpp by
default. I'm surprised it doesn't, since I can't think of a
reason not to.
Maybe speed.
This problem was solved in Xcode 2.3 (for which my thanks), but I've
got another problem now: Xcode (obviously) passes "-g" to gcc when
assembling such files in debug mode.
This means that gcc adds line information for the assembler file
itself. This confuses the hell out of gdb, because those files now
contain two sets of line info: one for the original Pascal source and
one for the assembler file. Depending on how the line information is
requested and which stab is "closer", gdb uses one or the other.
I can solve this by setting GCC_GENERATE_DEBUGGING_SYMBOLS to NO for
the debug build, but this obviously doesn't work well for mixed C/
Pascal projects (since then the C files will be compiled without
debug info as well). A workaround is to get info on the Pascal files
and add "-g0" to their "compiler flags" tab, but it doesn't seem to
be possible to specify this globally for all Pascal files (only for
individual files), so it's not a solution for templates.
Jonas
_______________________________________________
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