Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
2.8.0-rc5
-
None
-
Windows 2012 on AWS, 64-bit
-
Needed
Description
Running set_gopath.bat from the Windows PowerShell doesn't actually set the environment variables.
Apparently, while Command Prompt uses set to set environment variables, you need to use $Env:<Varname> = foo to set it in PowerShell.
I realize PowerShell is no one's favorite thing, but it still seems like a bug.
Attachments
Issue Links
- is documented by
-
DOCS-4591 Update build tools doc with Windows instructions
-
- Closed
-