使用 Homebrew, apt, Nix, dnf, MacPorts, zypper 安装 omniorb

项目链接

• 主页

命令和别名

• catior
• convertior
• genior
• nameclt
• omkdepend
• omniMapper
• omniNames
• omnicpp
• omniidl
• omniidlrun.py

项目历史

The project history says omniORB began at Olivetti Research Ltd in Cambridge, whose lab later became Olivetti and Oracle Research Ltd and then AT&T Laboratories Cambridge in 1999. Development continued through those institutional changes, with multiple public releases, betas, and development snapshots.

A historical presentation by Duncan Grisby records early design details: omniORB was developed at ORL, originally targeted embedded platforms, omniORB 1 used Orbix's proprietary protocol, and omniORB 2 was designed for IIOP. The same material identifies omniORB 2.2 as a public release in May 1997.

On April 24, 2002, AT&T Laboratories Cambridge closed as part of AT&T's research cuts. omniORB then became an independent project, with original developers continuing involvement and SourceForge becoming the public project home.

采用历史

The official site says omniORB is used by many thousands of developers and deployed in countless applications. It also notes that omniORB was one of only three ORBs awarded the Open Group's Open Brand for CORBA, meaning it passed compliance testing for CORBA 2.1.

Its adoption persisted because CORBA users needed a robust free ORB with both C++ and Python mappings. Distro packages across Debian, Ubuntu, Fedora-family systems, MacPorts, Nix, openSUSE, and Homebrew reflect the long tail of CORBA systems that still need IDL compilers, naming services, and IIOP interoperability.

使用方式

Developers use omniidl to compile CORBA IDL into language bindings, run omniNames as the CORBA Naming Service, and use utilities such as catior, convertior, and genior when inspecting or constructing interoperable object references.

The runtime implements CORBA 2.6-era features such as C++ and Python language bindings, GIOP/IIOP protocol support, a multithreaded runtime, TypeCode and Any, DynAny, AMI, local interfaces, IPv6, dynamic invocation/skeleton interfaces, and a complete Naming Service.

为什么软件包爱好者会关心

omniORB is one of those packages that carries a whole distributed-systems era inside a formula. Installing it pulls in not just a library but an IDL toolchain, a naming service, and utilities for an interoperability model that predates REST and gRPC.

Its significance is also archival: it connects package managers to the Cambridge research-lab lineage that produced VNC and other infrastructure, then survived the lab closure as an independent open source project.

时间线

• May 1997: omniORB 2.2 is released to the public, according to historical project material.
• 1999: Olivetti Research's successor lab becomes AT&T Laboratories Cambridge.
• June 1999: omniORB documentation records Open Group CORBA branding for CORBA 2.1 compliance.
• April 24, 2002: AT&T Laboratories Cambridge closes and omniORB becomes independent.
• March 31, 2025: the official site announces omniORB 4.3.3 and omniORBpy 4.3.3.

Related projects

• omniORB is part of the CORBA ecosystem alongside commercial ORBs, TAO, MICO, ORBit, and language mappings such as omniORBpy. For package users, omniORBpy is especially important because it lets Python programs interoperate with C++ CORBA services through the same ORB family.

来源

• https://omniorb.sourceforge.io/
• https://omniorb.sourceforge.io/docs.html
• https://omniorb.sourceforge.io/features.html
• https://omniorb.sourceforge.io/history.html
• https://omniorb.sourceforge.io/omni42/omniORB.pdf
• https://omniorb.sourceforge.io/omnipy42/omniORBpy/omniORBpy001.html
• https://sourceforge.net/projects/omniorb/
• https://www.cl.cam.ac.uk/research/dtg/attarchive/omniORB/omniORBForm.html
• https://www.esrf.fr/conferences/Corba_Controls/PAPERS/grisby_orb.pdf