Any plan for linux SDK

Feature Requests
21

@josh21
Tai-Lin Chu found that Zoom SDK version 5.4 worked better than 5.5 running in WINE.
He used this Dockerfile:

FROM i386/debian:sid

RUN \
  dpkg --add-architecture i386 \
  && apt-get update \
  && apt-get install -y wget gnupg2 \
  && wget -nc https://dl.winehq.org/wine-builds/winehq.key \
  && apt-key add winehq.key \
  && echo "deb https://dl.winehq.org/wine-builds/debian/ buster main" > /etc/apt/sources.list.d/winehq.list \
  && apt-get update \
  && apt-get install -y --install-recommends winehq-devel \
  && rm -rf /var/lib/apt/lists/*

Inside the container, I started the app something like this:

export WINEARCH="win32"
export WINEPATH="/zoom-sdk-windows/bin"
apt-get install xvfb
Xvfb :0 -screen 0 1024x768x16 &
DISPLAY=:0.0 wine ./your-app.exe

I have since abandoned this prototype, so I can’t say more about it.

22

Chromium (Electron) would be preferred as it is

  1. To much a hassle to make sure it works on each version of linux including future linux versions.
  2. Electron awesome
23

We have a large client who is pushing us to bring Zoom on our SironaTV devices which embedded Linux built using Yocto based IOT devices and uses a chromium browser.

Using WebRTC video and Audio tools like here we see our camera and our microphones on this link.

However when we do join.zoom.us we do not see the microphone and camera devices which the above link sees. We also get logs like these from chromium:

Failed to query video capabilities: Inappropriate ioctl for device
[ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type

Integrating Zoom with chromium opens doors of Zoom into the IOT world - which is substantial!

Answering about questions:

We prefer chromium as all our apps are built on Chromium thus a native Linux app will be difficult to manage. Our solution is based on a TV hence we only have a remote control to navigate.

24

Zoom has released Linux meeting SDK