1f6a32b3e7
This would cause frameworks to have spurious "redefinition" errors if they had both a (legacy) "module.map" and a (new) "module.modulemap" file and we happened to do a sub-directory search in that directory using a non-framework include path (e.g. -Ifoo/ -Ffoo/). For migration purposes it's very handy that the compiler will prefer the new spelling of the filename and not look at the old one if it doesn't need to. llvm-svn: 230308
19 lines
717 B
Objective-C
19 lines
717 B
Objective-C
// RUN: rm -rf %t
|
|
// RUN: %clang_cc1 -fmodules -fmodules-cache-path=%t -I %S/Inputs/ModuleMapLocations/Module_ModuleMap -I %S/Inputs/ModuleMapLocations/Both -F %S/Inputs/ModuleMapLocations -I %S/Inputs/ModuleMapLocations -F %S/Inputs -x objective-c -fsyntax-only %s -verify
|
|
|
|
// regular
|
|
@import module_modulemap;
|
|
@import both;
|
|
// framework
|
|
@import Module_ModuleMap_F;
|
|
@import Module_ModuleMap_F.Private;
|
|
@import Both_F;
|
|
@import Inferred;
|
|
|
|
void test() {
|
|
will_be_found1();
|
|
wont_be_found1(); // expected-warning{{implicit declaration of function 'wont_be_found1' is invalid in C99}}
|
|
will_be_found2();
|
|
wont_be_found2(); // expected-warning{{implicit declaration of function 'wont_be_found2' is invalid in C99}}
|
|
}
|