Skip to content

Improve windows module installer support #111

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

Merged
merged 1 commit into from
Oct 30, 2019

Conversation

Larusso
Copy link
Owner

@Larusso Larusso commented Oct 30, 2019

Description

Third patch to gain Unity Hub parity for module installation. For windows it was necessary to implement other changes first to get to the point to safely implement the missing installer types.
This patch adds the missing installer types:

  • zip
  • po
  • msi

Zip

Zip is used as for all other platforms. It invokes the shared cross platform implementation.

MSI

The msi installer is tricky. It seems to be used only by Facebook Gameroom. It seems Unity Hub expects a specigic cmd string to replace the installer path. I use the same trick as used with the exe installers by creating a temp cmd script which invokes the installer comand. At one point it might be worth investigating in a CommandExt to call the windows process in the correct way.

Changes

ADD WINDOWS zip module installer support
ADD WINDOWS msi module installer support
ADD WINDOWS po language files installer support
CHANGE WINDOWS installer API and support optional cmd string

Description
===========

Third patch to gaiin Unity Hub parity for module installation.
For windows it was necessary to implement other changes first to get to
the point to savely implement the missing installer types.
This patch adds the missing installer types:

* zip
* po
* msi

Zip
---

Zip is used as for all other platforms. It invokes the shared cross
platform implementation.

MSI
---

The `msi` installer is tricky. It seems to be used only by `Facebook
Gameroom`. It seems Unity Hub expects a specigic `cmd` string to replace
the installer path. I use the same trick as used with the `exe`
installers by creating a temp `cmd` script which invokes the installer
comand. At one point it might be worth investigating in a `CommandExt`
to call the windows process in the correct way.

Changes
=======

![ADD] ![WINDOWS] `zip` module installer support
![ADD] ![WINDOWS] `msi` module installer support
![ADD] ![WINDOWS] `po` language files installer support
![CHANGE] ![WINDOWS] installer API and support optional `cmd` string
@Larusso Larusso added this to the Unity Hub install parity milestone Oct 30, 2019
@Larusso Larusso merged commit b1545cb into master Oct 30, 2019
@Larusso Larusso deleted the improve/windows_installer_support branch October 30, 2019 10:02
@Larusso Larusso self-assigned this Oct 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant