Install ice with Homebrew, MacPorts

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• dsnode
• glacier2router
• ice2slice
• icebox
• iceboxadmin
• icebridge
• icegridadmin
• icegriddb
• icegridnode
• icegridregistry
• icestormadmin
• icestormdb
• slice2cpp
• slice2php
• slice2py

Project history

ZeroC documentation from the 3.1 era already describes Ice as the Internet Communications Engine, with Slice, language mappings, services, and a comparison with CORBA. That lineage matters: Ice came from the same problem space as CORBA and DCOM, but packaged an IDL-driven RPC system with a smaller, implementation-centered developer workflow.

The project evolved into a multi-language framework with a uniform API, compact binary RPC protocol, generated language bindings, and bundled services such as IceGrid, Glacier2, IceBridge, and IceStorm. ZeroC distributes the same source under GPLv2 or commercial licensing, which helped it occupy both open-source package repositories and proprietary distributed-application deployments.

Adoption history

Ice appears across language ecosystems and system package managers because it is not only a library: it ships compilers such as slice2cpp, slice2py, and slice2php, plus service daemons and administration tools. ZeroC's downloads page lists C++, C#, Java, JavaScript, MATLAB, Objective-C, PHP, Python, Ruby, and Swift entry points, which explains why a single package can serve heterogeneous client/server deployments.

The Homebrew formula sits alongside MacPorts and other packages as a convenient way for developers to install the middleware tools locally, especially when they need Slice compilation or to run IceGrid and IceStorm utilities during development.

How it is used

Users generally install Ice to compile Slice definitions, generate stubs, run service components, or test distributed applications locally. The installed executables include administrative tools for IceGrid and IceStorm, service daemons, database helpers, and language-specific Slice compilers.

In package-manager culture, Ice is one of the heavier RPC formulae: it is closer to installing a complete distributed-object environment than adding a single CLI.

Why package nerds care

Ice is significant because it preserves the classic IDL-plus-runtime model in a package-manager-friendly form. Installing it with Homebrew gives developers an immediately usable cross-language RPC toolchain, including compilers and service processes that would otherwise require a larger manual SDK setup.

It is also easy to confuse ZeroC Ice's IceStorm service with Project IceStorm for iCE40 FPGAs; the shared name makes the package namespace around `ice*` tools unusually dense.

Timeline

• 2003: ZeroC documentation describes the Internet Communications Engine as a distributed programming system.
• 2006: Ice 3.1-era manuals document Ruby preview support and the broader Ice architecture.
• 2015: ZeroC source history moved to the public GitHub repository era.
• 2026: ZeroC download metadata lists Ice 3.7.11 and links official source from GitHub.

Related projects

• IceStorm is ZeroC Ice's pub/sub service and ships with tools such as icestormadmin and icestormdb.
• IceGrid, Glacier2, IceBridge, and DataStorm are related ZeroC services or frameworks in the same distributed-systems family.
• IceRPC is ZeroC's newer RPC framework, but the Homebrew `ice` formula refers to the classic Ice framework.

Sources

• https://download.zeroc.com/Ice/3.1/IceRuby-3.1.1.pdf
• https://formulae.brew.sh/formula/ice
• https://github.com/zeroc-ice/ice
• https://www.zeroc.com/ice
• https://www.zeroc.com/ice/downloads/3.7