First, we probably should get out of the habit of using EMC2 for
variables and stuff to comply with the name change.
Secondly, why would the environmental variables not work outside of
python? You can use something like:
int main ()
{
char* lPath;
lPath = getenv ("LCNC_HOME");
if (lPath!=NULL)
printf ("Linux CNC's path is: %s",lPath);
return 0;
}
provided it is set in in the users or systems env. If it is in a .ini,
then you can use a C compliant parser. If this does not work for the
situation please explain and we will see if we can find a workaround.
EBo --
On Dec 10 2013 10:46 AM, Michael Haberler wrote:
> I note that two master commits recently appeared by Jeff and Dewey,
> providing and using a new feature of the linuxcnc module, namely
> carrying the EMC2_HOME pathname
>
> that's certainly useful for Python code using this module, but
> unfortunately not applicable beyond
>
> also, ubc3 already has a more general mechanism for some time, the
> linuxcncconfig.py module which is autogenerated by configure but not
> tied to the use of the linuxcnc module:
>
>
> https://github.com/mhaberler/linuxcnc/blob/32e92ac1377b0be7d092bdb5a717812416aec92d/src/linuxcncconfig.py-tmp.in
>
>
> please suggest a way how to get rid of this feature overlap
> downstream
>
> - Michael
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
