Managing temporary files

eMake runs commands and collects output in parallel, but the results are written in order, serially. This feature ensures a build behaves exactly as if it were run locally. See Transactional Command Output.

The eMake temporary directory is used to store output files from commands (for example, object files) that finished running but are waiting their turn to be relocated to a final destination on disk. By default, eMake creates a temporary directory in the current working directory. The directory name will have the form:

ecloud_tmp_<pid>_<n> where pid is the eMake process identifier. where n is a counter assigned by eMake to differentiate multiple temporary directories created during a single build if you specify multiple directories.

eMake removes the temporary directory on exit (including the Ctrl-C user interrupt). If eMake is terminated unexpectedly (for example, by the operating system), the temporary directory might persist and need to be removed manually.

Important temporary directory requirements include:

You can use the --emake-tmpdir command-line option or the EMAKE_TMPDIR environment variable to change the temporary directory default location:

Files are relocated from the temporary directory to their final location. Keeping the temporary directory on the same file system as the EMAKE_ROOT helps performance because files can simply be renamed in place, instead of copied.

eMake and agent machines reset the values for TEMP, TMP, and TMPDIR. This is necessary to avoid possible conflicts with multiple build agents/jobs running on the same machine.

If you have more than one EMAKE_ROOT that spans multiple file systems, you can specify more than one temporary directory to ensure eMake can always rename files in place, instead of copying them.

For example, if your EMAKE_ROOT contains three directories:

that reside on two different file systems

to ensure better performance, specify two temporary directories—write permission at both locations is required:

When specifying multiple temporary directories, note the following:

During a build, eMake creates a temporary directory inside the directory specified by the EMAKE_TMPDIR environment variable or in the directory specified by the --emake-tmpdir command-line option (or the current working directory if no eMake temporary directory is specified). If a specified directory does not exist, eMake creates it. All temporary directories created by eMake are automatically deleted when a build completes.

For example, if you set your temporary directory to /foo/bar/baz and only /foo/bar exists, eMake creates /foo/bar/baz and /foo/bar/baz/ecloud_tmp_<pid>_<n>, and then deletes both directories and all their contents when it exits. If /foo/bar/baz exists at the start of the build, only /foo/bar/baz/ecloud_tmp_<pid>_<n> is created and deleted.

However, if the build is aborted in-progress, eMake will not have the opportunity to remove the temporary directory.

Subsequent eMake invocations automatically delete temporary directories if they are more than 24 hours old. You can reclaim disk space more quickly by deleting temporary directories and their contents by hand. However, do not delete the temporary directory while a build is in-progress —this action causes the build to fail.

Temporary directory names are in this form:

ecloud_tmp_<pid>_<n> where pid is the eMake process identifier. where n is a counter assigned by eMake to differentiate multiple temporary directories created during a single build if you specify multiple directories.