[DGD] #include "file.h" not searching current directory for header file.

[Raymond Jennings]

Interpreting include file paths is the duty of the driver object.

The concept of "current directory" is an abstraction that must be provided
in LPC.  The driver and auto objects are exempt from this policy however
and their includes are given a "default" interpretation.

The kernel library is a good example of this though.


On Mon, Jun 5, 2017 at 1:42 PM, Larry Moore <cylis at mts.net> wrote:

>
> With the exception of auto.c, all other files cannot find header files if
> using a relative path. If I set the header include using an absolute path
> it finds it just fine:
>
> File: /std/room.c
> Eg:
> #include “defs.h”
> Cannot include “defs.h”
> Error = Failed to compile “/std/room.c”
>
> #include “/std/defs.h”
> Compiled.
>
>
> It’s not so bad if our domain files were short, but, when you have large
> file trees with rooms several layers deep, the absolute pathing can get
> tedious. Could there be something I missed when compiling the driver? I’m
> using DGD 1.6. Should I add “.” to the include search paths in the .dgd
> config file?
>
> Any assistance would be appreciated, thanks.
>
> Larry Moore
>
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd