Generation for non-local directories

Jens Engel — Mon, 21 Jul 2003 16:53:59 -0000

When processing frames that are not located in the current
working directory, it would be desirable to generate them
relative to the SPC file (or the FRAME file).

The OUTFILE command contains normally a rather simple
or a relative pathname. When a relative pathname is used,
this pathname is expressed relative to the location of SPC
or FRAME file (depending where OUTFILE is defined).

EXAMPLE:
# -- file:MySPC.spc
ADAPT MyFrameSubdir/MyFrame.frame
OUTFILE MyOutput/fileB.txt
...
# -- END-OF-FILE
sh> cd ..
sh> fp MySpcDir/MySPC.spc
CURRENT-OUTPUT:
generating MyOutput/fileB.txt
DESIRED-OUTPUT:
generating MySpcDir/MyOutput/fileB.txt

RATIONALE:
A normal C/C++ compiler also behaves like this.
For example, searches for include files relative to the
location of the source file. It generates (BY-DEFAULT) the
output-file in the location of the source file, independent
from which directory it is called.

DEFAULTS for Placeholders/Slots

Jens Engel — Mon, 21 Jul 2003 16:25:44 -0000

It would be usefull to provide defaults for placeholders.
Normally, you need a RENAME command in the SPC file to
provide this for default and non-default values. It would
better to provide default values for placeholders in the
FRAME file.

DESIRED-SYNTAX (Something like that):
"SLOT" PlaceHolderName OptionalDefaultValue

EXAMPLE:
SLOT MySlot1 0x0815
SLOT MySlot2

NOTE:
The second case may cause a warning or an error of the
placeholder value is not supplied via RENAME in the SPC
file (ERROR_IF_NOT_SUPPLIED).

Recent changes to support-requests

Generation for non-local directories

DEFAULTS for Placeholders/Slots