Open TheKnarf opened 3 years ago
I personally use a combination of uvm detect
with the flags -fr
to find the project version in sub directories (depending on your repo structure. I normally have the Unity project not in root).
uvm launch
has the -f, --force-project-version
flag with the combination of r, --recursive
works the same.
But there is room for adjustemts. I didn't work yet on that front because I use gradle for all that and have a custom JNI wrapper and plugins to build with unity etc.
https://github.com/wooga/atlas-unity https://github.com/wooga/atlas-unity-version-manager
With some settings which are sadly not yet fully documented gradle can figure out what Unity version is needed and install it before invoking whatever batchmode command was requested.
I like the init idea. What about additional modules (ios, android, etc). That would be also in this .uvm file? I think about it.
Btw. Uvm supports alias commands like git. So any executable starting with uvm- can be called. So for a custom init command just create a script or similar named uvm-init and make sure it is in PATH.
I'd like to commit a file to my git repo containing what version of Unity the project uses so that its clear.
Does
uvm
have some kind of project or settings file where it can specify it?I'd love some kind of
uvm init
command that I can run in a new git repo that would initialise a new Unity project and save what version of Unity is used in the repo.