You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I a file is relative to the compiler in an parent directory (ex.: gcc ../../test.cpp) then FILE contains also ...
This makes generated headers ending up outside the hidden directory .inspector-includes.
Possible hacky solution: Put headers in a sub-sub-sub-sub... directory (.inspector-includes/a/a/a/a/a/a) and print a warning if this level get exceeded.
The text was updated successfully, but these errors were encountered:
If I a file is relative to the compiler in an parent directory (ex.: gcc ../../test.cpp) then FILE contains also
..
.This makes generated headers ending up outside the hidden directory
.inspector-includes
.Possible hacky solution: Put headers in a sub-sub-sub-sub... directory (
.inspector-includes/a/a/a/a/a/a
) and print a warning if this level get exceeded.The text was updated successfully, but these errors were encountered: