llvm-project/clang/test/Modules/include-relative.c

// RUN: rm -rf %t
// RUN: mkdir %t
// RUN: cp -r %S/Inputs/include-relative %t/include-relative
// RUN: cd %t
// RUN: %clang_cc1 -fmodules -fimplicit-module-maps -x c -verify -fmodules-cache-path=%t -I include-relative %s

// expected-no-diagnostics

#include "a.h"

int f() { return n; }
If a module map is found in a relative -I path, convert the filenames within it to absolute paths when building the includes file for the module. Without this, the module build would fail, because the relative paths we were using are not necessarily relative to a directory in our include path. llvm-svn: 203528 2014-03-11 10:02:47 +08:00			`// RUN: rm -rf %t`
			`// RUN: mkdir %t`
			`// RUN: cp -r %S/Inputs/include-relative %t/include-relative`
			`// RUN: cd %t`
[modules] Simplify -cc1 interface for enabling implicit module maps. We used to have a flag to enable module maps, and two more flags to enable implicit module maps. This is all redundant; we don't need any flag for enabling module maps in the abstract, and we don't usually have -fno- flags for -cc1. We now have just a single flag, -fimplicit-module-maps, that enables implicitly searching the file system for module map files and loading them. The driver interface is unchanged for now. We should probably rename -fmodule-maps to -fimplicit-module-maps at some point. llvm-svn: 239789 2015-06-16 08:08:24 +08:00			`// RUN: %clang_cc1 -fmodules -fimplicit-module-maps -x c -verify -fmodules-cache-path=%t -I include-relative %s`
If a module map is found in a relative -I path, convert the filenames within it to absolute paths when building the includes file for the module. Without this, the module build would fail, because the relative paths we were using are not necessarily relative to a directory in our include path. llvm-svn: 203528 2014-03-11 10:02:47 +08:00
			`// expected-no-diagnostics`

			`#include "a.h"`

			`int f() { return n; }`