From Eike.Ziller at qt.io  Wed Feb  4 08:20:12 2026
From: Eike.Ziller at qt.io (Eike Ziller)
Date: Wed, 4 Feb 2026 07:20:12 +0000
Subject: [Qt-creator] Dev: Qt Creator 19 string freeze is approaching
Message-ID: <197A0633-E134-4560-A96D-ACB32B3774A9@qt.io>

Hi,

this is just a reminder for Qt Creator developers that the string and UI freeze for Qt Creator 19 is scheduled for next week (with Beta2):

Qt Creator 19
 
* String freeze wk7 (~ Feb 12 2026)
* RC release wk9 (~ Feb 26 2026)
* Final release wk11 (~ Mar 12 2026)

https://wiki.qt.io/Qt_Creator_Releases
https://wiki.qt.io/Qt_Creator_Submission_Policies#Release_Branch_States

I've already done a pass over new UI texts, but if you find anything else now is the time to fix it.

Br, Eike

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
eike.ziller at qt.io
https://qt.io

Gesch?ftsf?hrer: Mika P?lsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B



From andrzej at telszewski.com  Tue Feb 10 10:19:04 2026
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Tue, 10 Feb 2026 10:19:04 +0100
Subject: [Qt-creator] Set build environment variable from Qt Creator variable
Message-ID: <645b1626-1bd8-4067-9965-1f79a60f3642@telszewski.com>

Hi,

how can I use QtC's variables expansion to set an environment variable 
(e.g. in build environment)?

Because if I do, say:

STAGING_DIR=%{Project:Path}/../staging_dir

the "%{Project:Path}" isn't really expanded.

Thank you.

--
Best regards,
Andrzej Telszewski


From christian.kandeler at qt.io  Tue Feb 10 10:49:10 2026
From: christian.kandeler at qt.io (Christian Kandeler)
Date: Tue, 10 Feb 2026 10:49:10 +0100
Subject: [Qt-creator] Set build environment variable from Qt Creator
 variable
In-Reply-To: <645b1626-1bd8-4067-9965-1f79a60f3642@telszewski.com>
References: <645b1626-1bd8-4067-9965-1f79a60f3642@telszewski.com>
Message-ID: <c6119231-9674-41d5-9aa5-eaa031963ca8@qt.io>

On 2/10/26 10:19 AM, Andrzej Telszewski wrote:
> how can I use QtC's variables expansion to set an environment variable 
> (e.g. in build environment)?
There is currently no support for macro expansion in most environment 
widgets.
Feel free to file a feature request at bugreports.qt.io.

Christian

From Eike.Ziller at qt.io  Fri Feb 13 08:30:47 2026
From: Eike.Ziller at qt.io (Eike Ziller)
Date: Fri, 13 Feb 2026 07:30:47 +0000
Subject: [Qt-creator] Qt Creator 19 is in string freeze now
In-Reply-To: <197A0633-E134-4560-A96D-ACB32B3774A9@qt.io>
References: <197A0633-E134-4560-A96D-ACB32B3774A9@qt.io>
Message-ID: <A22AC887-FBFE-4284-AE3C-591256AE1B70@qt.io>

String freeze and UI freeze for Qt Creator 19 are in effect now.

Br, Eike

> On 4. Feb 2026, at 08:20, Eike Ziller via Qt-creator <qt-creator at qt-project.org> wrote:
>
> Hi,
>
> this is just a reminder for Qt Creator developers that the string and UI freeze for Qt Creator 19 is scheduled for next week (with Beta2):
>
> Qt Creator 19
>
> * String freeze wk7 (~ Feb 12 2026)
> * RC release wk9 (~ Feb 26 2026)
> * Final release wk11 (~ Mar 12 2026)
>
> https://wiki.qt.io/Qt_Creator_Releases
> https://wiki.qt.io/Qt_Creator_Submission_Policies#Release_Branch_States
>
> I've already done a pass over new UI texts, but if you find anything else now is the time to fix it.
>
> Br, Eike
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Erich-Thilo-Str. 10
> 12489 Berlin, Germany
> eike.ziller at qt.io
> https://qt.io/
>
> Gesch?ftsf?hrer: Mika P?lsi,
> Juha Varelius, Jouni Lintunen
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
>
>
> --
> Qt-creator mailing list
> Qt-creator at qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator

--
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
eike.ziller at qt.io
https://qt.io/

Gesch?ftsf?hrer: Mika P?lsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B



From andrzej at telszewski.com  Tue Feb 24 18:51:49 2026
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Tue, 24 Feb 2026 18:51:49 +0100
Subject: [Qt-creator] Set build environment variable from Qt Creator
 variable
In-Reply-To: <c6119231-9674-41d5-9aa5-eaa031963ca8@qt.io>
References: <645b1626-1bd8-4067-9965-1f79a60f3642@telszewski.com>
 <c6119231-9674-41d5-9aa5-eaa031963ca8@qt.io>
Message-ID: <59233d92-56dc-4451-a6db-b9fd9172c8a3@telszewski.com>

On 10/02/2026 10:49, Christian Kandeler via Qt-creator wrote:
> On 2/10/26 10:19 AM, Andrzej Telszewski wrote:
>> how can I use QtC's variables expansion to set an environment 
>> variable (e.g. in build environment)?
> There is currently no support for macro expansion in most environment 
> widgets.
> Feel free to file a feature request at bugreports.qt.io.
>

Did the first step and registered to the bugreports ;)

Anyways, I'll still want to ask: is there _any_ way to set build 
environment variable,
that could somehow contain project's root directory - not hardcoded, but 
derived?

My use case is for *.shared project files.
When creating such shared project file, I use the likes of macro expansion,
so that the shared file does not contain any hardcoded paths, and works
no matter in which location I checkout my source code.

Thanks!


From christian.kandeler at qt.io  Wed Feb 25 10:46:34 2026
From: christian.kandeler at qt.io (Christian Kandeler)
Date: Wed, 25 Feb 2026 10:46:34 +0100
Subject: [Qt-creator] Set build environment variable from Qt Creator
 variable
In-Reply-To: <59233d92-56dc-4451-a6db-b9fd9172c8a3@telszewski.com>
References: <645b1626-1bd8-4067-9965-1f79a60f3642@telszewski.com>
 <c6119231-9674-41d5-9aa5-eaa031963ca8@qt.io>
 <59233d92-56dc-4451-a6db-b9fd9172c8a3@telszewski.com>
Message-ID: <bdd34d12-7e9b-4a88-a15b-66fba06359dc@qt.io>

On 2/24/26 6:51 PM, Andrzej Telszewski wrote:
> On 10/02/2026 10:49, Christian Kandeler via Qt-creator wrote:
>> On 2/10/26 10:19 AM, Andrzej Telszewski wrote:
>>> how can I use QtC's variables expansion to set an environment 
>>> variable (e.g. in build environment)?
>> There is currently no support for macro expansion in most environment 
>> widgets.
>> Feel free to file a feature request at bugreports.qt.io.
>>
>
> Did the first step and registered to the bugreports ;)
>
> Anyways, I'll still want to ask: is there _any_ way to set build 
> environment variable,
> that could somehow contain project's root directory - not hardcoded, 
> but derived?
>
> My use case is for *.shared project files.
> When creating such shared project file, I use the likes of macro 
> expansion,
> so that the shared file does not contain any hardcoded paths, and works
> no matter in which location I checkout my source code.

I don't think so. However: Isn't this something you should rather do in 
your project file? Surely your build system provides you with the 
project directory and allows you to set environment variables?

Christian

From andrzej at telszewski.com  Thu Feb 26 19:00:30 2026
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Thu, 26 Feb 2026 19:00:30 +0100
Subject: [Qt-creator] Set build environment variable from Qt Creator
 variable
In-Reply-To: <bdd34d12-7e9b-4a88-a15b-66fba06359dc@qt.io>
References: <645b1626-1bd8-4067-9965-1f79a60f3642@telszewski.com>
 <c6119231-9674-41d5-9aa5-eaa031963ca8@qt.io>
 <59233d92-56dc-4451-a6db-b9fd9172c8a3@telszewski.com>
 <bdd34d12-7e9b-4a88-a15b-66fba06359dc@qt.io>
Message-ID: <92472a2e-728e-4fd0-8030-8fcde0bf063f@telszewski.com>

On 25/02/2026 10:46, Christian Kandeler via Qt-creator wrote:
> On 2/24/26 6:51 PM, Andrzej Telszewski wrote:
>> On 10/02/2026 10:49, Christian Kandeler via Qt-creator wrote:
>>> On 2/10/26 10:19 AM, Andrzej Telszewski wrote:
>>>> how can I use QtC's variables expansion to set an environment 
>>>> variable (e.g. in build environment)?
>>> There is currently no support for macro expansion in most 
>>> environment widgets.
>>> Feel free to file a feature request at bugreports.qt.io.
>>>
>>
>> Did the first step and registered to the bugreports ;)
>>
>> Anyways, I'll still want to ask: is there _any_ way to set build 
>> environment variable,
>> that could somehow contain project's root directory - not hardcoded, 
>> but derived?
>>
>> My use case is for *.shared project files.
>> When creating such shared project file, I use the likes of macro 
>> expansion,
>> so that the shared file does not contain any hardcoded paths, and works
>> no matter in which location I checkout my source code.
>
> I don't think so. However: Isn't this something you should rather do 
> in your project file? Surely your build system provides you with the 
> project directory and allows you to set environment variables?

My wish would be not to modify the build system, but actually that might 
be the best option.
It's CMake, so that's no-brainer.

Thanks!