Messages in this thread | | | Date | Wed, 5 Jun 2002 14:13:25 -0400 | From | Mark Mielke <> | Subject | Re: [kbuild-devel] Re: Announce: Kernel Build for 2.5, release 3.0 is available |
| |
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
-- mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________ . . _ ._ . . .__ . . ._. .__ . . . .__ | 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/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |