Skip to content

Tags

Tags

0.5.0

Toggle 0.5.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: bump version to 0.5.0 (14) (Droid-Deck#1081)

0.4.0

Toggle 0.4.0's commit message
DroidDeck 0.4.0

ci-debian-bullseye-r1

Toggle ci-debian-bullseye-r1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Windows components: install from a recording of the installer's result (

Droid-Deck#495)

* Windows components: install from a recording of the installer's result

A catalog entry may name a 'snapshot': what its own setup program leaves in a prefix,
recorded once in Wine by winlator-contents' tools/snapshot/record.py (the files it places and
the registry values it writes, the self-registering DLLs' CLSID entries included). With one,
the setup program never runs here: the files come from the archive beside the recording, or
out of the vendor's installer by the paths the recording maps (small generated ones inline),
and the registry values go to registry.json for droiddeck-wincomponents to write at launch.
The steps a recording makes redundant are skipped; DLL overrides still apply. A component
with a recording counts as installable; its prerequisites must still be.

* droiddeck-msi-install --unpack: open archives nested inside an installer

QuickTime's cabinets and an NSIS pack's payloads sit inside the unpacked installer; they are
opened in place into '<name>.nested' folders, two levels deep, the same layout the component
recordings map their file sources to, so a recording's paths resolve on the device (QuickTime:
593 of 593).

0.3.2

Toggle 0.3.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: bump version to 0.3.2 (12) (Droid-Deck#437)

msitools-0.106-r1

Toggle msitools-0.106-r1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: catch KGSL GEM_CLOSE at ioctl instead of exporting drmIoctl (Dro…

…id-Deck#305)

* fix: avoid reusing retired KGSL GEM handles

* fix: defer closing GEM_CLOSE'd KGSL dma-buf descriptors

* Revert "fix: defer closing GEM_CLOSE'd KGSL dma-buf descriptors"

This reverts commit 191bf4b.

* test: interpose drmIoctl without releasing GEM_CLOSE handles

* fix: catch KGSL GEM_CLOSE at ioctl instead of exporting drmIoctl

0.3.1

Toggle 0.3.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Prepare 0.3.1 release (Droid-Deck#263)

* docs: draft 0.3.1 release notes

* chore: bump version to 0.3.1 (11)

gamescope-3.16.29-p6

Toggle gamescope-3.16.29-p6's commit message
Keep the software compatibility declaration at namespace scope

0.3.0

Toggle 0.3.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request Droid-Deck#141 from Droid-Deck/release/0.3.0

Release 0.3.0: version bump, Deck mode for everyone, release notes and media, Updates page fix

fex-2609-r3

Toggle fex-2609-r3's commit message
FEX build: the x86 sysroot for the guest thunks' toolchains

The guest halves linked without it on the arm64 builder (no crtbeginS.o,
no libgcc).

fex-2609-r2

Toggle fex-2609-r2's commit message
FEX: fall back to openat inside the rootfs when openat2 is missing

Our proot answers openat2 with ENOSYS. FEX opened every rootfs path with
openat2(RESOLVE_IN_ROOT) and only fell back on EXDEV, so in a session
every x86 file lookup missed the rootfs and hit the arm64 guest: bash
under FEX could not find libtinfo. GetEmulatedFDPath already follows
absolute symlinks inside the rootfs, so a plain openat relative to the
rootfs fd is the same lookup. The rootfs also gets an empty
ld.so.preload, so the guest's arm64 preloads are not tried.