Re: [Machinekit] BeagleBone Black compiling hidcomp

[schoone...@btinternet.com]

On 30/11/17 02:05, Rob M wrote: Hi, Was wondering what would the procedure be to compile hidcomp http://hidcomp.sourceforge.net/ with this image that I am currently running, bone-debian-7.11-machinekit-armhf-2017-01-22-4gb.img.xz. There will probably be a problem compiling in-situ with that vintage image. An unforeseen consequence of the old build system, now fixed, was that in using posix to build the machinekit-dev package, it set the flavour to posix in Makefile.modinc irrespective of the running kernel flavour. I have the sources for both hidcomp ( pulled from https://github.com/ftkalcevic/hidcomp) and machinekit (pulled from github a couple of months ago) and with a few changes, just copying over the machinekit hal.h to the hidcomp source tree and adding a couple of defines I got it to compile and run on a x86 laptop with a RIP posix build. I use the laptop to test configs and such, easier than the BBB in the garage. If you push your working machinekit tree up to Github and send me a link, I will build it for armhf (Jessie?) and send you the binaries to add to your image and test. There may be merit in adding it to the machinekit repo and supporting it in packages hereafter, but will need to see the code. Rather looks from the wiki as if changes which might not be wanted are required. [ http://hidcomp.sourceforge.net/ ] The other potential issue is that your image is very old and pre a lot of hal changes If you have run it on x86 with a few month old machinekit pull, it probably is not an issue, but need to check I've lashed up a test device on a sparkfun ProMicro using the LUFA libs and I can talk to the deivce using both halinput & hidcomp. The reason I would like to use hidcomp is to be able to have more than 11 leds (linux kernel limit with the input subsystem for keyboard LEDs). The reason for this avenue is to be able to have a hardware control panel for some basic switches & indicators. As it is halinput is ok with the ProMirco, but eventually I would like to use a teensy for a bit more I\O. If a docker container is the go for cross compiling, is anyone able to supply some step by step instructions (really simple ones).....I had a go last night had some issues. Or should I just burn the image I have to a SD card, download all the required tools & libs to build, and go from there. Or........does anyone have some pointers to using python and pysub, if this is a viable option ? Thanks 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+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.