Dave Korn dave.korn@artimi.com
Thu Apr 28 17:02:00 GMT 2005

• Previous message (by thread): excessive stab information
• Next message (by thread): excessive stab information
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

----Original Message----
>From: Andy Chittenden
>Sent: 28 April 2005 17:48

> that's exactly what we do!

  With the exception of specifying the top-level-include-dir-relative path
to the published header when it's being included by a source file in the
same library, because that's why you're ending up with different paths.

  Hmm.  So perhaps if every compile always has -I include/, so that #include
"module/header.h" will work anywhere, and when compiling module XXX, you
specify "-I include/XXX -I include/" in that order, so that in module XXX a
#include of "header.h" will match include/XXX/header.h before it matches
./header.h ?

  There has to be a way to make this work nicely!
 
    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

---

• Previous message (by thread): excessive stab information
• Next message (by thread): excessive stab information
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list