OK, answered my own question. Looks like creating an environment.plist in ~/Library/LaunchAgents/ does the trick.
now another. do you all create an init.py and menu.py on each workstation? I tried creating a simlink to files on a central server, which seems to work, but not sure if there are downsides to that approach? Trying to keep the admin to a minimum. Thanks http://www.dowdandassociates.com/blog/content/howto-set-an-environment-variable-in-mac-os-x-launchd-plist/ Gary Jaeger / 650.728.7957 direct / 415.518.1419 mobile http://corestudio.com <http://corestudio.com/> > On Apr 24, 2017, at 3:58 PM, Gary Jaeger <[email protected]> wrote: > > Where is the current place to set env variables on the mac? Googling gives me > various answers, none of which I can really get to work. The latest (and what > the foundry docs say) seems to be launchd.conf, but for instance if I put > > setenv NUKE_PATH /Volumes/tools/nuke10_5 > setenv OFX_PLUGIN_PATH /Volumes/tools/nuke10_5/OFX > > they don't seem to get picked up > > also, what’s the difference between ‘setenv’ and ‘export’ ? > > thanks > > Gary Jaeger / 650.728.7957 direct / 415.518.1419 mobile > http://corestudio.com <http://corestudio.com/>
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
