Lines Matching refs:file

117 of their `System/Library/Extensions/System.kext/Info.plist` file.
164 2. Copy exiting boot configurations to alternate file
220 The directory containing the header file should have a Makefile that
222 If you are adding the first header file in a directory, you will need to
225 Add your header file to the correct file list depending on where you want
227 from each file list are -
229     a. `DATAFILES` : To make header file available in user level -
233     b. `DRIVERKIT_DATAFILES` : To make header file available to DriverKit userspace drivers -
236     c. `PRIVATE_DATAFILES` : To make header file available to Apple internal in
240     d. `EMBEDDED_PRIVATE_DATAFILES` : To make header file available in user
246     e. `KERNELFILES` : To make header file available in kernel level -
250     f. `PRIVATE_KERNELFILES` : To make header file available to Apple internal
254     g. `MODULEMAPFILES` : To make module map file available in user level -
257     h. `PRIVATE_MODULEMAPFILES` : To make module map file available to Apple
261     i. `LIBCXX_DATAFILES` : To make header file available to in-kernel libcxx clients:
264     j. `EXCLAVEKIT_DATAFILES` : To make header file available to Apple internal
268     k. `EXCLAVECORE_DATAFILES` : To make header file available to Apple internal
272 The Makefile combines the file lists mentioned above into different
282 by adding the appropriate file lists.  The default install lists, its
283 member file lists and their default location are described below -
293 b. `INSTALL_DRIVERKIT_MI_LIST` : Installs header file to a location that is
308 d. `INSTALL_IF_MI_LIST` : Installs header file to location that is available
315 e. `INSTALL_IF_MI_LCL_LIST` : Installs header file to location that is
322 f.  `INSTALL_SF_MI_LCL_LIST` : Installs header file to a location that is available
329 g. `INSTALL_KF_MI_LIST` : Installs header file to location that is available
336 h. `INSTALL_KF_MI_LCL_LIST` : Installs header file to location that is
343 i. `EXPORT_MI_LIST` : Exports header file to all of xnu (bsd/, osfmk/, etc.)
348 j. `INSTALL_KF_LIBCXX_MI_LIST` : Installs header file for in-kernel libc++ support.
354 k. `INSTALL_EXCLAVEKIT_MI_LIST` : Installs header file to location that is
361 l. `INSTALL_EXCLAVECORE_MI_LIST` : Installs header file to location that is
368 If you want to install the header file in a sub-directory of the paths
377 If you want to install the module map file in a sub-directory, specify the
384 A single header file can exist at different locations using the steps
386 in the header file available at all the locations.  For example, you
390  to control the text generated before a header file is installed.  The kernel
392  code for FALSE conditions from the header file.
425 ## VM header file name convention
434 ## Module map file name convention
439 file there. `module.modulemap` is used even for private modules in
450 a. Ideally the module map file covers an entire directory. A module map
451     file covering `usr/include/a/b/c` would be named `a_b_c.modulemap`.
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
500 settings set target.load-script-from-symbol-file true