[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | USG buildhelp questions/answers |
|
Moderator: | SMURF::FILTER |
|
Created: | Mon Apr 26 1993 |
Last Modified: | Mon Jan 20 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2763 |
Total number of notes: | 5802 |
1118.0. "Re: re-2:same file name s build export" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Dec 13 1994 15:59
Date Of Receipt: 28-NOV-1994 23:27:35.95
From: FLUME::jmcg "Jim McGinness"
To: [email protected]
CC: buildhelp@DEC:.zko.flume
Subj: Re: re-2:same file name's build export
As I said, I was a little unclear on what you were ultimately trying
to do.
I assume you are making a change to one of the signal.h files and
want to propagate that change out to the export and obj trees without
doing a complete rebuild of everything that depends on signal.h. I
haven't tested out the export_signal.h rule, but I would expect it to
do something to the export tree in the 3 marked Makefiles. I don't
believe these Makefiles will populate the obj tree (particularly
usr/sys/include/...) with that rule. Nothing in the build should
depend on something in the obj tree, but the files in the obj tree --
not the ones in the export tree -- are the ones that the install step
eventually places on the result disk. Updating just the export tree
might be all you need to do...but I would probably want all the copies
of signal.h to be updated after the change.
As to the last part, when I looked at the export tree, I saw it
contained no usr/sys directory. This is the location used when the
customer rebuilds the system after installation but is not used by our
build procedures.
T.R | Title | User | Personal Name | Date | Lines
|
---|