request to add additional runtime path

[Frank Ch. Eigler]

Hi -


> One example is that I want to use some macros inside the embedded c 
> functions in my stp files:
> function foo1()
> %{
>     _stp_printf("%d, %d...", EVENTID_1, HOOKID_2, ...);
> %}

Not that this directly relates to your issue, but why would you use
embedded-C for something like this?  Could you post a fuller example?

It is undesirable for embedded C code to make direct calls to the
runtime.  Among other reasons, this is since that API exists for the
convenience of the translator, and thus may change frequently


> [...] such macros appear almost in every stp files, so it's better
> to include a .h file in each stp file [...]

Assuming this were a good idea, it could be supported by adding the
tapset source directories to the C compiler's include path.


- FChE