[cfe-dev] Any differences between Windows and Linux header search?

[papin_g]

Hi,

I was wondering if there is any known differences on the way the header path search is performed between Windows and Unix like systems? Especially regarding angled #include <> resolution.
Or maybe the difference can be with virtual file mapping between the two platforms.

I'm working on the C++11 migrator where I made a class to modify #include directives but I have a hard time getting the unit tests to work on the Windows build bots.

The IncludeDirectivesTest.cpp file available here: http://llvm-reviews.chandlerc.com/D1438#ca09f9a2
The buildbots errors are about the includes not being found, see :
- http://bb.pgr.jp/builders/ninja-clang-i686-msc17-R/builds/4176
- http://bb.pgr.jp/builders/cmake-clang-i686-mingw32/builds/3837


The test setups some virtual files (headers) using FileManager::getVirtualFile() and SourceManager::overrideFileContents().
The virtual files are mapped in "$(pwd)/virtual/HEADER" and $(pwd) is added to the header search path with the option "-I".

It looks like to me the test has no dependencies on the file system specifics but it breaks only on the  Windows build bots.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130826/ac2dfcf0/attachment.html>