brunodev85/winlator

Purpose and Entry Points

Winlator is an Android runtime for launching Windows x86_64 applications through Wine with Box86/Box64 emulation. The user-facing entry point is the Android application under app; release installation is via an APK. Runtime support is assembled from native compatibility layers and bundled installable archives.

Paths: app, README.md

Android Application / Runtime Orchestration

The app module is the architectural owner for Android-side installation, container/shortcut configuration, and starting Windows workloads. It must bridge Android lifecycle, storage, display/input, and native runtime processes; the repository does not expose its source tree here, so its internal entry classes cannot be identified.

Paths: app, input_controls/index.txt

Windows Execution Stack

Windows programs execute under Wine, with Box86/Box64 supplying x86/x86_64 binary translation on Android’s ARM environment. Wine add-ons are bundled separately for applications requiring browser or .NET functionality, rather than being application code.

Paths: wine_addons/wine-mono-10.1.0-x86.msi, wine_addons/wine-gecko-2.47.4-x86_64.msi, installable_components/box64/index.txt

Graphics Compatibility and Versioned Components

Graphics translation is installable and versioned independently from the app: DXVK targets Direct3D-over-Vulkan, VKD3D addresses newer Direct3D paths, WineD3D provides an alternative Wine graphics backend, and Turnip provides the Android Vulkan driver stack. The indexed .tzst archives form a component-distribution boundary, enabling runtime selection or updates without representing source modules.

Paths: installable_components/dxvk/index.txt, installable_components/vkd3d/index.txt, installable_components/turnip/index.txt

Audio Integration Boundary

A custom ALSA PCM plugin connects guest/runtime audio to an Android audio-server configuration. The native module is built through CMake and uses vendored ALSA headers/configuration, isolating Android-specific audio adaptation from the Android app and Wine stack.

Paths: android_alsa/module_pcm_android_aserver.c, android_alsa/CMakeLists.txt, android_alsa/android_aserver.conf

libc/System-V Shared-Memory Compatibility

GLIBC patches implement Android-specific System V shared-memory operations (shmget, shmat, shmctl, shmdt). This is a low-level runtime boundary likely needed by Linux-side compatibility software that expects SysV IPC unavailable or divergent on Android.

Paths: glibc_patches/sysdeps/unix/sysv/linux/android_sysvshm.c, glibc_patches/sysdeps/unix/sysv/linux/shmget.c, glibc_patches/sysdeps/unix/sysv/linux/shmat.c

Input Profile Data

Game-specific .icp files and a central index provide data-driven input-control mappings. The app/runtime can select profiles per title instead of embedding each game’s touch/controller bindings into code.

Paths: input_controls/index.txt, input_controls/Skyrim.icp, input_controls/GTA 5.icp

External Runtimes and Infrastructure

Material external dependencies are Wine, Box86/Box64, Mesa/Turnip, DXVK, VKD3D, and Android’s native audio/graphics environment. gladio and vortek are top-level repository boundaries with no visible contents in this tree; their roles cannot be established from the supplied files.

Paths: gladio, vortek, .gitmodules