Conference smurf::buildhelp

Date Of Receipt: 	14-SEP-1995 16:05:19.13
From: 	SMURF::FLUME::jmcg "Jim McGinness"
To: 	[email protected]
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re:  submitting links to a pool??

Won't VPATH do what you need?  There are some assumptions that have
been built up about ODE trees that would be broken if the source
tree itself contained links.

 -- jmcg

Date Of Receipt: 	14-SEP-1995 17:37:13.47
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  14-Sep-1995 1735"
To: 	[email protected]
CC: 	[email protected], [email protected], [email protected]
Subj: 	Re: submitting links to a pool??

Steve, I agree with Jim; VPATH is definitely the appropriate mechanism
to accomplish what you want.  At the top of each make file that need to
access "linked" sources, just put a directive like this; here I've shown
how to have more than one alternate directory for make to look in:
          
          VPATH    =     ${MAKETOP}/path/a:${MAKETOP}/path/b:../path/c

where path/a and path/b are relative to src (MAKETOP is the directory
which contains the Makeconf file, and gets automatically defined by make),
and path/c is "dot-relative" to the current directory.

-josh

------
Date: Thu, 14 Sep 1995 16:03:44 -0400
From: Jim McGinness <jmcg>
To: [email protected]
Subject: Re:  submitting links to a pool??
Cc: odehelp

Won't VPATH do what you need?  There are some assumptions that have
been built up about ODE trees that would be broken if the source
tree itself contained links.

 -- jmcg
------

> 
> Hi Chuck,
> 
> I may have asked you this before, but here goes...
> 
> In the qaqc pool, there's a situation where we want to make a certain
> subtree of the pool sortof autonomous with respect to the rest.  That is,
> this subtree contains everything that it needs to run its own tests.
> 
> However, elsewhere in the pool (outside this subtree) there are tools
> which we wish to incorporate in the subtree.  So, we were hoping that
> rather than copy (and maintain) the tools, we could somehow submit a
> symbolic link to the pool.  Is there a way to submit such a link to
> the pool?
> 
> Make sense?
> 
> Thanks,
> --steve
> 

Date Of Receipt: 	14-SEP-1995 18:01:32.81
From: 	SMURF::ALPHA::"[email protected]" "14-Sep-1995 1459"
To: 	"Joshua M. Friedman, OSF/UNIX SDE 381-1548" <[email protected]>
CC: 	[email protected], [email protected], [email protected]
Subj: 	Re: submitting links to a pool??

Hi Josh,

I don't think that this will do exactly what we want because we're supposedly
going to donate the contents of this tree to the CDE partners.  When we copy
or tar up the tree, the VPATH would, in this case, reference nonexistent
files.

With a symbolic link, we can cause cp or tar to get the referenced file
instead of the link.  This is the kind of behavior that we want.

So, we effectively want to have a way to generate "snapshots" of this
subtree such that there will be no unfulfilled references.

If there's no other facility for this kind of thing, I reckon we'll have
to bite the bullet and manually sync the two files.

Thanks much,
--steve

) Steve, I agree with Jim; VPATH is definitely the appropriate mechanism
) to accomplish what you want.  At the top of each make file that need to
) access "linked" sources, just put a directive like this; here I've shown
) how to have more than one alternate directory for make to look in:
)           
)           VPATH    =     ${MAKETOP}/path/a:${MAKETOP}/path/b:../path/c
) 
) where path/a and path/b are relative to src (MAKETOP is the directory
) which contains the Makeconf file, and gets automatically defined by make),
) and path/c is "dot-relative" to the current directory.
) 

Date Of Receipt: 	14-SEP-1995 19:32:17.04
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  14-Sep-1995 1930"
To: 	[email protected]
CC: 	[email protected], [email protected], [email protected]
Subj: 	Re: submitting links to a pool??

Steve, another way to accomplish what you want is that the sources live
in one place, and any other place that needs that source, instead of
using the VPATH directive in the Makefile, can tar-copy the sources
or make symlinks during the build process.  These would not be part of
the submit pool, but would appear in the build tree, and would, I
believe, accomplish what you want, without compromising the integrity
of the ODE source control model.

-josh

> 
> Hi Josh,
> 
> I don't think that this will do exactly what we want because we're supposedly
> going to donate the contents of this tree to the CDE partners.  When we copy
> or tar up the tree, the VPATH would, in this case, reference nonexistent
> files.
> 
> With a symbolic link, we can cause cp or tar to get the referenced file
> instead of the link.  This is the kind of behavior that we want.
> 
> So, we effectively want to have a way to generate "snapshots" of this
> subtree such that there will be no unfulfilled references.
> 
> If there's no other facility for this kind of thing, I reckon we'll have
> to bite the bullet and manually sync the two files.
> 
> Thanks much,
> --steve
> 
> ) Steve, I agree with Jim; VPATH is definitely the appropriate mechanism
> ) to accomplish what you want.  At the top of each make file that need to
> ) access "linked" sources, just put a directive like this; here I've shown
> ) how to have more than one alternate directory for make to look in:
> )           
> )           VPATH    =     ${MAKETOP}/path/a:${MAKETOP}/path/b:../path/c
> ) 
> ) where path/a and path/b are relative to src (MAKETOP is the directory
> ) which contains the Makeconf file, and gets automatically defined by make),
> ) and path/c is "dot-relative" to the current directory.
> )