update_dyld_shared_cache(1) [mojave man page]

update_dyld_shared_cache(1)				    BSD General Commands Manual 			       update_dyld_shared_cache(1)

NAME

     update_dyld_shared_cache -- Updates dyld's shared cache

SYNOPSIS

     update_dyld_shared_cache [-root directory] [-overlay directory] [-arch arch] [-force] [-debug] [-universal_boot]

DESCRIPTION

     update_dyld_shared_cache ensures that dyld's shared cache is up-to-date.  This tool is normally only run by Apple's Installer and Software
     Update, as they are the only official ways for OS dylibs to be updated.  But if for some reason you used another mechanism to alter an OS
     dylib, you should manually run update_dyld_shared_cache.

     Note that the new cache does not take effect until the OS is rebooted.

     The dyld shared cache is mapped by dyld into a process at launch time. Later, when loading any mach-o image, dyld will first check if is in
     the share cache, and if it is will use that pre-bound version instead of opening, mapping, and binding the original file.	This results in
     significant performance improvements to launch time.

     update_dyld_shared_cache scans the directory /System/Library/Receipts/ for .bom files which list all files installed.  From that info it cre-
     ates the set of OS dylibs to build into the dyld cache.

     update_dyld_shared_cache builds a separate cache file for each architecture.  The cache files and a readable text map of the cached are gen-
     erated to /var/db/dyld.

     You must be root to run this tool.

     The options are as follows:

     -root directory
		 This option specifies the root of an OS installation for which dyld's shared cache should be updated.	This is used by the In-
		 staller to update the dyld shared cache in a partition other than the one you into which you are currently booted.  The cache
		 files are created in the var/db/dyld directory of the specified directory.  Note: if you are manually doing this, be sure to run
		 the update_dyld_shared_cache tool that is in the partition being updated.  This assures the cache format created will match that
		 expected when booting off that partition.

     -overlay directory
		 This option specifies the root of a sparse directory tree.  When building the dyld shared cache, any corresponding mach-o files
		 in the sparse directory will override those in the boot partition.  This is used by Software Update to build a dyld shared cache
		 for the update that is about to be installed.	The cache files are created in the var/db/dyld directory of the specified direc-
		 tory.

     -arch arch  By default update_dyld_shared_cache generates cache files for all architecture that the current machine can execute.  You can
		 override this behavior by specifying one or more -arch options and list exactly which architectures should have their shared
		 caches updated.

     -force	 This option will cause update_dyld_shared_cache to regenerated the shared cache files even if they appear to be already up-to-
		 date.

     -debug	 This option prints out additional information about the work being done.

     -universal_boot
		 This option builds caches for all machines.

SEE ALSO

     dyld(1)

Darwin								   June 1, 2017 							    Darwin

Check Out this Related Man Page

FC-CACHE(1)															       FC-CACHE(1)

NAME

       fc-cache - build font information cache files

SYNOPSIS

       fc-cache  [ -EfrsvVh ]  [ --error-on-no-fonts ]	[ --force ]  [ --really-force ]  [  [ -y dir ]	[ --sysroot dir ]  ]  [ --system-only ]  [
       --verbose ]  [ --version ]  [ --help ]  [ dir... ]

DESCRIPTION

       fc-cache scans the font directories on the system and builds font information cache files for applications using fontconfig for their  font
       handling.

       If  directory  arguments  are not given, fc-cache uses each directory in the current font configuration. Each directory is scanned for font
       files readable by FreeType. A cache is created which contains properties of each font and the associated filename.  This cache is  used	to
       speed up application startup when using the fontconfig library.

       Note that fc-cache must be executed once per architecture to generate font information customized for that architecture.

OPTIONS

       This  program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included
       below.

       -E     Raise an error if there are no fonts in dir or directories in the configuration if not given.

       -f     Force re-generation of apparently up-to-date cache files, overriding the timestamp checking.

       -r     Erase all existing cache files and rescan.

       -s     Only scan system-wide directories, omitting the places located in the user's home directory.

       -v     Display status information while busy.

       -y     Prepend dir to all paths for scanning.

       -h     Show summary of options.

       -V     Show version of the program and exit.

       dir    Directory to scan for fonts.

RETURN CODES

       fc-cache returns zero if the caches successfully generated. otherwise non-zero.

FILES

       %cachedir%/*-%arch%.cache-%version%
	      These files are generated by fc-cache and contain maps from file names to font properties. They are read by the  fontconfig  library
	      at application startup to locate appropriate fonts.

SEE ALSO

       fc-cat(1) fc-list(1) fc-match(1) fc-pattern(1) fc-query(1) fc-scan(1)

       The fontconfig user's guide, in HTML format: /usr/share/doc/fontconfig/fontconfig-user.html.

AUTHOR

       This manual page was written by Keith Packard <keithp@keithp.com> and Josselin Mouette <joss@debian.org>.

								   Aug 13, 2008 						       FC-CACHE(1)

Linux and UNIX Man Pages

update_dyld_shared_cache(1) [mojave man page]

Check Out this Related Man Page