|
On 30/11/17 14:23, Rob M wrote:
Depends completely upon what you are trying to do. The image is actually probably Wheezy.
Yeah, that is what we use in the CI Builder
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.
-- 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 [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. |
- [Machinekit] BeagleBone Black compiling hidcomp Rob M
- Re: [Machinekit] BeagleBone Black compiling... [email protected]
- [Machinekit] Re: BeagleBone Black compiling... Rob M
- Re: [Machinekit] Re: BeagleBone Black c... [email protected]
- Re: [Machinekit] Re: BeagleBone Bla... 'fishy' via Machinekit
- [Machinekit] Re: BeagleBone Black compiling... Rob M
- [Machinekit] Re: BeagleBone Black compiling... Rob M
- [Machinekit] Re: BeagleBone Black compiling... Rob M
