On Thu, 2 Nov 2000, Dimitrie O. Paun wrote:
> On Thu, 2 Nov 2000, Alexandre Julliard wrote:
>
> > No, makedep relies on this to find out which headers to include in the
> > dependencies.
>
> OK, I wasn't aware of that. Is this documented anywhere? (Not that I read
> documentation, but... :) )
I don't know if this is documented somewhere but I think it is a
relatively common, i.e. it's not only Wine that uses this convention.
The idea is that you usually already use "xxx.h" for your headers
because some are in a local directory (and <> would not work unless you
have '.' in your path which I consider evil). For system system headers
people usually use <> because obvioulsy they are obvioulsy not going to
be in the local directory (and if they were anyway (which would be even
more evil) then you would not want them). Then when generating
dependencies it's a simple matter to separate the system headers
(included with <>) that never change and which we don't care about from
our headers which keep changing daily and are included by "".
Well, not that I have given my (maybe not so good) explanation of the
rational behind things, here's a good practical reason for doing so:
this corresponds to what 'gcc -MM' does.
`-MM'
Like `-M' but the output mentions only the user header files
included with `#include "FILE"'. System header files included
with `#include <FILE>' are omitted.
--
Francois Gouget [EMAIL PROTECTED] http://fgouget.free.fr/
Any sufficiently advanced bug is indistinguishable from a feature.
-- from some indian guy
