Restructure Gamma include files required for the generated compiler about gamma HOT 2 OPEN

@linkrope What to you think about moving all those files to src/gruntime - "gruntime" for gamma runtime, similar to druntime?

The dmd compiler call then could be adjusted to
dmd S.d SLex.d -I=src/gruntime;
and at the generated compiler compilation
dmd S.d SLex.d -I=build/gruntime.

This schema is more flexible for the case the gamma compiler generator is carried with the VScode extension or the Eclipse plugin and temporary extracted to an arbitrary configurable project directory structure.

...I would take over to make this change. Just would like to agree with you, first.

from gamma.

Just thought on how to implement this and it seems to me that having a different include path at the development project and at the generated compiler compilation is not a good idea.

So, maybe, it is better to have them all in include/gruntime. That way, the include directive for the D compiler would be always the same: dmd S.d SLex.d -I=include/gruntime
If the extension/plugin is creating the compiler source code at the build sub directory, e.g., then it only would need to copy all include files in the build/include/gruntime directory.

We could also put all include files directly under include where runtime.d is located today already.

Maybe the last option is the best? What do you think?

from gamma.