From owner-freebsd-arch Mon Jan 22 22:52:42 2001 Delivered-To: freebsd-arch@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id D430337B402; Mon, 22 Jan 2001 22:52:24 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14KxQr-0000Kb-00; Mon, 22 Jan 2001 23:59:57 -0700 Message-ID: <3A6D2BED.66CA8268@softweyr.com> Date: Mon, 22 Jan 2001 23:59:57 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Justin T. Gibbs" Cc: arch@FreeBSD.org, bde@FreeBSD.org Subject: Re: Local driver include files. References: <200101222012.f0MKCns65410@aslan.scsiguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Justin T. Gibbs" wrote: > > When writing core driver code to run on several operating systems, > the fact that we use -nostdinc becomes a real pain in the but. > Take a look at sys/dev/aic7xxx/aic7xxx.c: > > #ifdef __linux__ > #include "aic7xxx_linux.h" > #include "aic7xxx_inline.h" > #include "aicasm/aicasm_insformat.h" > #endif > > #ifdef __FreeBSD__ > #include > #include > #include > #endif > > If we provided "-Ipath/to/file/being/compiled" this could > be replaced with: > > #include "aic7xxx_osm.h" > #include "aic7xxx_inline.h" > #include "aicasm/aicasm_insformat.h" > > This is a much more scalable approach. > > I can understand the desire to fully document the path to > an include file, but is this really too much to ask? No, it's not. What does that have to do with -nostdinc? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message