Missing emccannon and interpreter python modules?
10 Jun 2023 16:52 #273276
by drose
Missing emccannon and interpreter python modules? was created by drose
Hi,
I'm currently trying to piece together the different python modules that interact directly with linuxcnc. From what perusing around I've found that the following python modules get directly compiled from source:
From what I understanding the core modules for talking to linuxcnc are:
linuxcnc.so -> Allows access to interpreter through NML messages
_hal.so -> Used with wrapper hal.py to access hal (pins, components, ect...)
gcode.so -> Parse gcode? (Not sure what this is used for in a GUI yet)
On top of these three I've also seen the emccannon and interpreter modules mentioned in the documentation here: linuxcnc.org/docs/html/remap/remap.html
But I don't see these modules being built into .so objects when compiling. On top of this I don't seem them anywhere in the submakefile under rs274ngc/ except being listed as source files.
How do these modules get built? Am I missing something?
Also how do these modules differ from the linuxcnc and gcode modules?
I'm trying to get a better understanding of how linuxcnc works by playing around with the python exports from the source code.
I'm currently trying to piece together the different python modules that interact directly with linuxcnc. From what perusing around I've found that the following python modules get directly compiled from source:
~@fa089c591b06 /o/l/l/python> find . -name "*.so"
./_togl.so
./lineardeltakins.so
./_hal.so
./rotarydeltakins.so
./linuxcnc.so
./gcode.so
From what I understanding the core modules for talking to linuxcnc are:
linuxcnc.so -> Allows access to interpreter through NML messages
_hal.so -> Used with wrapper hal.py to access hal (pins, components, ect...)
gcode.so -> Parse gcode? (Not sure what this is used for in a GUI yet)
On top of these three I've also seen the emccannon and interpreter modules mentioned in the documentation here: linuxcnc.org/docs/html/remap/remap.html
But I don't see these modules being built into .so objects when compiling. On top of this I don't seem them anywhere in the submakefile under rs274ngc/ except being listed as source files.
How do these modules get built? Am I missing something?
Also how do these modules differ from the linuxcnc and gcode modules?
I'm trying to get a better understanding of how linuxcnc works by playing around with the python exports from the source code.
Please Log in or Create an account to join the conversation.
11 Jun 2023 21:12 #273351
by cmorley
Replied by cmorley on topic Missing emccannon and interpreter python modules?
For remap, there is a python interpreter embedded and invoked from the C (++?) code.
These are module that give the embedded python access to linuxcnc's internals.
This is a completely different interpreter that is used for GUI code.
These are module that give the embedded python access to linuxcnc's internals.
This is a completely different interpreter that is used for GUI code.
Please Log in or Create an account to join the conversation.
12 Jun 2023 16:34 #273401
by drose
Replied by drose on topic Missing emccannon and interpreter python modules?
Ok, do these both talk to the internals via NML channels? Also any clue why those two python modules are not built on compile?
Please Log in or Create an account to join the conversation.
12 Jun 2023 22:02 #273423
by rodw
Replied by rodw on topic Missing emccannon and interpreter python modules?
read these docs
linuxcnc.org/docs/2.9/html/code/code-notes.html
the folders under /src/emc contain submake files which are called from the main make files
linuxcnc.org/docs/2.9/html/code/code-notes.html
the folders under /src/emc contain submake files which are called from the main make files
Please Log in or Create an account to join the conversation.
Time to create page: 0.124 seconds