Lines Matching refs:file

105 of their `System/Library/Extensions/System.kext/Info.plist` file.
150   2. Copy exiting boot configurations to alternate file
183 How to install a new header file from XNU
203 The directory containing the header file should have a Makefile that
205 If you are adding the first header file in a directory, you will need to
208 Add your header file to the correct file list depending on where you want
210 from each file list are -
212     a. `DATAFILES` : To make header file available in user level -
216     b. `DRIVERKIT_DATAFILES` : To make header file available to DriverKit userspace drivers -
219     c. `PRIVATE_DATAFILES` : To make header file available to Apple internal in
223     d. `EMBEDDED_PRIVATE_DATAFILES` : To make header file available in user
229     e. `KERNELFILES` : To make header file available in kernel level -
233     f. `PRIVATE_KERNELFILES` : To make header file available to Apple internal
237     g. `MODULEMAPFILES` : To make module map file available in user level -
240     h. `PRIVATE_MODULEMAPFILES` : To make module map file available to Apple
244     i. `LIBCXX_DATAFILES` : To make header file available to in-kernel libcxx clients:
247     j. `EXCLAVEKIT_DATAFILES` : To make header file available to Apple internal
251     k. `EXCLAVECORE_DATAFILES` : To make header file available to Apple internal
255 The Makefile combines the file lists mentioned above into different
265 by adding the appropriate file lists.  The default install lists, its
266 member file lists and their default location are described below -
276     b. `INSTALL_DRIVERKIT_MI_LIST` : Installs header file to a location that is
291     d. `INSTALL_IF_MI_LIST` : Installs header file to location that is available
298     e. `INSTALL_IF_MI_LCL_LIST` : Installs header file to location that is
305     f.  `INSTALL_SF_MI_LCL_LIST` : Installs header file to a location that is available
312     g. `INSTALL_KF_MI_LIST` : Installs header file to location that is available
319     h. `INSTALL_KF_MI_LCL_LIST` : Installs header file to location that is
326     i. `EXPORT_MI_LIST` : Exports header file to all of xnu (bsd/, osfmk/, etc.)
331     j. `INSTALL_KF_LIBCXX_MI_LIST` : Installs header file for in-kernel libc++ support.
337     k. `INSTALL_EXCLAVEKIT_MI_LIST` : Installs header file to location that is
344     l. `INSTALL_EXCLAVECORE_MI_LIST` : Installs header file to location that is
351 If you want to install the header file in a sub-directory of the paths
358 If you want to install the module map file in a sub-directory, specify the
363 A single header file can exist at different locations using the steps
365 in the header file available at all the locations.  For example, you
369  to control the text generated before a header file is installed.  The kernel
371  code for FALSE conditions from the header file.
401 Module map file name convention
407 file there. `module.modulemap` is used even for private modules in
418     a. Ideally the module map file covers an entire directory. A module map
419        file covering `usr/include/a/b/c` would be named `a_b_c.modulemap`.
422        the module map file would be named after the module it defines.
423        A module map file defining the module `One.Two.Three` would be named
467     settings set target.load-script-from-symbol-file true