Skip to content

[FEAT] Publish manylinux aarch64 wheels to PyPI #127

@alibeyram

Description

@alibeyram

Feature Description

Summary

The rtms package currently only publishes Linux wheels for x86_64. There are no aarch64 (ARM64) wheels for Linux, which makes the package unusable on Linux ARM environments without emulation.

Current published wheels

Platform Architecture Available
Linux (manylinux) x86_64
macOS arm64
Linux (manylinux) aarch64

Problem

When running pip install rtms on a Linux aarch64 machine (e.g. Ubuntu on AWS Graviton, Docker on Apple M-series), pip returns:

ERROR: Could not find a version that satisfies the requirement rtms
ERROR: No matching distribution found for rtms

The macOS arm64 wheel cannot be used as a substitute — despite being the same CPU architecture, it is a different binary format (Mach-O vs ELF) and a different OS ABI.

Affected environments

  • Docker containers on Apple M1/M2/M3 Macs (very common dev environment)
  • AWS Graviton instances (EC2, ECS, Lambda)
  • Any Linux ARM64 server or CI runner

Expected behavior

pip install rtms should work on Linux aarch64 the same way it does on Linux x86_64.

Request

Please publish manylinux_2_34_aarch64 (or manylinux_2_28_aarch64) wheels to PyPI for all supported Python versions (3.10, 3.11, 3.12, 3.13). Tools like cibuildwheel make this straightforward to add to your existing CI/CD pipeline.

As a workaround, users currently have to use --platform linux/amd64 in Docker, which requires QEMU emulation and has a significant performance cost in production.

Use Case

This feature would allow developers to install and run the rtms SDK on Linux ARM64 environments — including Docker containers on Apple M-series Macs and AWS Graviton instances — without requiring x86_64 emulation via QEMU, enabling native-performance real-time media streaming pipelines on ARM-based infrastructure.

Affected Language Bindings

Python

Proposed Solution

No response

Implementation Considerations

No response

Alternatives Considered

No response

Additional Context

No response

Verification

  • I have searched existing issues to ensure this feature has not already been requested
  • This feature would benefit a significant portion of RTMS SDK users

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions