unitysetup.powershell icon indicating copy to clipboard operation
unitysetup.powershell copied to clipboard

Installs should set path environment vars so capabilities can be detected.

Open jwittner opened this issue 7 years ago • 2 comments

Set/Remove environment variables, eg. {key:"UNITY_2017.4.2f2", value: ""}.

This would make them discoverable in online build systems and leveraged appropriately.

jwittner avatar May 21 '18 20:05 jwittner

Hey I am interested in contributing here, can you help me with this bug, tell me where to get started?

abhinuvpitale avatar Oct 03 '18 04:10 abhinuvpitale

Install-UnitySetupInstance starts here: https://github.com/Microsoft/unitysetup.powershell/blob/07042627b82c31631af8120b4cb62fb310063683/UnitySetup/UnitySetup.psm1#L414

It could write an env var, e.g. UNITY_<version> with the install path as the value.

Let me know if you have any questions about that code! Thanks for reaching out to get involved. =)!!!

jwittner avatar Oct 08 '18 20:10 jwittner