-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
Detect 2019 modules and allow to install 2019, skipping dmg install for now #392
Detect 2019 modules and allow to install 2019, skipping dmg install for now #392
Conversation
Thanks, yeah should be able to test it out in a few hours. |
Tried out the branch however there are a few issues still. In line 261 of If i change to So i guess the biggest question remaining is how to get the version number. |
Did a grep for it and only get binary files 😢
|
@lacostej I think that this is a solid alternative to the ivy file since it seems to be as present as it used to be so can rely on this. However, this is super lackluster and does not support a ton of the modules. For instance:
Many of those would not be covered by the So I think that if we want to address this issue correctly we need to tackle those as well. Languages could be fairly easy: |
@BastianBlokland Thanks a bunch for your help on this! I think that we shouldn't be too afraid of looking into binaries. We already do this for Windows to get the version number from the exe: Lines 327 to 362 in e980ddd
So I believe that we should try looking into this. |
Did some digging on the Unity executable, unfortunately all the occurrences seem to be in the
I guess those are all just constants they use in their source code:
Not sure how we would access those in any sane way. |
Kinda crazy but the Seems to be present across a bunch of unity versions and has the version number at a fixed offset into the file:
|
Any updates on this? |
got delayed, and January was mostly offtime. Resuming this now. |
acc6228
to
a6d6269
Compare
According to https://forum.unity.com/threads/manual-install-sdk-ndk-tools-in-unity-2019-1-0f2.663907/ NDK goes under PlaybackEngines as well. |
69fc3c2
to
20b780a
Compare
This doesn't solve the reinstalll of the modules yet, but it at least makes installing 2019 functional. Let's use it and release a new version with this, and I'll implement the #394 support after that. WDYT? |
In our case we are interested in the original purpose of this pull request: to be able to correctly detect the installed modules. We're wasting a lot of time doing unnecessary reinstallations through Jenkins. I agree with the approach as long as it does not take too long to solve the main problem. |
@bdominguez I heard you! Just a bit too tight for me to deal with this this week. It's next in pipeline. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nitpick, but it looks good if the objective is to bring things up for Unity 2019
deprecated = { | ||
PlaybackEngineUtils: IvyPlaybackEngineUtils, | ||
INIParser: INIModulesParser | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would move this out of the method, maybe to a constant like DEPRECATED_CLASSES or something
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do in a future cleanup.
Definitively WIP with Windows not supported at all.
The approach is to use the
modules.asset
files to detect Playback Engines. @niezbop any better idea on how to support this?I will also need some help to test this on Windows at some point. Maybe @BastianBlokland would like to test it on Linux?