Skip to content

chore(windows): distribute static CRT and Z3 packages #5653

Open

Description

@shailendra-nv

User Story

For OpenShell Windows ZIP distribution and validation on N1x-Test, the maintainer requested packages that carry their CRT and Z3 dependencies rather than requiring a separate Visual C++ runtime installation and matching Z3 DLL.

Problem Statement

The windows branch currently ships four OpenShell executables plus libz3.dll. The gateway loads that DLL, which depends on the native Visual C++ redistributable. A package therefore needs architecture-matched runtime installation and DLL staging in addition to the OpenShell executables.

Impact / Why This Matters

Missing or mismatched runtime dependencies can prevent gateway startup. Operators must provision the redistributable and preserve the matching Z3 DLL when moving ZIP packages between hosts.

Proposed Design

Build the four Windows executables with the static CRT and embed Z3 in the gateway. Preserve the existing solver version and existing Windows/MXC behavior. Keep the normal windows:build:x64 and windows:build:arm64 commands; their outputs should run without an adjacent Z3 DLL or a Visual C++ redistributable requirement imposed by OpenShell itself. The separate MXC executor retains its own prerequisites.

Acceptance Criteria

  • Both MSVC architectures build the four OpenShell executables with static CRT linkage and static Z3 in the gateway.
  • Release builds reject normal or delayed imports of Z3 and redistributable CRT DLLs.
  • Remote/E2E packaging no longer requires libz3.dll.
  • Native Windows CI, GitHub-hosted x64/ARM64 runners, and N1x-Test runtime validation are reported with any limitations.
  • Compare binary/package sizes and update the Windows build guidance.

Alternatives Considered

Continue distributing the prebuilt Z3 DLL and provisioning the Visual C++ redistributable, or rebuild the DLL with static CRT while retaining separate Z3 distribution. Embedding Z3 removes both deployment dependencies. OpenShell middleware and provider extension points cannot change executable loader dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions