[Info-vax] Can C #includes like this be made to work onVMS?

[mjos_examine]

On 2024-10-15 3:21 p.m., Brian Schenkenberger wrote:
> On 2024-10-15 19:15:00 +0000, John Dallman said:
> 
>> In article <vemd23$1qdt1$1 at dont-email.me>, mail at SendSpamHere.ORG (Brian
>> Schenkenberger) wrote:
>>
>>> I want to port a freeware package. It's C code is littered with
>>> includes like:
>>>
>>> #include "package_name/include_file.h"
[...]
> 
> In the distribution, the includes are in a directory:
> 
> [package_name.INCLUDE]
> 
> and the source is in [package_name.SRC]
> 
> I am hoping not to have to edit all of the sources to change the 
> #include "..."s.


$ create/dir dka100:[my_package_name.include]
$ edit/edt dka100:[my_package_name.include]include_file.h
$ dir dka100:[my_package_name.include]

Directory DKA100:[my_package_name.include]

INCLUDE_FILE.H;1

Total of 1 file.
$ define package_name [my_package_name.include]

$ show def
dka100:[devel.testincl]

$ type dka100:[devel.testincl]test.c
#include <stdio.h>
#include <stdlib.h>
#include "package_name/include_file.h"

int main(int argc, char *argv[])
{
     printf("this is a test: %s.\n", testresult);
}

$ cc test.c
$