Qlocky.UI

The Qlocky.UI is configured as Docker container which can be used with VSCode and Devcontainer Extension. But WSL must be configured right to build Qlocky.UI for target and host:

<aside> ⚠️

For a working docker container, the following points must be installed on WSL

• the crossplatform QT SDK must be installed to /opt/poky
• The /opt/qlocky folder must exist and user must have permissions
• For QT installation sudo apt install libxcb1 libxcb-render0 libxcb-shape0 libxcb-xfixes0 libxcb-xkb1 libxkbcommon-x11-0 libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-randr0 libxcb-render-util0 libxcb-util1 libxcb-xinerama0 libxcb-cursor0 libxcb-cursor-dev
• the native QT SDK must be installed to /opt/qt. (IMPORTANT: Version must match with crossplatform QT 6.8.1 and QT installer must be executed on linux WSL command line)

The following points must be installed on host computer

• The following vscode setting must be enabled on host:

</aside>

VSCode Initial Setup

1. Clone the Qlocky.UI (See Repository Description)
2. Open workspace from VSCode (ensure workspace is opened in container)

Configuration

The VSCode has two CMake configurations:

• armv7_qlocky: Used for Raspberray PI build. Ensure .env file exists and target host is connected to local network.
• x64_gcc: Used for WSL linux x64 host build and unit tests. It contrast to armv7_qlocky, this build uses stubs and mocks for testing.

A change of the active configuration trigger cmake configuration which automatically edits the launch.json file.