| Date Of Receipt: 7-MAY-1993 01:40:02.28
From: MINSRV::"[email protected]" "Joshua M. Friedman ULTRIX SDE"
To: [email protected]
CC: [email protected], [email protected]
Subj: re: Changing an include file...
Bill, here's how it works. If the include is done, as you show, using
the 'include <file.h>' syntax, then the <>s mean look for the file
strictly along the -I path as defined, which first looks in your private
sandbox and then in the backing tree. This means you do NOT need to
do the bco you suggest.
If the include is done using the 'include "file.h"' syntax, the ""s tell
the preprocessor to first look in the directory in which the file that
contains the include was found, and then look along the -I path. In this
case, you in fact do need to have the file which does the including in
your sandbox, or else the file.h from the backing tree will be used.
You can have the file via a link (using mklinks) or a copy, as from
bco -u file (or bsh cat file > file).
During MIPS/Silver development, a switch "-no_current_include" was
added to the preprocessor and turned on via the rc_files to make it
such that ""s were interpreted the same as <>s, to insure proper
building in sandboxes. This support was not carried over to the
alpha port.
In reality, with our current build structure, there should not be
any uses of the include "" format; all includes should use <>,
however they don't.
-josh
------- Forwarded Message
Return-Path: [email protected]
Received: by krisis.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
id AA00243; Wed, 5 May 1993 11:56:14 -0400
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Changing an include file...
Date: Wed, 05 May 93 11:56:13 -0400
From: John Flanagan <[email protected]>
X-Mts: smtp
- ------- Forwarded Message
Return-Path: grava
Received: by krisis.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
id AA29896; Wed, 5 May 1993 11:49:56 -0400
Received: by awasted.zk3.dec.com; id AA15636; Wed, 5 May 1993 11:50:15 -0400
Message-Id: <[email protected]>
To: odehelp
Subject: Changing an include file...
Date: Wed, 05 May 93 11:50:15 +28716
From: grava
X-Mts: smtp
I'm adding a new #define to devio.h. The new constant is for the
benefit of third-party devices, so none of the existing kernel code will
care about the new addition. However, I want to be certain that the code
that cares about this include file will at least have the opportunity to
see and ignore this new constant. Do I have to 'bco -u' the source files
that include <sys/devio.h> to force them to see the new include file, or
will the 'bco /kernel/io/common/devio.h' checkout command cover me?
Thanks,
bill grava
- ------- End of Forwarded Message
------- End of Forwarded Message
|