ClangSharp icon indicating copy to clipboard operation
ClangSharp copied to clipboard

Add option to use relative paths for NativeTypeName

Open thhous-msft opened this issue 3 years ago • 2 comments

Right now, a full path to each header file is used for NativeTypeName in generated files. This makes it so generating in CI or across different dev systems has different paths. Instead, an option to allow relative paths to be used for this would be very helpful for reproducible generations.

thhous-msft avatar Aug 15 '21 02:08 thhous-msft

What would this path be relative to? A separate/explicitly stated option?

tannergooding avatar Aug 16 '21 15:08 tannergooding

Likely, yeah. I'm generating into a path in the source tree, so a relative path in the same source tree is what I would want.

thhous-msft avatar Aug 16 '21 15:08 thhous-msft