Build windows version with github workflow or codespace?

[Fred-Vatin]

Hi,

Anyone knows if someone released such a workflow to build any version of kanata for windows?
I tried using github codespace but it runs on linux with the current devcontainer.json and I don’t know if it would be possible to use windows container for Rust MSVC that really work, a fortiori in codespace. But if someone has a working devcontainer.json to do so, please share. It would be awesome because I don’t want to install Rust in my system just to build the winIOv2 1.6.1 with cmd support. I think the build command is cargo build --release --features win_manifest,cmd,win_llhook_read_scancodes,win_sendinput_send_scancodes. Can you confirm? I need to test this version because the kanata_cmd_allowed.exe is not as reliable as the wintercept version and the latter has been having problems lately.

Or if someone could build this winIOv2 1.6.1 with cmd support for me, I would be grateful. I suggest this winIOv2 with cmd support to be in the next release along with the other builds.

[jtroo]

You can try adapting the macos-build workflow: https://github.com/jtroo/kanata/actions/runs/12272295379/workflow

I don't know if the Windows runner uses the windows-gnu or the windows-msvc toolchain though; the windows-msvc toolchain is the one required.

[Fred-Vatin]

can your confirm cargo build --release --features win_manifest,cmd,win_llhook_read_scancodes,win_sendinput_send_scancodes is the right command to build winIOv2 with cmd support?

[jtroo]

Yes these are the correct flags to my reading. Can check against the justfile.

[gerhard-h]

cargo build --release --features win_manifest,cmd,win_llhook_read_scancodes,win_sendinput_send_scancodes is

I always do cargo build --release --features win_llhook_read_scancodes --features cmd is that the same?

[Fred-Vatin]

The justfile says the command for winIOv2 is

cargo build --release --features win_manifest,win_sendinput_send_scancodes,win_llhook_read_scancodes