I think it's sorted now.
I did a dist-upgrade and I've got a comp command in the path now:
/usr/bin/comp, owned by the machinekit-xenomai package. I'm not sure
what was wrong previously, but I think I got confused chasing the
red-herring of a missing machinekit-dev package which I didn't need,
wh
Just checked, the comp binary and includes etc are in the
machinekit- not the main one.
It was a while back, forgot which.
The Makefile.inc etc are per flavour, to stop the problems we had with
machinekit-dev always having a posix flavour
because of the build setup for that package.
On 11/08
I've got the latest machinekit package installed, but I don't see a
comp command. There's an instcomp binary, but it doesn't like the two
*.comp files I'm trying to compile, reporting:
machinekit@beaglebone:~/embedded/beaglebone$
EXTRA_LDFLAGS="-lprussdrv" instcomp --compile raster.comp
Error: Un
HI Charles
Yes Comp, plus headers, Makefile.inc and everything else in the -dev
package was moved into the main machinekit package some time ago.
There are only four machinekit-dev packages left in the repo and they
match the also deprecated wheezy and raspian packages in the repo,
which a
I'm trying to migrate to a fresh install on a BBB and am having
problems building some custom hal components. The first problem is
the comp command is missing, so I figure I'll just install
machinekit-dev package. But apt-get complains about broken packages
and how I need a different version of t
