Skip to content

Issue #31: Implement Windows 10/11 Release Packaging (MSI + Portable EXE) #7

@SSobol77

Description

@SSobol77

Problem Description

Currently, ECLI provides .deb, .rpm, and (planned) macOS + PyPI distributions, but there is no official release process for Windows 10/11. This prevents adoption among a large developer base and enterprise users working on Windows environments.

Proposed Solution

Extend the packaging strategy to support native Windows installers and portable builds:

* Build Process

  • Use PyInstaller to generate a standalone .exe (portable binary).

  • Create an .msi installer (or NSIS-based installer) with:

    • Proper Start Menu shortcuts
    • Uninstaller support
    • Installation into C:\Program Files\ECLI\
  • CI/CD Integration

    • Add a windows-latest job to GitHub Actions.
    • Automate code signing with a provided certificate (if available).
    • Upload .exe and .msi artifacts to GitHub Releases.

Acceptance Criteria

  • make package-windows produces both a portable .exe and an MSI installer.
  • The package runs correctly on Windows 10 and Windows 11 (x86_64, ARM64 optional).
  • The MSI installer properly registers/unregisters ECLI in Windows Programs & Features.
  • Other packaging workflows (.deb, .rpm, macOS, PyPI) remain unaffected.

Metadata

Metadata

Assignees

Labels

build-environmentIssues related to the build environment, Docker, CI/CD, and cross-platform compatibility.enhancementNew feature or requestpackagingIssues related to build scripts, installers, package managers (apt, rpm), Docker, and distribution.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions