Figure it's too coincidental not to mention, but once you start considering overriding such settings, say in the cascading fashion of having children add or subtract environment settings or paths to executables from their parents, I just happen to be working on such a solution at the moment; I'm calling it Open Metadata <https://github.com/abstractfactory/openmetadata> and just made a 0.3 pre-release over at Github<https://github.com/abstractfactory/openmetadata/releases/tag/v0.3> and are focusing questions and answers in this Google Group<https://groups.google.com/forum/#!topic/open-metadata/JcWOZ95JYzc> .
On 7 April 2014 20:20, Marcus Ottosson <[email protected]> wrote: > +1 for modifying PATH to include the binary. > > Haven't come across a scenario this wouldn't work. E.g. when you've got > multiple binaries, such as Maya 2013, 2014 and 2015, you can substitute > directly calling the maya.exe with calling something like maya2013.bat and > maya2014.bat, each containing the full path to their respective executables. > > > On 7 April 2014 19:44, Jesse Kretschmer <[email protected]> wrote: > >> If you are running a background process for VRay rendering, you must also >> be somehow handling other VRay environment variables. These variables may >> be coming for *free* from the maya environment that spawned the background >> process. If that is the case, then you can also adjust the the PATH >> variable in the maya.env. >> >> I suggest that you set the PATH variable to include your vray bin >> directory, then simple call "vray.exe" without a full path. >> >> >> Side note: >> I've setup network installs of VRay on windows and bootstrapped the >> plugin loading with the userSetup.py. I like using python to manage the >> various plugin versions. In my case it also is setting the PATH variable >> such that I can simply call vray.exe directly from within maya using >> subprocess.Popen(["vray"]+args). >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CANESWi3sU-3BaHg%3DESC6Rh9EDMZPG3kSp5%3DPfg8i31tzUmkp0g%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CANESWi3sU-3BaHg%3DESC6Rh9EDMZPG3kSp5%3DPfg8i31tzUmkp0g%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > *Marcus Ottosson* > [email protected] > -- *Marcus Ottosson* [email protected] -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmODrYZyFYdifgZ6gdJTUgS8LbHw9ar4PJ%3Dcy7fGf_qQ6PQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
