Thanks for all of your suggestions. linuxcnc_var sounds quite handy. Thanks. It looks like I'll have to build a test version of my comms module under every version that I need to support and check the size of emcStatus for each one. That way I can work out how many versions I need to distribute. Hopefully I can write a script using linuxcnc_var to decide which version of my comms module to run.
Looking to the future hopefully I can add it to the LinuxCNC source so I won't have these issues with later versions of LCNC. The code that connects to LCNC is GPL and the comms library will be LGPL or a more permissive license. Les On 21/12/16 15:32, Dewey Garrett wrote: > The included script linuxcnc_var might be helpful: > > ------------------------------------------------------------ > $ linuxcnc_var > Retrieve Linuxcnc Variables > Usage: > linuxcnc_var [ varname | all ] > Varnames supported: > LINUXCNCVERSION > REALTIME > RTS > HALLIB_DIR > Option 'all' returns varname=value for all supported varnames > > ------------------------------------------------------------ > For remote to a host named t520 with a deb install > (setup authorized keys first for automatic login): > > $ ssh t520 linuxcnc_var LINUXCNCVERSION > 2.8.0~pre1 > > ------------------------------------------------------------ > When using a RIP, source rip-environment (in RIP root_dir/scripts) > first: > > $ ssh t520 source /home/git/linuxcnc-dev/scripts/rip-environment; > linuxcnc_var LINUXCNCVERSION > 2.8.0~pre1 > ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
