When generating template include paths, the relative path to the header is based on the current working directory of the execution. However, this is inconsistent with other code generation where the include path is relative to the model file (symbol location).
When generating template include paths, the relative path to the header is based on the current working directory of the execution. However, this is inconsistent with other code generation where the include path is relative to the model file (symbol location).
This inconsistency should be fixed!