On 1/16/2014 12:09 PM, Bas de Bruijn wrote: > > One thing I experienced when I used a ~/linuxcnc-dev directory was > that the config I choose always pointed to the ~/linuxcnc directory, > no matter what I changed in the script when starting up, maybe it was > my inexperience at the time, but after rip-environment I could not > see the configs unless I put them in the ~/linuxcnc tree
At least a part of that is my fault. There are hard-coded paths in the configurations for some things like the PRU code and user-mode HAL components (the python script to read thermistor temperatures). Fixing this is a big part of the general cleanup I'm working on for the BeagleBone and PRU driver. -- Charles Steinkuehler char...@steinkuehler.net
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
