Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
jwittner opened this issue May 21, 2018 · 2 comments
Open

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

jwittner opened this issue May 21, 2018 · 2 comments
Labels
enhancement good first issue

Comments

@jwittner
Copy link
Member

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

This would make them discoverable in online build systems and leveraged appropriately.
@abhinuvpitale
Copy link

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

@jwittner
Copy link
Member Author

jwittner commented Oct 8, 2018 •
edited
Loading

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. =)!!!

abhinuvpitale added a commit to abhinuvpitale/unitysetup.powershell that referenced this issue Oct 8, 2018
@abhinuvpitale
add env variable for installer path for Unity microsoft#111
5b8da9c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement good first issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jwittner @abhinuvpitale