[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] build question -- extra switches
|
James and Ed,
Thanks for the insight. Your information made me question my findings.
Turns out the switch theory was a red herring; the result of sloppy
detective work. The debugger issue is not triggered by those switches,
but rather which toolchain is used (MinGW or Cygwin).
John
At 07:56 AM 4/15/2010, Ed.Swartz@xxxxxxxxx wrote:
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_F69D6574A9EB154AB7DEA2BC80F07DDF22E2D5A9DANOKEUMSG03mgd_"
Hi John,
Those -M options are preprocessor options
that generate the dependency information needed to allow incremental
builds. I don't know where they're generated, because our tooling
bypasses all this stuff, but it's just something I remember.
I'm not sure they'd impact the debugger or
compile behavior, other than preventing unnecessary compiles, but what do
I know :)
http://gcc.gnu.org/onlinedocs/gcc-4.4.1/gcc/Preprocessor-Options.html
-- Ed
- From: John Cortell
[
mailto:rat042@xxxxxxxxxxxxx]
- Sent: Thursday, April 15, 2010 7:44 AM
- To: cdt-dev@xxxxxxxxxxx
- Subject: [cdt-dev] build question -- extra switches
- Can someone familiar with the build support tell me why the compile
line generated by the GNU Make Builder for a simple Cygwin or MinGW
project is
- gcc -O0 -g3 -Wall -c -fmessage-length=0
-MMD -MP -MF"src/p1.d"
-MT"src/p1.d"
-o"src/p1.o" "../src/p1.c"
- but the -MMD -MP -MF and -MT options
don't appear in the GUI (see attached screenshot).
- At least one of these options is triggering a problem for the
debugger. The Internal Builder does not specify those options.
- Seems odd to me that
- (a) the program is built with options that the user is not informed
of via the GUI
- (b) the internal and make builder don't compile the source files the
same way.
- John
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
