Module runtime 

Where the Chromium engine lives.

On Linux the engine — the tilo-chromium-host process and the Chromium Embedded Framework it loads — is its own signed Tilo runtime bundle, RUNTIME_REF. It is installed the way every runtime bundle is: by the image at /usr/lib/tilo-runtime/<version>, or for one user under the per-user runtime directory. An app that embeds the engine requires the bundle in its manifest ([package].optional-runtimes, the key of the runtimes an app requires): installing or updating the app installs it in the same step, and the launcher verifies the bundle’s signature, mounts it read-only at /run/tilo-runtime/<version> inside the app’s sandbox and refuses to start the app without it. Outside the launcher the installed bundle is used directly.

On macOS the packaged app carries the engine as a nested application in its Contents/Frameworks directory.

Under the launcher a missing engine means a broken install; outside it (a developer run) it is ordinary. Either way locate reports it as RuntimeMissing, which an app shows as NOT_INSTALLED_MESSAGE and logs with RuntimeMissing::developer_hint.

Structs

RuntimeMissing

No engine runtime was found in any place it is installed.

SearchRoots

The places the engine is looked for, in order.

Constants

FAILED_MESSAGE

What a person sees when an installed engine fails to start. The cause goes to the log.

HOST_IN_BUNDLE

The host executable, relative to the bundle root.

HOST_OVERRIDE_ENV

Names a host executable directly, for a developer running a locally built engine. Release images never set it.

MOUNT_ROOT

Where the launcher mounts runtime bundles inside an app’s sandbox.

NOT_INSTALLED_MESSAGE

What a person sees when the engine is missing. The app requires it, so this is a broken install: updating or reinstalling the app repairs it.

RUNTIME_DIR_ENV

Overrides the per-user runtime root, as it does for every runtime bundle.

RUNTIME_REF

The runtime reference an app that embeds the engine requires in its manifest’s [package].optional-runtimes.

RUNTIME_VERSION

The engine runtime’s version: the directory name of its bundle and of its mount. Bump it whenever the host’s protocol or its pinned CEF build changes. The apps that embed the engine require this version, so it installs and updates with them.

SYSTEM_ROOT

Where the image installs system runtime bundles.

Functions

locate

The engine host of the running process.