Skip to content

Windows: Add Qt6 and Editor install script#210

Draft
Ghabry wants to merge 3 commits intoEasyRPG:masterfrom
Ghabry:windows-qt6
Draft

Windows: Add Qt6 and Editor install script#210
Ghabry wants to merge 3 commits intoEasyRPG:masterfrom
Ghabry:windows-qt6

Conversation

@Ghabry
Copy link
Member

@Ghabry Ghabry commented Nov 24, 2025

The buildscripts part to get the editor (soon) running again on Windows.

In short running build_editor.cmd and download_qt6.cmd gets everything setup.

The PR to the editor repo follows later. This needs a bit more work.

@Ghabry
Copy link
Member Author

Ghabry commented Nov 26, 2025

uhm have to shorten the triplet name a bit. I wonder since 2 days why CMake while buliding Kirigami reports "unknown error". Turns out I hit the 260 char path length limit 🤦 so have to tune everything to make it shorter. hmpf

Correction: Enabling Long path support also appears to work.

Run once as administrator in powershell

New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force

Have to document this.

@Ghabry Ghabry marked this pull request as draft November 26, 2025 10:41
@Ghabry Ghabry marked this pull request as ready for review February 18, 2026 15:27
@Ghabry Ghabry marked this pull request as draft February 19, 2026 15:55
@Ghabry
Copy link
Member Author

Ghabry commented Feb 19, 2026

Already documenting the workflow here to build the editor on Windows (PR for the Editor repo will come tomorrow):

Buildscripts:

  1. Run build_editor.cmd
  2. Run download_qt6.cmd
  3. Run setup_env.cmd (if not already done due to Player development)

Now in the Editor repository (inside a MSVC command prompt):

  1. Run cmake --preset windows-x64-vs2022-liblcf-debug
  2. Open the generated Visual Studio solution in build/win
  3. Clicking Run will compile and execute the Editor

Note the difference with liblcf here: For the Player you need -DPLAYER_BUILD_LIBLCF=ON instead. I decided here to create another preset instead because we have far less target architectures here so the combinatorial explosion from all the presets is not as bad.


For other editors (e.g. VS Code):

  1. Configure the editor to use preset windows-x64-liblcf-debug
  2. Run build/win/setup_env.cmd to configure the environment
  3. Start coding

For distribution:

  1. Run cmake --build --preset windows-x64-vs2022-liblcf-debug --target install
  2. You will find the binary and all dependencies in the "install" subdirectory

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments