Lines Matching refs:file

104 of their `System/Library/Extensions/System.kext/Info.plist` file.
149   2. Copy exiting boot configurations to alternate file
182 How to install a new header file from XNU
202 The directory containing the header file should have a Makefile that
204 If you are adding the first header file in a directory, you will need to
207 Add your header file to the correct file list depending on where you want
209 from each file list are -
211     a. `DATAFILES` : To make header file available in user level -
215     b. `DRIVERKIT_DATAFILES` : To make header file available to DriverKit userspace drivers -
218     c. `PRIVATE_DATAFILES` : To make header file available to Apple internal in
222     d. `EMBEDDED_PRIVATE_DATAFILES` : To make header file available in user
228     e. `KERNELFILES` : To make header file available in kernel level -
232     f. `PRIVATE_KERNELFILES` : To make header file available to Apple internal
236     g. `MODULEMAPFILES` : To make module map file available in user level -
239     h. `PRIVATE_MODULEMAPFILES` : To make module map file available to Apple
243     i. `LIBCXX_DATAFILES` : To make header file available to in-kernel libcxx clients:
246     j. `EXCLAVEKIT_DATAFILES` : To make header file available to Apple internal
250     k. `EXCLAVECORE_DATAFILES` : To make header file available to Apple internal
254 The Makefile combines the file lists mentioned above into different
264 by adding the appropriate file lists.  The default install lists, its
265 member file lists and their default location are described below -
275     b. `INSTALL_DRIVERKIT_MI_LIST` : Installs header file to a location that is
290     d. `INSTALL_IF_MI_LIST` : Installs header file to location that is available
297     e. `INSTALL_IF_MI_LCL_LIST` : Installs header file to location that is
304     f.  `INSTALL_SF_MI_LCL_LIST` : Installs header file to a location that is available
311     g. `INSTALL_KF_MI_LIST` : Installs header file to location that is available
318     h. `INSTALL_KF_MI_LCL_LIST` : Installs header file to location that is
325     i. `EXPORT_MI_LIST` : Exports header file to all of xnu (bsd/, osfmk/, etc.)
330     j. `INSTALL_KF_LIBCXX_MI_LIST` : Installs header file for in-kernel libc++ support.
336     k. `INSTALL_EXCLAVEKIT_MI_LIST` : Installs header file to location that is
343     l. `INSTALL_EXCLAVECORE_MI_LIST` : Installs header file to location that is
350 If you want to install the header file in a sub-directory of the paths
357 If you want to install the module map file in a sub-directory, specify the
362 A single header file can exist at different locations using the steps
364 in the header file available at all the locations.  For example, you
368  to control the text generated before a header file is installed.  The kernel
370  code for FALSE conditions from the header file.
400 Module map file name convention
406 file there. `module.modulemap` is used even for private modules in
417     a. Ideally the module map file covers an entire directory. A module map
418        file covering `usr/include/a/b/c` would be named `a_b_c.modulemap`.
421        the module map file would be named after the module it defines.
422        A module map file defining the module `One.Two.Three` would be named
466     settings set target.load-script-from-symbol-file true