Bug: include behavior on Windows
In the current build system on windows (at least for the CI tests), we can't use #include <something>
to include a ParaView file that is under a different folder than the one we're including from.
This shouldn't be happening since looking at msvc doc, #include ""
is the same as #include <>
plus:
- In the same directory as the file that contains the #include statement.
- In the directories of any previously opened include files in the reverse order in which they were opened. The search starts from the directory of the include file that was opened last and continues through the directory of the include file that was opened first. Clearly the first makes no difference for two files in two different directories, which led me to suspect that somehow it's failing because of the second search.
Note that it works perfectly under linux and osx.