teak-llvm/clang/test/Modules/module-name-private.m
Bruno Cardoso Lopes 5bccc5270e [Modules] Extend -fmodule-name semantic for frameworks with private modules
Assume Foo.framework with two module maps and two modules Foo and
Foo_Private.

Framework authors need to skip building both Foo and Foo_Private when
using -fmodule-name=Foo, since both are part of the framework and used
interchangeably during compilation.

rdar://problem/37500098

llvm-svn: 325305
2018-02-16 00:12:57 +00:00

13 lines
443 B
Objective-C

// RUN: rm -rf %t
// RUN: %clang_cc1 -verify -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -F %S/Inputs/implicit-private-canonical -fsyntax-only %s -Wprivate-module -fmodule-name=A -Rmodule-build
// Because of -fmodule-name=A, no module (A or A_Private) is supposed to be
// built and -Rmodule-build should not produce any output.
// expected-no-diagnostics
#import <A/a.h>
#import <A/aprivate.h>
int foo() { return APRIVATE; }