Skip to content

Migrate KAOS project to OpenTK 4 and SDK-style .csproj#2

Draft
stomppah wants to merge 1 commit intodevelopfrom
codex/update-to-opentk-4-and-refactor-code-base
Draft

Migrate KAOS project to OpenTK 4 and SDK-style .csproj#2
stomppah wants to merge 1 commit intodevelopfrom
codex/update-to-opentk-4-and-refactor-code-base

Conversation

@stomppah
Copy link
Copy Markdown
Owner

@stomppah stomppah commented May 7, 2026

Motivation

  • Move the project off the old OpenTK 1.x package and legacy .NET Framework project system to a modern, package-managed OpenTK 4 setup to enable iterative API upgrades.
  • Provide a clean, SDK-style baseline so subsequent runtime changes (windowing, input, math, GL modernization) can be implemented incrementally.

Description

  • Replaced KAOS/KAOS.csproj with an SDK-style project targeting net8.0-windows and enabled WinForms support while preserving explicit Compile includes for the existing source layout.
  • Switched dependency wiring to PackageReference entries and added OpenTK 4.8.2 and OpenTK.GLControl 4.8.2, and updated NUnit and AssimpNet package references.
  • Kept the existing binary references to MataliPhysics and MataliRender via HintPath to avoid breaking the current native/binary dependency surface.
  • Added KAOS/OpenTK4-MIGRATION.md documenting the migration changes and listing the recommended follow-up runtime refactors (game window/input/math/GL updates).

Testing

  • Confirmed the new project file and migration document were added and committed successfully using the repository git commands (commit succeeded).
  • No automated build or unit test runs were executed as part of this change; a follow-up should run dotnet build and existing test suites after runtime API updates are applied.

Codex Task

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant