WSL2 Setup for Development Environments (Bluecon, KEBA)

Tags: WSL, Windows Subsystem for Linux, Qt, KEBA, Bluecon2.5, Ubuntu, ext4.vhdx, Qt5.15.13, Qwt, Virtualization, Windows, Linux, Compatibility, Development, KEBA Controller

Why Use WSL?

WSL (Windows Subsystem for Linux) allows a full Linux environment to run directly within Windows – without needing a separate virtual machine or dual-boot setup. For our Qt/KEBA/Bluecon2.5 development workflow, a preconfigured ext4.vhdx image is provided, ensuring consistency across developer machines.

Step-by-Step Setup Guide

1. Enable WSL Features

Open a terminal with administrator privileges and run:

bashKopierenBearbeitendism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

2. Install WSL2 Linux Kernel Update

Download and install the latest kernel: 👉 WSL2 Kernel Update Package (Microsoft)

3. Set WSL Version to 2 by Default

bashKopierenBearbeitenwsl --set-default-version 2

4. Install Ubuntu from Microsoft Store

Search for “Ubuntu” in the Microsoft Store and install e.g., Ubuntu 20.04.

5. Use the Provided ext4.vhdx Image

Replace the default virtual disk with the provided image: Path:

makefileKopierenBearbeitenC:\Users\<USERNAME>\AppData\Local\Packages\
CanonicalGroupLimited.Ubuntu18.04onWindows_...\LocalState\

6. Disable Hyper-V Temporarily (If Needed)

bashKopierenBearbeitenbcdedit /set hypervisorlaunchtype off

A restart is required. Re-enable with:

bashKopierenBearbeitenbcdedit /set hypervisorlaunchtype auto

Notes for Qt Development in WSL

• Qt version 5.15.13 is used (LGPLv3 compliant).
• Ensure correct Qwt and toolchain paths in Qt Creator.
• Flags like -D_LINUX_ARM_ARCH_ can be removed for x86_64 targets.
• Avoid redefining types like uint64_t to prevent conflicts with standard headers.

💡 Benefits

• Shared .vhdx image provides a consistent development environment.
• Compatible with Linux-based KEBA controllers.
• No need for separate Linux hardware or dual-boot setups.

📂 Internal image path: Z:\Technik\Steuerung\11.KEBA\Images\ext4.vhdx