Kbase 15108: How to specify WHERE the r-code goes?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
How to specify WHERE the r-code goes?
The Procedure Settings Dialog box has a
fill-in labeled 'Compile In' which is
for specifying a directory in which to place
the r-code when a compile is done. You can
specify this directory and save it in the
template so that all objects created with that
template will be compiled into the same
directory, if you wish.
Another scenario is that you may specify a
a relative pathname instead of a full pathname.
This can be done by specifying a
directory that exists underneath a directory
that was specified in the PROPATH. For example,
if you have a PROPATH specified as follows:
PROPATH="/apps/xxx/dev/run:/apps/xxx/dev/src:..."
and you specify the 'ar/cust' as the
directory to compile into, then the r-code will
be generated and placed in /apps/xxx/dev/run/ar/cust
because /apps/xxx/dev/run was the first
directory in the PROPATH that had a subdirectory 'ar/cust'
underneath it.
In this way, you can use the PROPATH and the
compile in specification in combination to control
the placement of your r-code without having to give
full pathnames. From this example you can see how
important the ORDER is in which your directories are
specified in your PROPATH.
Progress Software Technical Support Note # 15108