Qt Creator 17 Ushers in a Fresh Look and Stronger CMake Integration

Linux Journal
1 week 1 day ago
by George Whittaker

In June 2025, the Qt team officially rolled out Qt Creator 17, marking a notable milestone for developers who rely on this IDE for cross-platform Qt, C++, QML, and Python work. While there are many changes under the hood, two of the spotlighted improvements are its updated default visual style and significant enhancements in how CMake is supported. Below, we’ll explore these in depth, assess their impact, and offer guidance on how to adopt the new features smoothly.

What's New in Qt Creator 17: A Snapshot

Before zooming into the theme and CMake changes, here are some of the broader enhancements in version 17 to set context:

  • The “2024” theme set (light and dark variants) — which first appeared in earlier versions — becomes the foundational appearance for all new installs.

  • General polish across the UI: icon refreshes, more consistent spacing, and better contrast.

  • Projects now bind run configurations more tightly to the build configurations. That means selecting a build (e.g. Debug vs Release) also constrains which run configurations apply.

  • Upgraded C++ tooling (with LLVM 20.1.3), improved QML formatting options, enhanced Python (pyproject.toml) support, and refinements in version control & analysis tools.

With that backdrop, let’s dive into the theme and CMake changes in more detail.

A Refreshed Visual Identity: Default “2024” Themes What Has Changed

Qt Creator 17 makes the “2024” light and dark themes the standard look & feel for new installations. These themes had been available previously (since Qt Creator 15) but in this version become the out-of-the-box configuration.

Other visual adjustments accompany the theme change:

  • Icons throughout the IDE have been reviewed and updated so they align better with the new theme style.

  • UI consistency is improved: spacing, contrast, and alignment between interface elements have been refined so that the environment feels more cohesive.

Why These Changes Matter

A theme isn't just aesthetics. The look and feel of an IDE affect user comfort, readability, efficiency, and even fatigue. Some benefits include:

  • Improved clarity for long coding sessions: better contrast helps in low-ambient light or for users with visual sensitivity.

  • Consistency across elements: less jarring visual transitions when switching between parts of the interface or when using external themes/plugins.

  • Reduced setup friction: since the “2024” theme is now default, many users won’t need to hunt down or tweak theme settings just to get a modern, usable look.

Go to Full Article
George Whittaker

[Testing Update] 2025-09-10 - Kernels, Systemd, LibreOffice, Thunderbird, Deepin

Manjaro Linux
1 week 1 day ago

Hello community, here we have another set of package updates.

Current Promotions Recent News Valkey to replace Redis in the [extra] Repository (click for more details) Previous News Finding information easier about Manjaro (click for more details) Notable Package Updates
  • Kernels got updated
  • Systemd 257.9
  • LibreOffice 25.2.6
  • OpenSearch 3.2.0
  • Thunderbird 142.0
  • Deepin updates
  • Haskell and Python updates
Additional Info Python 3.13 info (click for more details) Info about AUR packages (click for more details)

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.

Our current supported kernels
  • linux54 5.4.299
  • linux510 5.10.243
  • linux515 5.15.192
  • linux61 6.1.151
  • linux66 6.6.105
  • linux612 6.12.46
  • linux615 6.15.11 [EOL]
  • linux616 6.16.6
  • linux617 6.17.0-rc5
  • linux61-rt 6.1.146_rt53
  • linux66-rt 6.6.101_rt59
  • linux612-rt 6.12.43_rt12
  • linux615-rt 6.15.0_rt2
  • linux616-rt 6.16.0_rt3

Package Changes (Wed Sep 10 07:56:48 CEST 2025)

  • testing core x86_64: 7 new and 7 removed package(s)
  • testing extra x86_64: 1917 new and 1919 removed package(s)
  • testing multilib x86_64: 21 new and 21 removed package(s)

Overlay Changes

  • testing core x86_64: 25 new and 25 removed package(s)
  • testing extra x86_64: 123 new and 190 removed package(s)
  • testing multilib x86_64: 1 new and 1 removed package(s)

A list of all changes can be found here.

Click to view the poll.

Check if your mirror has already synced:

13 posts - 9 participants

Read full topic

philm

Windows 11 Powers Up WSL: How GPU Acceleration & Kernel Upgrades Change the Game

Linux Journal
1 week 2 days ago
by George Whittaker Introduction

Windows Subsystem for Linux (WSL) has gradually become one of Microsoft’s key bridges for developers, data scientists, and power users who need Linux compatibility without leaving the Windows environment. Over recent versions, WSL2 brought major improvements: a real Linux kernel running in a lightweight virtualized environment, much better filesystem behavior, nearly full system-call compatibility, etc. However, until recently, certain high-performance workloads, GPU computing, video encoding/decoding, and very up-to-date kernel features, were either limited, inefficient, or unavailable.

In Windows 11, Microsoft has taken bold strides to remove many of these bottlenecks. Two of the most significant enhancements are:

  1. The ability for WSL to tap into the GPU for acceleration (compute, video hardware offload, etc.), reducing reliance on CPU where the GPU is much more suited.

  2. More seamless Linux kernel upgrades, allowing users to run newer kernel versions inside WSL2, bringing performance, driver, and feature improvements faster.

This article walks through each thing in detail: what has changed, why it matters, how to use it, what limitations still exist, and how these developments shift what’s possible with WSL on Windows 11.

What WSL Was, and Where It Needed Improvement

Before diving into recent changes, it helps to understand what WSL (especially WSL2) already provided, and where it lagged.

  • WSL1: Early versions translated Linux system calls to Windows equivalents. Good for basic command-line tools, scripts, but limited in compatibility with certain networking, kernel module, filesystem, and performance-sensitive tasks.

  • WSL2: Introduced a real Linux kernel inside a lightweight VM (Hyper-V or a similar backend), better system-call compatibility, better performance especially for Linux tools, and much improved behavior for things like Docker, compiling, etc. Still, heavy workloads (e.g. ML training, video encoding, hardware-accelerated graphics) were constrained by CPU support, lack of passthrough of GPU features, older kernels, etc.

So developers were pushing Microsoft to allow more direct access to GPU functionality (CUDA, DirectML, video decoding), and to speed up how kernel updates reach users.

GPU Acceleration in WSL on Windows 11: What It Means

GPU acceleration here refers to WSL’s ability to offload certain computation or video tasks from the CPU to the GPU, enabling faster, more efficient execution. This includes:

  • Compute workloads - frameworks like CUDA (for NVIDIA), DirectML, etc., so that things like deep learning, scientific computing, data-parallel tasks run much faster. Microsoft now supports running NVIDIA CUDA inside WSL to accelerate ML libraries like PyTorch, TensorFlow.

Go to Full Article
George Whittaker