On Tue, Jun 04, 2002 at 10:25:20PM -0400, John Cowan wrote:
> Keith Owens scripsit:
> > In order to do separate source and object correctly, kbuild 2.5
> > enforces the rule that #include "" comes from the local directory,
> > #include <> comes from the include path. include/linux/zlib.h
> > incorrectly does #include "zconf.h" instead of #include <linux/zconf.h>,
> > breaking the rules.
> This is not the standard gcc behavior, however; quoted-includes
> can come from the include path, although the current directory
> is searched first. The purpose of <>-includes is to suppress
> searching the current directory.
It raises the question 'who not always use #include "..."'?
In the case of a tool that generates dependencies for a source file,
the difference is sensibility.
In other cases, it is just common sense.
mark
--
[EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
