Timeline for Setting enivorment variables permanently with a .sh
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 2, 2021 at 15:44 | vote | accept | Jonathan Woollett-light | ||
Apr 2, 2021 at 1:40 | history | became hot network question | |||
Apr 1, 2021 at 22:11 | answer | added | Ken Jackson | timeline score: 1 | |
Apr 1, 2021 at 18:00 | comment | added | terdon♦ |
The other way around, actually. . is the command, so you would want . /path/to/dir/setup-env.sh .
|
|
Apr 1, 2021 at 18:00 | answer | added | terdon♦ | timeline score: 4 | |
Apr 1, 2021 at 17:42 | comment | added | Jonathan Woollett-light |
@glennjackman In that case the line would be /path/to/dir . setup-env.sh right?
|
|
Apr 1, 2021 at 17:41 | comment | added | Jonathan Woollett-light |
@Pourko This just copy and paste of the setup-env.sh from the Vulkan SDK linux version ( vulkan.lunarg.com/sdk/home#linux).
|
|
Apr 1, 2021 at 17:36 | comment | added | Pourko | Just curious, what exactly have you copyrighted there? | |
Apr 1, 2021 at 17:34 | comment | added | glenn jackman |
You could put . setup-env.sh in your ~/.bashrc or ~/.bash_profile or ~/.profile
|
|
Apr 1, 2021 at 17:28 | review | First posts | |||
Apr 3, 2021 at 19:06 | |||||
Apr 1, 2021 at 17:22 | history | asked | Jonathan Woollett-light | CC BY-SA 4.0 |