Lines Matching refs:module

254     g. `MODULEMAPFILES` : To make module map file available in user level -
257     h. `PRIVATE_MODULEMAPFILES` : To make module map file available to Apple
285 a. `INSTALL_MI_LIST`, `INSTALL_MODULEMAP_MI_LIST` : Installs header and module map
301     module map files to a location that is available for Apple internal in user level.
377 If you want to install the module map file in a sub-directory, specify the
404 within the xnu/bsd module.
406 within the xnu/osfmk module.
437 can be represented by a standalone module. Where this is the case, set
438 `INSTALL_MODULEMAP_MI_DIR` to `INSTALL_MI_DIR` and install a `module.modulemap`
439 file there. `module.modulemap` is used even for private modules in
440 `usr/local/include`; `module.private.modulemap` is not used. Caveat: in order
441 to stay in the simple case, the module name needs to be exactly the same as
446 module map files that are sourced from `usr/include/module.modulemap` and
447 `usr/local/include/module.modulemap`. The naming convention for the `xnu`
448 module map files are as follows.
450 a. Ideally the module map file covers an entire directory. A module map
453 b. Some headers are special and require their own module. In that case,
454     the module map file would be named after the module it defines.
455     A module map file defining the module `One.Two.Three` would be named