en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/explicit-build/module.modulemap#7f330cdb Make module files passed to a module build via -fmodule-file= available toconsumers of that module.Previously, such a file would only be available if the module happened toactually import something from that module.llvm-svn: 232583 List of files: /llvm-project-15.0.7/clang/test/Modules/Inputs/explicit-build/module.modulemap Wed, 18 Mar 2015 01:42:29 +0000 Richard Smith <richard-llvm@metafoo.co.uk> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/explicit-build/module.modulemap#e842a474 [modules] Initial support for explicitly loading .pcm files.Implicit module builds are not well-suited to a lot of build systems. Inparticular, they fare badly in distributed build systems, and they lead tobuild artifacts that are not tracked as part of the usual dependency managementprocess. This change allows explicitly-built module files (which are alreadysupported through the -emit-module flag) to be explicitly loaded into a build,allowing build systems to opt to manage module builds and dependenciesthemselves.This is only the first step in supporting such configurations, and it shouldbe considered experimental and subject to change or removal for now.llvm-svn: 220359 List of files: /llvm-project-15.0.7/clang/test/Modules/Inputs/explicit-build/module.modulemap Wed, 22 Oct 2014 02:05:46 +0000 Richard Smith <richard-llvm@metafoo.co.uk>