This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
RE: excessive stab information
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Andy Chittenden'" <AChittenden at bluearc dot com>,"'Daniel Jacobowitz'" <drow at false dot org>,"'Ian Lance Taylor'" <ian at airs dot com>
- Cc: <binutils at sourceware dot org>,"'Martin Dorey'" <mdorey at bluearc dot com>
- Date: Thu, 28 Apr 2005 17:53:19 +0100
- Subject: RE: excessive stab information
----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....