FWIW I have tried the /configs/sim/axis/qtvcp/qtvcp_tabs sample on a 64bit Pi4
and it works.
raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 11 (bullseye)
Release:11
Codename: bullseye
raspberrypi:~ $ uname -a
Hi Gene.
I actually see no apparent show stoppers.
The Desktop Notify error is weird but seems to not stop anything.
It just seems not to embed.
Could your try the sim sim/axis/qtvcp/qtvcp_tabs sample.
It should embed a cam window too.
also is the new tab window completely plain or is there
Gretibgs all;
I se some debugging has been turned on so it not a showstopper on my g0704.
The camera tab is created, but empty.
The terminal its launched from now contains some debugging info that may
be useful:
halcmd loadusr -Wn qtvcp_embed qtvcp -d -c qtvcp_embed -x {XID} cam_align
Buildbot is not really useful in terms of testing the Debian build until
such times as it can build it on the target OS platform. If that's a
requirement, then the focus should be on buildbot upgrades.
I think back and we had a stretch distro well before stretch was the stable
debian release. It's
I'm not sure you could say it adds _no_ value - the code is compiled and tested
by the buildbot.
Just not on the target you wish yet. - not perfect but still lots of goodness.
I personally don't see how we could have a good release candidate anywhere soon
(depends what you mean soon of course -
What has been overlooked so far is that there is still no buildbot version
for 2.9 on Bullseye so its increasingly difficult to deploy Linuxcnc on
newer hardware that requires say 5.10 kernel and higher. Buildbot is a long
way behind current kernel versions.
It's all very fine to support older
Thank you for the explanation.
It sounds to me we will likely/potentially have 3 or 4 versions to maintain.
buildbot debs release version (for early bugfix users)
Debian version that may or may not be up to date with the buildbot.
Master version for development and traditionally daily use by early
On 9/4/22 10:36, Sebastian Kuzminsky wrote:
There are currently four ways to get pre-built debs of linuxcnc:
1. debian.org
2. buildbot
3. www.linuxcnc.org
4. github "artifacts"
I forgot to mention another important difference between the debian.org
debs and the buildbot debs:
The
On 9/3/22 23:53, Chris Morley wrote:
I see the action with Debian package.
I hope that gets us some more exposure and more develops/users.
Me too!
I did wonder what that means for the project as far as maintaining versions.
How are bug fixes addressed with Debian packages after (Debian)
Personally, I think it makes sense that when V2.9 becomes the release
version (eg replacing V2.8), V2.9 is pushed to the Debian version and
master branch will need to be built from source. Only bug fixes to the
released version would then be sent to Debian until lcnc releases a new
version.
It
10 matches
Mail list logo
