ADD_ENV_VARIABLE.cmd assumes My Documents location
dustdustinthewind opened this issue · comments
I have My Documents set up to be on my F: drive, rather than the windows-install C: drive.
set SDKPATH="%userprofile%\Documents\PlaydateSDK on line 3 of ADD_ENV_VARIABLE.cmd does not grab the right documents in my case, it's looking for C:[user]\Documents instead of F:My Documents
The PlaydateSDK installation used the correct location, the F: location. The mismatch between Playdate and this program means invalid locations are being used for the env vars for users like me, causing errors when building.
The documents address to use instead can be found here (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders name: Personal).
Replacing line 3 with my location and re-running the program didn't fix the issue for me. I got a different error from powershell about the address I gave it (idk if being on a different drive has anything to do with it). Re-running the program also kept adding to the Path env variable, it doesn't check for dupes it seems.
I did the following to fix the variables instead. For users in my situation here's how you fix the bad paths:
Copy your Playdate SDK folder address. ( "...\PlaydateSDK" )
Go to start menu, search for "Environment Variable" click on "Edit the system environment variables"
Click on "Environment Variables..."
Look under "System variables" for "PLAYDATE_SDK_PATH" and click it. Then click "Edit"
Replace the "Variable value" with the Playdate SDK folder address you copied earlier. Click "OK"
Under "System variables" again, look for "Path". Click "Edit"
Replace any and all instances of the bad Playdate SDK address with the SDK folder address you copied earlier BUT add "\bin" to the end ( "...\PlaydateSDK\bin" ).
Click OKs until you're out. Try building again.
Yes, .cmd file don't rewrite envvar for PATH if it already exist, but PLAYDATE_SDK_PATH var should be rewritten.
Maybe your problem was missing / in F:/My Documents?
I'll look into link you provided and will try to find a solution. Thank you for the issue.
Not exactly the same issue but still related to the "ADD_ENV_VARIABLE.cmd" file. When running it, an error would come up on the SETX usage saying: "Invalid syntax. Default option is not allowed more than '2' time(s)." My SDK installation is the default one in the C drive so not sure why it was failing but I was able to unblock myself by following @FlyingRabidUnicornPig suggestion of in my case adding the environment variables manually as I had none set.
@FlyingRabidUnicornPig @samuelalmeidadev
Try latest version please