trioalt.blogg.se - Ez7z output directory

Ez7z output directory install#

You can use Bazel's -output_base startup option to override the defaultīazel -output_base=/tmp/bazel/output build x/y:z.

home/user/src/my-project (or in a directory symlinked to that one), thenĪn output base directory is created called: So, for example, if Bazel is running in the workspace directory

Is also created whose name is the MD5 hash of the path name of the workspaceĭirectory. Beneath the outputUserRoot directory, an outputBase directory.It is an installBase directory whose name is the MD5 hash of the Bazel

Ez7z output directory install#

Beneath the outputUserRoot directory there is an install directory, and in.This is called the outputUserRoot directory. The Bazel user's build state is located beneath outputRoot/_bazel_$USER.If theĮnvironment variable $TEST_TMPDIR is set, as in a test of Bazel itself, SHGetKnownFolderPath() with the FOLDERID_Profile flag set. private/var/tmp on macOS, and on Windows it defaults to %HOME% if set,Įlse %USERPROFILE% if set, else the result of calling The outputRoot directory defaults to ~/.cache/bazel on Linux,." workspace directory"), or a subdirectory thereof. Bazel must be invoked from a directory containing a WORKSPACE file (the.The solution that's currently implemented: All the build state per user should be underneath one directory ("I'd like toĬlean all the.Is unambiguous, even if the user relies on symbolic links when changing into.Supports building for multiple target configurations in the same workspace.Supports building in multiple workspaces at the same time.

Doesn't collide if multiple users are building on the same box.

Requirements for an output directory layout: This page covers requirements and layout for output directories.