From owner-freebsd-arch  Mon Jan 22 12:13: 8 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106])
	by hub.freebsd.org (Postfix) with ESMTP
	id F009637B6A6; Mon, 22 Jan 2001 12:12:50 -0800 (PST)
Received: from scsiguy.com (localhost [127.0.0.1])
	by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0MKCns65410;
	Mon, 22 Jan 2001 13:12:50 -0700 (MST)
	(envelope-from gibbs@scsiguy.com)
Message-Id: <200101222012.f0MKCns65410@aslan.scsiguy.com>
To: arch@FreeBSD.org
Cc: bde@FreeBSD.org
Subject: Local driver include files.
Date: Mon, 22 Jan 2001 13:12:49 -0700
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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 <dev/aic7xxx/aic7xxx_freebsd.h>
#include <dev/aic7xxx/aic7xxx_inline.h>
#include <dev/aic7xxx/aicasm/aicasm_insformat.h>
#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?

--
Justin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message