When MzScheme's load/use-compiled, load-relative, or require-library procedure is used to load a file, MzScheme automatically detects an alternate byte code and/or native code compiled file that resides near the requested file. Byte code files are found in a compiled subdirectory in the directory of the requested file. Native code files are found in (build-path dir "compiled" "native" (system-library-subpath)) where dir is the directory of the requested file. A byte code or native code file is used in place of the rquested file only if its modification date is later than the requested file. If both byte code and native code files are found, the native code file is loaded.
Example:
mzc --extension --destination compiled native i386-linux file.ssUnder Linux, the above command compiles file.ss in the current directory and produces compiled/native/i386-linux/file.so. Evaluating (load/use-compiled "file.ss") in MzScheme will then load compiled/native/i386-linux/file.so instead of file.ss. If file.ss is changed without recreating file.so, then load/use-compiled loads file.ss, because file.so is out-of-date.