Install eiffelstudio with Homebrew, MacPorts, pacman

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• compile_all
• ecb
• estudio
• finish_freezing
• iron
• syntax_updater
• vision2_demo

Project history

Eiffel Software describes itself as recognized since 1985 for making software projects predictable and controllable, with EiffelStudio as its flagship IDE. The EiffelStudio documentation presents the tool as the interactive development environment for Eiffel, including an IDE, compiler, debugger, project settings, command-line compiler, and release notes.

The public source history is unusual by modern GitHub standards. The EiffelStudio README states that the main public source repository is an official Subversion repository at svn.eiffel.com, while the GitHub repository is a mirror of trunk. That makes EiffelStudio a packaged survivor of an older vendor-hosted source-control era rather than a GitHub-native project.

The documentation tree preserves long release-note and compiler-history chains, including EiffelStudio 5.x, 6.x, 7.x, and year-based releases through the 2010s and 2020s. This gives packagers a rare long-lived IDE/compiler stack with decades of compatibility decisions embedded in its release history.

Adoption history

EiffelStudio adoption is tied to Eiffel's niche but durable community: universities, long-lived industrial systems, and developers interested in Design by Contract, void-safety, and strongly specified object-oriented programming. It is not a mass-market compiler package, but it matters to users who need the canonical Eiffel implementation.

The input package metadata lists Homebrew, MacPorts, and Nix coverage, which reflects the practical need to keep the toolchain available on developer machines even as the wider programming-language ecosystem moved toward package managers and language servers.

How it is used

Users create or open Eiffel projects, edit classes, compile through the graphical IDE or command-line compiler, debug applications, inspect metrics, and manage project settings stored in Eiffel configuration files. Homebrew exposes both GUI and CLI-oriented executables such as estudio, ec, ecb, iron, compile_all, and finish_freezing.

EiffelStudio also anchors Eiffel's project format. The `*.ecf` Eiffel Configuration File is package-relevant because it is the metadata file that tells the compiler how to build a system, much like a project file in other compiled-language toolchains.

Why package nerds care

EiffelStudio is package-nerd significant because it is a full language distribution rather than a single CLI: compiler, IDE, libraries, project metadata, code generation, and platform-specific integration all move together. That makes it a heavier formula than most modern Go or Rust binaries.

It also illustrates how package managers preserve minority programming-language ecosystems. Even if Eiffel is niche, Homebrew and peers keep a reproducible path to the canonical toolchain, and that is exactly the sort of long-tail utility package indexes are good at.

Timeline

• 1985: Eiffel Software traces its recognition in Eiffel tooling and methods to this period.
• 2000s: EiffelStudio 5.x and 6.x release-note histories appear in the official documentation tree.
• 2010s: The documentation records EiffelStudio 7.x and year-based releases such as 13.11, 14.05, 15.x, and later.
• 2016-06-12: The official GitHub mirror is created.
• 2026-01-20: Eiffel.org documentation metadata shows the EiffelStudio documentation page updated.

Related projects

• The Eiffel programming language and Design by Contract method are the central context for EiffelStudio.
• ISE Eiffel is the historical naming lineage visible in compiler-history pages.
• The Eiffel libraries and Iron package tooling are related parts of the broader Eiffel ecosystem.

Sources

• https://www.eiffel.com/company/about-us/
• https://www.eiffel.org/doc/eiffelstudio
• https://github.com/EiffelSoftware/EiffelStudio#readme
• https://github.com/EiffelSoftware/EiffelStudio