On Wed, Sep 11, 2013 at 04:08:18PM -0500, Charles Steinkuehler wrote: > I also wasn't aware the python code could be compiled like a > conventional HAL module. Pretty nifty! :)
Calling it "compiling" is a bit of a misnomer. Mostly that makefile fragment does two things: first, makes sure the file is valid python syntax. second, substitutes the right #!-line based on the version of Python selected at configure-time (almost always /usr/bin/python but some weirdo will come along with /usr/local/bin/python2) Jeff > On 9/11/2013 3:33 PM, Jeff Epler wrote: > > On Wed, Sep 11, 2013 at 03:14:17PM -0500, Charles Steinkuehler wrote: > >> Several of the listed files are from me. I can't push anything to the > >> LinuxCNC repository, but I'm willing to clean up my files and commit > >> them. I have a github clone of the LinuxCNC repository where I can push > >> changes to the ubc-3 branch and send a pull request, or would you prefer > >> a different work-flow? > >> > >> Alternately, I can push to my MachineKit branch (currently based off > >> ubc-2) and changes can be pulled into ubc-3. > > > > Unless Michael H. has a different opinion, I can accept your patches and > > push them onto the tip of the ubc branch. > > Thanks! Michael has said he'll deal with pulling the changes. > > >>> = configs/ARM/BeagleBone/BeBoPr-Bridge/dtc.sh and other new sh files > >>> > >>> Does not contain license declaration. Some appear to be duplicated in > >>> multiple > >>> directories; use our facility configs/common so that build process copies > >>> to > >>> each destination. Or put them in scripts/ if sensible. > >> > >> This is from me as well, I'll add a license header. > >> > >> I realize there is a fair amount of duplication of some files in the > >> BeagleBone config directories. I'm still working out how to put things > >> like python scripts and include files in common places that can be > >> referenced in HAL files. I am willing and anxious to get rid of the > >> duplication...I'm the one having to keep all the various files updated > >> and synchronized! :) > >> > >> All help and suggestions are greatly appreciated! Particularly with how > >> to put python based user-mode HAL components in a common location and > >> still be able to load them from a HAL file! > > > > If you put an executable file in scripts/, "halcmd loadusr" should find > > it. For shell scripts where "#!/bin/sh" will work on all systems, > > that's what I'd do. > > > > For Python scripts, put it in the source tree with or without a #!-line. > > Then you'll have to do some cut&paste in a Submakefile: > > Thanks! That looks like a big chunk of what I need! > > I'll see if I can work through the makefile changes. I have some > include files (things like thermistor settings) I'd like to extract out > of the existing python scripts, so I'll have to figure out include > > -- > Charles Steinkuehler > char...@steinkuehler.net > ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
