One of the knock-ons from splitting the CNC stack and putting the VCP elements into it.
The latency-test requires pyvcp, linuxcnc.so etc. which are part of the _emc/userintf/axis build which is now in machinekit-cnc.
I can see arguments to do this the other way, but that would probably move a whole lot of other stuff into machinekit-hal which is really CNC GUI related and may leave the requirement to import even more from a machinekit-hal build, before machinekit-cnc could be built into a package.
One of the knock-ons from splitting the CNC stack and putting the VCP elements into it. The latency-test requires pyvcp, linuxcnc.so etc. which are part of the _emc/userintf/axis build which is now in machinekit-cnc.
I can see arguments to do this the other way, but that would probably move a whole lot of other stuff into machinekit-hal which is really CNC GUI related and may leave the requirement to import even more from a machinekit-hal build, before machinekit-cnc could be built into a package.
It can be easily reversed if necessary.