Don't load Framework module.map files when searching subdirectoriesThis would cause frameworks to have spurious "redefinition" errors ifthey had both a (legacy) "module.map" and a (new) "module.mo
Don't load Framework module.map files when searching subdirectoriesThis would cause frameworks to have spurious "redefinition" errors ifthey had both a (legacy) "module.map" and a (new) "module.modulemap" file and wehappened to do a sub-directory search in that directory using anon-framework include path (e.g. -Ifoo/ -Ffoo/). For migrationpurposes it's very handy that the compiler will prefer the new spellingof the filename and not look at the old one if it doesn't need to.llvm-svn: 230308
show more ...
Add a new spelling for module map files 'module.modulemap'This name, while more verbose, plays more nicely with tools that usefile extensions to determine file types. The existing spelling'module
Add a new spelling for module map files 'module.modulemap'This name, while more verbose, plays more nicely with tools that usefile extensions to determine file types. The existing spelling'module.map' will continue to work, but the new spelling will takeprecedence.In frameworks, this new filename will only go in a new 'Modules'sub-directory.Similarly, add a module.private.modulemap corresponding tomodule_private.map.llvm-svn: 204261