- Yosemite el capitan mac os sierra how to#
- Yosemite el capitan mac os sierra mac os x#
- Yosemite el capitan mac os sierra windows#
Launchctl setenv JAVA_HOME /usr/local/jdk1.7 Syslog -s -l warn "Set environment variables with /etc/environment $(whoami) - start"
r-xr-xr-x 1 root wheel 369 Oct 21 04:42 /etc/environment Main file with environment variables definition: $ ls -la /etc/environment
Yosemite el capitan mac os sierra mac os x#
It is possible to set environment variables on Mac OS X 10.10 Yosemite with 3 files + 2 commands. Additionally if you set variables in the terminal via ~/.profile or ~/.bash_profile, they will override things set via launchctl setenv for applications started from the shell. If you are having a problem, remember that you will need to restart applications for this to take effect. However I have tested on multiple Yosemite machines and it does work for me. : A user below mentions that this did not work for him. Granted, neither of these workarounds is as convenient as /etc/nf. If you do have multiple users you could either manually set a Login Item for each of them or place a copy of in each of their local Library/LaunchAgents directories, pointing at the same shell script. : Neither solution is perfect as the variables will only be set for that specific user but I am hoping/guessing that may be all you require. That way the the script will be invoked when the user logs in.
Yosemite el capitan mac os sierra how to#
: To work around this place all the variables you wish to define in a short shell script, then have a look at this previous answer about how to run a script on MacOS login. Finally open System Settings → Users & Groups → Login Items and add your new application. Now save ( ⌘+ s) as File format: Application. (Use multiple lines if you want to set multiple variables) : To avoid this, launch AppleScript Editor, enter a command like this: do shell script "launchctl setenv variablename value" Obviously you will not want to do this every time you login. : You can still use launchctl setenv variablename value to set a variable so that is picked up by all applications (graphical applications started via the Dock or Spotlight, in addition to those started via the terminal). That needs to be set via 'launchctl config user path. Finally, this doesn't seem to work for PATH on El Capitan and Sierra. Also, if you log in via ssh, the variables will not be set (so you'll need to set them in ~/.bash_profile).
Yosemite el capitan mac os sierra windows#
If the computer is restarted and "Reopen windows when logging back in" is selected, the reopened windows may not see the variables (Perhaps they are opened before the agent is run). There a couple of situations where this doesn't quite work. The old behaviour can be enabled with this command:ĭefaults write .Xcode UseSanitizedBuildSystemEnvironment -bool NO
Xcode 7.0+ doesn't evaluate environment variables by default. The same solution works in El Capitan too. You can also use launchctl load ~/Library/LaunchAgents/ist to launch it immediately. The plist will activate after system reboot. You can add many launchctl commands inside the block. Launchctl setenv PATH $PATH:/Applications/gradle/bin Launchctl setenv ANDROID_NDK_HOME /Applications/android-ndk Launchctl setenv PRODUCTS_PATH /Users/mortimer/Projects/my_products Create an ist file in ~/Library/LaunchAgents/ with this content:
0 kommentar(er)
