I do think that option number B is the best for moving forward with LinuxCNC. I spent some time cruising through configure.in and see where it checks for at least 2.7 or greater but the implicit check eludes me...
Option number A is the easy way out for sure for me to do but I'll keep looking at the configure.in for a while and see if it makes sense after a while... The GUI is Python with PyQt which seems to be easier to work with than PyGtk. Stuff doesn't have a mind of it's own in PyQt like PyGtk. Thanks JT On 2/8/2017 9:53 AM, Sebastian Kuzminsky wrote: > On 02/08/2017 05:36 AM, John Thornton wrote: >> When I build my branch it builds without any errors. The lhgui.py file >> gets the first line changed from: >> #! /usr/bin/env python3 >> to >> #!/usr/bin/python >> when it is copied to /bin. Which makes the program not work. I'm >> wondering if there is something in my Submakefile that is doing that? > All our existing python programs and libraries are for python2, and our > build system doesn't expect to have a different python interpreter involved. > > Our configure system (src/configure.in) currently requires that > /usr/bin/python (or whatever you specify with --with-python=) is at > least 2.7 (explicitly checked), and less than 3 (implicitly checked by > using python2 syntax in our checks). > > So i think your options are to either rewrite your gui for python2, or > rewrite our configure/build/package system to handle mixed > python2/python3 code. > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
