Probably, over Wheezy anyway.
The problem with czmq, was that they changed the API so that the
Machinekit code only worked with earlier versions.
We changed the code and Debian backported the czmq packages to Jessie
from Stretch,
which means that Jessie and Stretch are supported by Debian packages.
Wheezy is stuck with earlier packages and the old code.
This, plus the imminent 'end of life' is why Wheezy packages are no
longer being produced
On 01/12/2017 22:10, 'fishy' via Machinekit wrote:
Is jessie the best debian to use now?
I got the feeling that the czmq or zmq versions in 'configure;
autobuild were upgraded to require the stretch versions and it broke
back compatability with wheezy and jessie?
On Thursday, 30 November 2017 16:14:12 UTC, Schooner wrote:
On 30/11/17 14:23, Rob M wrote:
Schooner,
Cheers for your reply. Going by what you said maybe running on a
Jessie image maybe my best bet ?
Depends completely upon what you are trying to do.
The image is actually probably Wheezy.
So I managed to get a docker image to build machinekit packages
for jessie, so I guess that is a plus. This is the resource I
used https://github.com/Dovetail-Automata/mk-cross-builder
<https://github.com/Dovetail-Automata/mk-cross-builder> .
Yeah, that is what we use in the CI Builder
I guess now the best thing to do would be start running jessie,
install/upgrade machine with the packages built in the docker
container. With a large enough sd card I could install a build
enviroment and use that to build hidcomp on ?
I would be minded to fix hidcomp on the image you have first, then
look at upgrading the image to something else.
There are other problems with using Jessie and later kernels that
are best left until after this.
Trying to build anything natively on the BBB is a major pain, it
has the processing power of an 80's Casio watch. (minor exaggeration)
That is without the added problem of the Makefile.modinc from the
earlier -dev packages previously mentioned.
I would cross-build the altered Machinekit repo for Wheezy armhfÂ
and copy the relevant modules across to test them.
When that is proved, if it fits nicely with the rest of the repo,
it could be included and then you can just install the new
Machinekit packages onto whatever
platform you are using, but would need to see the code first.
I'm not looking to use the LCD portion so that's not a real issue
I'm guessing ?
I must admit I'm not a "debian guy" Slackware is more my cup of
tea. Would I be correct in guessing before I build the
binary-debs I should build a source package that I can decompress
later and use to build hidcomp against ?
I'm really appreciating your time.
Rob
--
website: http://www.machinekit.io blog: http://blog.machinekit.io
github: https://github.com/machinekit
---
You received this message because you are subscribed to the
Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to machinekit+...@googlegroups.com <javascript:>.
Visit this group at https://groups.google.com/group/machinekit
<https://groups.google.com/group/machinekit>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io
github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google
Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to machinekit+unsubscr...@googlegroups.com
<mailto:machinekit+unsubscr...@googlegroups.com>.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
