Infer "link" lines for top-level frameworks. Essentially, a frameworkwill have a shared library with the same name as its framework (and nosuffix!) within its .framework directory. Detect this both
Infer "link" lines for top-level frameworks. Essentially, a frameworkwill have a shared library with the same name as its framework (and nosuffix!) within its .framework directory. Detect this both wheninferring the whole top-level framework and when parsing a module map.llvm-svn: 172439
show more ...
Introduce the notion of excluded headers into the module mapdescription. Previously, one could emulate this behavior by placingthe header in an always-unavailable submodule, but Argyrios guilted me
Introduce the notion of excluded headers into the module mapdescription. Previously, one could emulate this behavior by placingthe header in an always-unavailable submodule, but Argyrios guilted meinto expressing this idea properly.llvm-svn: 165921
Introduce module attributes into the module map grammar, along with asingle attribute ("system") that allows us to mark a module as being a"system" module. Each of the headers that makes up a syste
Introduce module attributes into the module map grammar, along with asingle attribute ("system") that allows us to mark a module as being a"system" module. Each of the headers that makes up a system module isconsidered to be a system header, so that we (for example) suppresswarnings there.If a module is being inferred for a framework, and that frameworkdirectory is within a system frameworks directory, infer it as asystem framework.llvm-svn: 149143
When generating includes for all of the headers we found in anumbrella directory, skip includes for any headers that are part of anunavailable module.llvm-svn: 147572
When we have an umbrella directory in a module map, recursively walkthe subdirectories to find headers in submodules.llvm-svn: 146398
Implement the notion of umbrella directories, which implicity coverall of the headers below that particular directory. Use umbrelladirectories as a clean way to deal with (1) directories/frameworks
Implement the notion of umbrella directories, which implicity coverall of the headers below that particular directory. Use umbrelladirectories as a clean way to deal with (1) directories/frameworksthat don't have an umbrella header, but don't want to enumerate all oftheir headers, and (2) PrivateHeaders, which we never want toenumerate and want to keep separate from the main umbrella header. This also eliminates a little more of the "magic" for private headers,and frameworks in general.llvm-svn: 146235