iTX TechnologiesMirai ecosystem

MCL Installer

An interactive command-line installer for downloading Java and MCL.

Legacy project
Concept illustration
Brand
iTX Technologies
Platforms / runtime
  • Windows
  • macOS
  • Linux
Technologies
  • Rust

About the project

MCL Installer combines environment checks, Java selection, and downloading MCL into an interactive command-line workflow. It is intended for users who have not yet prepared a runtime and would prefer guided setup, reducing the steps involved in finding downloads and arranging files manually.

The installer and MCL work at different stages. The installer prepares the runtime and loader files; MCL manages packages, updates, and startup afterward. Users with suitable Java already installed can skip the runtime download. Configuration of ongoing runtime behavior belongs in the MCL command-line documentation.

  1. Guided setup

    Follow prompts to optionally install Java and download MCL.

  2. Platform-specific releases

    Select the executable matching your operating system and architecture from the releases page.

Make setup choices step by step

The workflow displays the result of checking the existing Java installation, then asks whether to install Java and offers choices for its version, runtime or development kit, and processor architecture. It then reads package metadata and asks whether to download MCL from the stable channel. The defaults belong to the historical installer and should be checked against the target machine and loader requirements.

Work within the installation directory

The installer downloads and extracts files in its working directory. When Java is installed as well, it sets the Java path in the downloaded MCL startup script. Choosing to reinstall Java deletes and replaces the existing java folder there, so back up any files you need to keep first. The project is written in Rust and includes build instructions.

Choose the matching release asset

Choose a release asset for the operating system and architecture on GitHub Releases, then run it in the intended installation directory. Available assets determine actual coverage; cross-platform source does not mean every combination has a prebuilt binary. Setup also depends on network access, download services, and package metadata. If an old service is unavailable, the MCL documentation provides a manual installation path.