From lfs.mailing at leloft.co.uk  Thu Oct  8 10:40:03 2020
From: lfs.mailing at leloft.co.uk (fraser kendall)
Date: Thu, 8 Oct 2020 11:40:03 +0100
Subject: [qTox-dev] shared build
Message-ID: <20201008114003.27a1a620@bay6-hi5-1>

Hi Devs,

Please forgive this question if it is overly naive.  I am running qtox
on a number of machines (including two laptops) that run various
combinations of devuan ascii (debian oldstable)  beowulf (debian
stable), chimaera (debian testing) and beowulf/ceres (debian unstable
'sid') and chimaera/ceres hybrids with either linux-libre or native
devuan/debian kernels.  The text function never fails, but there is
patchiness with respect to the video calling.  Some combinations work,
some can't do sound, some cant do video, some can't find the webcam etc.
I am hoping to replace the use of Google Duo (which works on every
machine, every time) with the use of qtox, but until I can iron out
these discrepancies, I am stuck with Duo.  

To pin down the OS-specific issues, I would like to use the same
'master' build across all machines, held on an internal server and from
which I can download and deploy the same build on all machines.
However, I am having issues: Installing qtox from the debian/devuan
repos does not pull in the required (toxcore?) dependencies to support
the master build. So far, I am only able to get the master build to run
if I have previously built qtox on that machine. 

So my question is this:  Can I build the required toxcore elements into
the master build, so that I can bypass the need to install anything
qtox from the devuan/debian repos. I see that a mac build can be
shared like this.

Thank you for your time.  I would be happy to share any learned
information if it would assist you while you are stabilizing the
code.

fraser