I'll admit on my Mac laptop I do it the easy, not that versatile way and just do this in my login .bash_profile, using 'export' for setting environment variables and also setting up an alias to launch Nuke from a shell. This is how it's described in the Nuke docs. If you want the variables to stick you can't launch Nuke from the Finder this way though, hence the app alias - and it'll only work for that user login.
On 24 April 2017 at 18:58, Gary Jaeger <g...@corestudio.com> 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 <(650)%20728-7957> direct / 415.518.1419 > <(415)%20518-1419> mobile > http://corestudio.com > > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
