mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-10-14 19:27:09 -04:00
The412BannerandThe412Banner
08559a02f8
* Windows components: install .msi packages (XNA, PhysX, GFWL, MSXML...) without running them
droiddeck-msi-install reads a Windows Installer package's tables with msiinfo and unpacks its
cabinets with cabextract, then lays out what Wine's msiexec would have installed: files at their
64-bit Windows paths (Program Files (x86), syswow64...), .NET assemblies in the GAC, side-by-side
assemblies in winsxs, and the registry values in the view the component writes through. Conditions,
features and the folder-setting custom actions are evaluated as on Windows 10 64-bit; what needs
the package's own code (DXSETUP, self-registration) is listed in the component's notes.
droiddeck-wincomponents puts a component's drive_c tree into the prefix (keeping the prefix's own
spelling of each folder) and writes its registry values into system.reg/user.reg before launch,
following Wine's link keys (Wow6432Node\Classes, CurrentControlSet...). Turning it off puts every
value back and takes an added PATH entry out again.
The app installs these from the Windows components menu like the DLL ones: it downloads the .msi
into the runtime and runs the installer there (GuestCommand). msitools 0.106 and cabextract 1.11
come from Arch Linux ARM, pinned in tools/msitools/packages.txt and hosted on the msitools-0.106-r1
release. wine-gecko stays hidden (Proton ships it) and wine-mono keeps waiting (uninstall step).
* Windows components: open with the top switch focused, by touch or by pad
The dialog's window starts in touch mode, where a switch cannot take focus, and the first switch
was asked once, two frames after the list loaded, only when a pad opened it - racing the dialog's
own Done focus. Now it always puts the window in pad mode, holds Done while the list loads and
then asks the top switch every frame until it has focus.
* Windows components: give msitools its own libraries; show a failed install on its row
msiinfo and cabextract sit with their libraries in /usr/local/lib/droiddeck-msitools, which the
loader does not search: every .msi install stopped at "libmsi-1.0.so.0: cannot open shared
object file". droiddeck-msi-install now runs them with that folder on LD_LIBRARY_PATH.
A failed install also says so under the component itself ("Could not install: ..."), not
only at the foot of the dialog, past the list.
---------
Co-authored-by: The412Banner <[email protected]>
15 lines
839 B
Plaintext
15 lines
839 B
Plaintext
Windows components installer tools (usr/local/lib/droiddeck-msitools), Arch Linux ARM's aarch64
|
|
builds, unchanged:
|
|
|
|
msiinfo, libmsi-1.0.so.0 msitools 0.106 GPL-2.0-or-later / LGPL-2.1-or-later
|
|
https://gitlab.gnome.org/GNOME/msitools
|
|
libgsf-1.so.114 libgsf 1.14.60 LGPL-2.1-only
|
|
https://gitlab.gnome.org/GNOME/libgsf
|
|
libgcab-1.0.so.0 gcab 1.6 LGPL-2.1-or-later
|
|
https://gitlab.gnome.org/GNOME/gcab
|
|
cabextract cabextract 1.11 GPL-3.0-or-later
|
|
https://www.cabextract.org.uk/
|
|
|
|
The packages and their sources: https://github.com/Droid-Deck/DroidDeck/releases/tag/msitools-0.106-r1,
|
|
https://github.com/archlinuxarm/PKGBUILDs. The licence texts are beside this file.
|