Re: [Qt-creator] Need help building my plugin in GitHub
Sorry, that is an unfortunate error. The include is not even used anymore, it is a left-over from previous patches and can be removed: 553256: TextEditor: Remove non-exported include from public header | https://codereview.qt-project.org/c/qt-creator/qt-creator/+/553256 Br, Eike > Am 04.04.2024 um 21:29 schrieb Carel Combrink : > > Just a follow up. > > The issue now is my plugin includes > qt-creator\src\plugins\texteditor\syntaxhighlighter.h which includes #include > but this header is not contained in the > '_dev' package/archive.(PS: I only see 'state' and not 'Definitions') > The files are still in the github project: > https://github.com/qt-creator/qt-creator/tree/v13.0.0/src/libs/3rdparty/syntax-highlighting/autogenerated/include/KSyntaxHighlighting > Not sure why they are not packaged in the _dev package > -- > Qt-creator mailing list > Qt-creator@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.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] [qt-creator] custom plugin using debugger compilation error
Hi,
> qtcreator-4.12.4
As a side note, you should probably not start developing a plugin for that old
version of Qt Creator.
> Debugger::Internal::DebuggerEngine *engine =
> Debugger::Internal::EngineManager::currentEngine();
EngineManager is internal (as can be seen from the namespace), and the symbol
is not exported to other plugins/libraries.
I do not think that the Debugger plugin allows the kind of interaction that you
want from it.
Br, Eike
> Am 08.03.2024 um 00:28 schrieb ogre up :
>
> Hi all,
> I want to implement a qt creator plug-in that can read specified variables
> (such as a vector with more elements) from the debugger, and then export the
> variable values to a text file.
>
> Currently, simple sample plug-ins can be compiled and loaded according to the
> qt creator wizard (using qt creator 4.12.4/Qt 5.14.2/vs2017 build tools), but
> when trying to use the Debugger class, a compilation error will appear,
> prompting an unresolved external symbol. I tried adding a dependency on
> debugger in the pro file, but it didn't seem to have any effect.
>
> complier error message as follows:
> example.obj : error LNK2019: Unresolved external symbol "public: static class
> QPointer __cdecl
> Debugger::Internal::EngineManager::currentEngine(void)"
> (?currentEngine@EngineManager@Internal
> @Debugger@@SA?AV?$QPointer@VDebuggerEngine@Internal@DebuggerXZ), this
> symbol is in the function "private: void __cdecl
> Example::Internal::ExamplePlugin::triggerAction(void)" (?triggerAction@
> Referenced in ExamplePlugin@Internal@Example@@AEAAXXZ)
> ..\..\..\..\Qt\qtcreator-4.12.4\lib\qtcreator\plugins\Example4.dll : fatal
> error LNK1120: 1 unresolved external command
>
>
> some of the source code as follows:
> void ExamplePlugin::triggerAction()
> {
> QMessageBox::information(Core::ICore::mainWindow(),
> tr("Action Triggered"),
> tr("This is an action from Example."));
>
> Debugger::Internal::DebuggerEngine *engine =
> Debugger::Internal::EngineManager::currentEngine();
> if (engine)
> {
> // try fetch variable by name, and dump it's values to text file ...
> }
> }
>
> and lib dependency settings in pro file:
>
> QTC_PLUGIN_NAME = Example
> QTC_LIB_DEPENDS += \
> # nothing here at this time
>
> QTC_PLUGIN_DEPENDS += \
> coreplugin \
> debugger \
> projectexplorer
>
> QTC_PLUGIN_RECOMMENDS += \
> # optional plugin dependencies. nothing here at this time
> --
> I would like to know:
> 1. How to solve the above compilation error?
> 2. To achieve the function I want, what code snippets can I refer to?
>
> Any suggestion would be appreciated.
> --
> Qt-creator mailing list
> Qt-creator@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.zil...@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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 13 is now in string and UI freeze
Qt Creator 13 (13.0 branch) is now in string and UI freeze. Br, Eike > Am 26.02.2024 um 12:15 schrieb Eike Ziller via Qt-creator > : > > This is a reminder that string and UI freeze for Qt Creator 13.0 is scheduled > for this week. > > Qt Creator 13 > > * String freeze wk9 (~Feb 29 2024) > * RC release wk11 (~Mar 14 2024) > * Final release wk13 (~Mar 28 2024) > > https://wiki.qt.io/Qt_Creator_Releases > https://wiki.qt.io/Qt_Creator_Submission_Policies > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Str. 10 > 12489 Berlin, Germany > eike.zil...@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@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.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: String and UI freeze for 13.0 scheduled for this week
This is a reminder that string and UI freeze for Qt Creator 13.0 is scheduled for this week. Qt Creator 13 * String freeze wk9 (~Feb 29 2024) * RC release wk11 (~Mar 14 2024) * Final release wk13 (~Mar 28 2024) https://wiki.qt.io/Qt_Creator_Releases https://wiki.qt.io/Qt_Creator_Submission_Policies Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Raising the minimum required Qt version for building Qt Creator 14+ to Qt 6.4(.3)
> Am 20.02.2024 um 11:54 schrieb Mike Trahearn : > > Could you please qualify why not Qt 6.5 LTS at this time? We are not that far > away from the next LTS. I just answered on the similar question on gerrit: The absolute minimum requirement is "2 stable versions including at least 1 LTS release". That could be Qt 6.5 (LTS) and Qt 6.6, but since Qt 6.5.0-.3 had various issues, adding another one before that (Qt 6.4.3 which has "proven itself" in Qt 10 & 11) seems reasonable. Br, Eike > > From: Qt-creator on behalf of Eike Ziller > via Qt-creator > Sent: Tuesday, February 20, 2024 8:12:10 PM > To: QtCreator List > Subject: [Qt-creator] Raising the minimum required Qt version for building Qt > Creator 14+ to Qt 6.4(.3) Hi, > > we would like to raise the Qt version required for building Qt Creator to Qt > 6.4(.3), starting with Qt Creator 14 (current master branch). > That does not affect which Qt versions you can use for developing your own > applications. > > Qt 6.5 is the latest LTS version of Qt. > Qt 6.6 is released (and we build prebuilt packages with it). > Qt 6.7 will release soon. > > Raising the requirement to Qt 6.4 still leaves 4 minor Qt versions including > a LTS line for building Qt Creator. > > 541548: Require Qt 6.4.3 for building Qt Creator | > https://urldefense.com/v3/__https://codereview.qt-project.org/c/qt-creator/qt-creator/*/541548__;Kw!!Nbma_1s!poZh5uCJ1c3bJdMGOBewD7GJ-c_uZquS0coeUgGje2QPXdF7dW2AxB3XbmK89ub0XUiCr2mvFvgIedEY6ZsT8OnJ$ > > > Feel free to comment here or on the change! > > Br, Eike > > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Str. 10 > 12489 Berlin, Germany > eike.zil...@qt.io > https://urldefense.com/v3/__https://qt.io__;!!Nbma_1s!poZh5uCJ1c3bJdMGOBewD7GJ-c_uZquS0coeUgGje2QPXdF7dW2AxB3XbmK89ub0XUiCr2mvFvgIedEY6Vj9cfNz$ > > > 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@qt-project.org > https://urldefense.com/v3/__https://lists.qt-project.org/listinfo/qt-creator__;!!Nbma_1s!poZh5uCJ1c3bJdMGOBewD7GJ-c_uZquS0coeUgGje2QPXdF7dW2AxB3XbmK89ub0XUiCr2mvFvgIedEY6bWUNFqM$ > > Confidentiality Notice: This message (including attachments) is a private > communication solely for use of the intended recipient(s). If you are not the > intended recipient(s) or believe you received this message in error, notify > the sender immediately and then delete this message. Any other use, > retention, dissemination or copying is prohibited and may be a violation of > law, including the Electronic Communication Privacy Act of 1986. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Raising the minimum required Qt version for building Qt Creator 14+ to Qt 6.4(.3)
Hi, we would like to raise the Qt version required for building Qt Creator to Qt 6.4(.3), starting with Qt Creator 14 (current master branch). That does not affect which Qt versions you can use for developing your own applications. Qt 6.5 is the latest LTS version of Qt. Qt 6.6 is released (and we build prebuilt packages with it). Qt 6.7 will release soon. Raising the requirement to Qt 6.4 still leaves 4 minor Qt versions including a LTS line for building Qt Creator. 541548: Require Qt 6.4.3 for building Qt Creator | https://codereview.qt-project.org/c/qt-creator/qt-creator/+/541548 Feel free to comment here or on the change! Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Heads-up Qt Creator 13 feature freeze this week - NEW PROCESS
The branch "master" is open for submitting again, Qt Creator 13 is in feature freeze. Please concentrate on fixing bugs there. The Qt Creator 13 Beta1 is scheduled for ~ in two weeks. Br, Eike > Am 30.01.2024 um 09:51 schrieb Eike Ziller : > > I have created the 13.0 branch(es). > > The master branch is locked (nobody can submit) until feature freeze. > > You can move existing changes in Gerrit to the new branch with the vertical > “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). > If you miss the submit button even after moving and getting a +2 code review, > check that you have a +1 sanity review as well (can be manually added by > Approvers in the review dialog). > > Br, Eike > >> Am 29.01.2024 um 16:45 schrieb Eike Ziller via Qt-creator >> : >> >> This is a heads-up that Qt Creator 13 feature freeze is planned for this >> week. >> >> To avoid the phase of "the 13.0 branch is created, but we are not in feature >> freeze yet and master is merged back into 13.0 branch for a few days" >> confusion (some patches end up in 13.0, some in master) and merge hassle, >> we'll try something else this time. >> The goal of the previous process was to give people some time to get aware >> of the creation of the 13.0 branch, and avoid that fixed that accidentally >> were submitted to master branch have to be cherry-picked to the 13.0 branch. >> This time I'll: >> >> 1) Create the 13.0 branch and LOCK MASTER branch (tomorrow, Tuesday, Jan >> 30). Qt Creator 13 is NOT in feature freeze yet. >> 2) Everything (except for fixes for 12.0.x) needs to go into 13.0 branch >> during this time. This will hopefully make everyone aware that feature >> freeze is about to happen. >> 3) Thursday morning master branch is unlocked, and Qt Creator 13 goes into >> feature freeze. After that, all content in master is for Qt Creator 14. >> >> Br, Eike >> >> https://wiki.qt.io/Qt_Creator_Releases >> >> Qt Creator 13 >> >> * Feature freeze wk5 (~Feb 1 2024) >> * Beta release wk7 (~Feb 15 2024) >> * String freeze wk9 (~Feb 29 2024) >> * RC release wk11 (~Mar 14 2024) >> * Final release wk13 (~Mar 28 2024) >> -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Heads-up Qt Creator 13 feature freeze this week - NEW PROCESS
I have created the 13.0 branch(es). The master branch is locked (nobody can submit) until feature freeze. You can move existing changes in Gerrit to the new branch with the vertical “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). If you miss the submit button even after moving and getting a +2 code review, check that you have a +1 sanity review as well (can be manually added by Approvers in the review dialog). Br, Eike > Am 29.01.2024 um 16:45 schrieb Eike Ziller via Qt-creator > : > > This is a heads-up that Qt Creator 13 feature freeze is planned for this week. > > To avoid the phase of "the 13.0 branch is created, but we are not in feature > freeze yet and master is merged back into 13.0 branch for a few days" > confusion (some patches end up in 13.0, some in master) and merge hassle, > we'll try something else this time. > The goal of the previous process was to give people some time to get aware of > the creation of the 13.0 branch, and avoid that fixed that accidentally were > submitted to master branch have to be cherry-picked to the 13.0 branch. > This time I'll: > > 1) Create the 13.0 branch and LOCK MASTER branch (tomorrow, Tuesday, Jan 30). > Qt Creator 13 is NOT in feature freeze yet. > 2) Everything (except for fixes for 12.0.x) needs to go into 13.0 branch > during this time. This will hopefully make everyone aware that feature freeze > is about to happen. > 3) Thursday morning master branch is unlocked, and Qt Creator 13 goes into > feature freeze. After that, all content in master is for Qt Creator 14. > > Br, Eike > > https://wiki.qt.io/Qt_Creator_Releases > > Qt Creator 13 > > * Feature freeze wk5 (~Feb 1 2024) > * Beta release wk7 (~Feb 15 2024) > * String freeze wk9 (~Feb 29 2024) > * RC release wk11 (~Mar 14 2024) > * Final release wk13 (~Mar 28 2024) > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Str. 10 > 12489 Berlin, Germany > eike.zil...@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@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.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Heads-up Qt Creator 13 feature freeze this week - NEW PROCESS
This is a heads-up that Qt Creator 13 feature freeze is planned for this week. To avoid the phase of "the 13.0 branch is created, but we are not in feature freeze yet and master is merged back into 13.0 branch for a few days" confusion (some patches end up in 13.0, some in master) and merge hassle, we'll try something else this time. The goal of the previous process was to give people some time to get aware of the creation of the 13.0 branch, and avoid that fixed that accidentally were submitted to master branch have to be cherry-picked to the 13.0 branch. This time I'll: 1) Create the 13.0 branch and LOCK MASTER branch (tomorrow, Tuesday, Jan 30). Qt Creator 13 is NOT in feature freeze yet. 2) Everything (except for fixes for 12.0.x) needs to go into 13.0 branch during this time. This will hopefully make everyone aware that feature freeze is about to happen. 3) Thursday morning master branch is unlocked, and Qt Creator 13 goes into feature freeze. After that, all content in master is for Qt Creator 14. Br, Eike https://wiki.qt.io/Qt_Creator_Releases Qt Creator 13 * Feature freeze wk5 (~Feb 1 2024) * Beta release wk7 (~Feb 15 2024) * String freeze wk9 (~Feb 29 2024) * RC release wk11 (~Mar 14 2024) * Final release wk13 (~Mar 28 2024) -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] check if debugger is running
Hi, since multiple debuggers could be running for different projects etc I guess getting all current RunControls with ProjectExplorerPlugin::allRunControls(), and checking their runMode() (ProjectExplorer::Constants::DEBUG_RUN_MODE) and if they are isRunning() or isStarting(), and possibly checking their project()/target() would be a possibility. Br, Eike > Am 31.10.2023 um 14:57 schrieb Knut Petter Svendsen via Qt-creator > : > > Hi! > > In my plugin, I've established a slot connected to the > EditorManager::currentEditorChanged signal. I'm looking for a way to > determine if I'm presently in a debugging session within this slot. This > distinction is important as I intend to perform different actions based on > this context. > > Although checking Core::ModeManager::currentModeId() against > Debugger::Constants::MODE_DEBUG allows me to ascertain if I'm in debugging > mode, it doesn't inform me whether the debugger is actively running. > > Knut > > -- > Qt-creator mailing list > Qt-creator@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.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: String freeze of Qt Creator 12 is scheduled for this week
String freeze is now in effect. Br, Eike > Am 24.10.2023 um 11:01 schrieb Eike Ziller via Qt-creator > : > > Hi, > > The string freeze for Qt Creator 12 is planned for this week, as well as > Beta2. > We've already gone through the strings, but if you find anything that needs > fixing, this is now the latest time to do it. > > Qt Creator 12 > > * String freeze wk43 (~Oct 26 2023) > * RC release wk45 (~Nov 9 2023) > * Final release wk47 (~Nov 23 2023) > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Str. 10 > 12489 Berlin, Germany > eike.zil...@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@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.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: String freeze of Qt Creator 12 is scheduled for this week
Hi, The string freeze for Qt Creator 12 is planned for this week, as well as Beta2. We've already gone through the strings, but if you find anything that needs fixing, this is now the latest time to do it. Qt Creator 12 * String freeze wk43 (~Oct 26 2023) * RC release wk45 (~Nov 9 2023) * Final release wk47 (~Nov 23 2023) Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 12 feature freeze is planned for next week
The last merge from master to 12.0 is done. Qt Creator 12 is now in feature freeze. Everything that goes to master is now for 13.0. The Qt Creator 12 Beta release is scheduled for ~Oct 12. Br, Eike > Am 25.09.2023 um 15:35 schrieb Eike Ziller : > > I have created the 12.0 branch(es). Please start using them. > You can move existing changes in Gerrit to the new branch with the vertical > “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). > > I will merge changes going into the master branch back into the 12.0 branch > for a few days until a final merge from master->12.0 on Thursday. > After that, all changes going into the master branch will be for Qt Creator 13 > > Merges from 11.0 -> 12.0 -> master continue to happen as usual. > > https://wiki.qt.io/Qt_Creator_Releases > > Br, Eike > >> Am 21.09.2023 um 14:03 schrieb Eike Ziller via Qt-creator >> : >> >> Hello Qt Creator developers, this is a heads-up/reminder that Qt Creator 12 >> feature freeze is planned for next week: >> >> Qt Creator 12 >> • Feature freeze wk39 (~Sep 28 2023) >> • Beta release wk41 (~Oct 12 2023) >> • String freeze wk43 (~Oct 26 2023) >> • RC release wk45 (~Nov 9 2023) >> • Final release wk47 (~Nov 23 2023) >> >> Br, Eike >> >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Erich-Thilo-Str. 10 >> 12489 Berlin, Germany >> eike.zil...@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@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.zil...@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 -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] clangd/clang-tidy give errors but MSVC doesn't
Hi, unfortunately building with MSVC and feeding Clangd with information are different processes. The former one is just telling CMake to do its stuff based on the CMake project files, but we cannot do the same for Clangd or clang-tidy. CMake gives us information about the flags that it passes to MSVC, but it complicates things that Clang and MSVC have different interfaces. Qt Creator generates /.qtc_clangd/compile_commands.json for Clang, from the information from CMake given via .cmake/api/v1/reply/, and some information can also be inspected via Tools > Debug Qt Creator > Inspect C++ Code Model. The best would be to create a bug report with information on which flags go missing and other details. Br, Eike > Am 27.09.2023 um 18:43 schrieb Adam Light : > > Hi > > If I compile my cmake-based project from Qt Creator 11.0.2 on Windows using > the build tools that come with MS Visual Studio 2022, the project compiles > without errors or warnings emitted. However, if I run clang-tidy on the > entire project, there are quite a few files that cannot be processed due to > compile errors in the file. If I open those files with errors in Creator, I > see the red circle in the margin, indicating an error, on the same lines that > clang-tidy complains about. > > Clearly clangd/clang-tidy and MSVC are doing something different if the > compile is successful only in MSVC, but I can't figure out why that would be. > > In the QtC global settings for clangd, I have "Build-system warnings" > selected for Diagnostic configuration. In the project settings for this > project, "Use global settings" is checked for everything, including Clang > Tools and clangd. I am using the default clangd and clang-tidy executables > that ship with QtC. > > We are suppressing quite a few warnings in our CMakeLists.txt files, and the > command lines I see for clang-tidy.exe don't have corresponding -Wno... > flags, so maybe that's the problem. If so, it's not clear to me how to work > around this, especially since I have "Build-system warnings" selected for > clangd diagnostics. > > Thanks for any ideas > > Adam > -- > Qt-creator mailing list > Qt-creator@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.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 12 feature freeze is planned for next week
I have created the 12.0 branch(es). Please start using them. You can move existing changes in Gerrit to the new branch with the vertical “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). I will merge changes going into the master branch back into the 12.0 branch for a few days until a final merge from master->12.0 on Thursday. After that, all changes going into the master branch will be for Qt Creator 13 Merges from 11.0 -> 12.0 -> master continue to happen as usual. https://wiki.qt.io/Qt_Creator_Releases Br, Eike > Am 21.09.2023 um 14:03 schrieb Eike Ziller via Qt-creator > : > > Hello Qt Creator developers, this is a heads-up/reminder that Qt Creator 12 > feature freeze is planned for next week: > > Qt Creator 12 >• Feature freeze wk39 (~Sep 28 2023) >• Beta release wk41 (~Oct 12 2023) >• String freeze wk43 (~Oct 26 2023) >• RC release wk45 (~Nov 9 2023) >• Final release wk47 (~Nov 23 2023) > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Str. 10 > 12489 Berlin, Germany > eike.zil...@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@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.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 12 feature freeze is planned for next week
Hello Qt Creator developers, this is a heads-up/reminder that Qt Creator 12 feature freeze is planned for next week: Qt Creator 12 • Feature freeze wk39 (~Sep 28 2023) • Beta release wk41 (~Oct 12 2023) • String freeze wk43 (~Oct 26 2023) • RC release wk45 (~Nov 9 2023) • Final release wk47 (~Nov 23 2023) Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] closeEditors
Hi,
are you doing all these things while "in the stack trace" of the
EM::currentEditorChanged signal?
Please make sure that you are not changing the EditorManager state in
EM::currentEditorChanged with a direct connection.
Br, Eike
> Am 13.09.2023 um 15:40 schrieb Knut Petter Svendsen via Qt-creator
> :
>
> Hi everyone,
>
> I'm currently working on a plugin where I aim to achieve the following
> functionality:
>
> ```
> Given I open file "filename1.cpp"
> Then immediately open "filename2.cpp"
> And close "filename1.cpp" so it is not in the "open documents".
> ```
>
> I have a slot connected to
> `EditorManager::currentEditorChanged(IEditor*)`. In this slot, I perform a
> condition check and subsequently execute `EditorManager::openEditor()`
> with the other file, which works smoothly. However, when attempting to
> close the first file with
> EditorManager::closeEditors({EditorManager::currentEditor()}) (not even
> opening the second file), I encounter a segfault at
> `LanguageClient::SemanticTokenSupport::onCurrentEditorChanged`.
>
> Why is this not be functioning as expected, and I wonder if there might be
> a more effective solution?
>
>
> --
> Qt-creator mailing list
> Qt-creator@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.zil...@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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] QtCreator 11 compile problem on Gentoo
Hi, sounds like https://bugreports.qt.io/browse/QTCREATORBUG-29238 As a workaround you can set DISABLE_COMPILE_WARNING_AS_ERROR=ON Br, Eike > Am 26.06.2023 um 14:15 schrieb Alexey Minnekhanov : > > I can confirm I've also seen this compile error (also on Gentoo). > FIxed by removing all "-Werror" from build.ninja file > > пн, 26 июн. 2023 г. в 09:56, Oleg Shalnev : >> >> Good day. >> >> I have no idea what's wrong with my build system. >> 10.0.2 was built without problems. >> >> Thank's a lot. >> >> OVS (Kalpa Foundation) >> -- >> e-mail : oleg@arisha.online , oleg.shal...@gmail.com >> cell,Viber,WhatsUp,Telegram : +7 (918) 741 7217 >> >> -- >> Qt-creator mailing list >> Qt-creator@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > -- > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer Qt Group Erich-Thilo-Straße 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Qt Creator 11 is now in string freeze
Hi, Qt Creator 11 (11.0 branch) is now in string freeze. The final Qt Creator 11.0.0 release is planned for in about 4 weeks (~Jul 20 2023): https://wiki.qt.io/Qt_Creator_Releases Br, Eike -- Eike Ziller Principal Software Engineer Qt Group Erich-Thilo-Straße 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 11 string freeze this week
Hi, Qt Creator 11 string freeze is planned for this week (as well as the beta2). We have gone through a lot of translatable strings trying to fix as much as possible, but if you find issues in the translatable strings or have some time checking some of the UI, the next days would be a good time to do fixes ;) https://wiki.qt.io/Qt_Creator_Releases Qt Creator 11 * String freeze wk25 (~Jun 22 2023) * RC release wk27 (~Jul 6 2023) * Final release wk29 (~Jul 20 2023) Br, Eike -- Eike Ziller Principal Software Engineer Qt Group Erich-Thilo-Straße 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 11 feature freeze this week
The last merge from master back to 11.0 is done. Qt Creator 11 is now in feature freeze. Please test and fix issues in 11.0 branch in preparation for the beta release. Features go to master branch which becomes Qt Creator 12. Br, Eike > Am 22/05/2023 um 10:18 schrieb Eike Ziller via Qt-creator > : > > Hi all, > > Qt Creator 11 feature freeze is planned for this week. > > I have created the 11.0 branch(es). Please start using them. > You can move existing changes in Gerrit to the new branch with the vertical > “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). > > I will merge changes going into the master branch back into the 11.0 branch > for a few days until a final merge from master->11.0 on Thursday. > After that, all changes going into the master branch will be for Qt Creator > 12. > > Merges from 10.0 -> 11.0 -> master continue to happen as usual. > > https://wiki.qt.io/Qt_Creator_Releases > > Qt Creator 11 > > * Feature freeze wk21 (~May 25 2023) > * Beta release wk23 (~Jun 8 2023) > * String freeze wk25 (~Jun 22 2023) > * RC release wk27 (~Jul 6 2023) > * Final release wk29 (~Jul 20 2023) > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > Qt Group > Erich-Thilo-Straße 10 > 12489 Berlin, Germany > eike.zil...@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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer Qt Group Erich-Thilo-Straße 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Using build type in _Default build directory_
If the name is not sufficient (which should be there by default), I guess it
would be just %{BuildConfig:Type}
Br, Eike
> Am 24/05/2023 um 10:06 schrieb Andrzej Telszewski :
>
> Hi,
>
> when configuring CMake based project, I would like the build directory to
> contain the _build type_ in the directory path.
>
> I tried putting:
>
> - %{CurrentDocument:Project:BuildConfig:Name}
> - %{ActiveProject:BuildConfig:Name}
> - %{CurrentDocument:Project:BuildConfig:Type}
> - %{ActiveProject:BuildConfig:Type}
>
>
> in the _Default build directory:_ in Preferences -> Build & Run -> Default
> Build Properties.
>
> Unfortunately, when configuring the project, I get _empty_ or "unknown"
> strings.
>
> Is there any way to solve it?
>
> Thank you!
>
> --
> Best regards,
> Andrzej Telszewski
>
> --
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
--
Eike Ziller
Principal Software Engineer
Qt Group
Erich-Thilo-Straße 10
12489 Berlin, Germany
eike.zil...@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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 11 feature freeze this week
Hi all, Qt Creator 11 feature freeze is planned for this week. I have created the 11.0 branch(es). Please start using them. You can move existing changes in Gerrit to the new branch with the vertical “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). I will merge changes going into the master branch back into the 11.0 branch for a few days until a final merge from master->11.0 on Thursday. After that, all changes going into the master branch will be for Qt Creator 12. Merges from 10.0 -> 11.0 -> master continue to happen as usual. https://wiki.qt.io/Qt_Creator_Releases Qt Creator 11 * Feature freeze wk21 (~May 25 2023) * Beta release wk23 (~Jun 8 2023) * String freeze wk25 (~Jun 22 2023) * RC release wk27 (~Jul 6 2023) * Final release wk29 (~Jul 20 2023) Br, Eike -- Eike Ziller Principal Software Engineer Qt Group Erich-Thilo-Straße 10 12489 Berlin, Germany eike.zil...@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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 10 string freeze this week
Qt Creator 10 is in string freeze now. Br, Eike > Am 27/02/2023 um 11:19 schrieb Eike Ziller via Qt-creator > : > > Hi, > > this is a reminder that Qt Creator 10 string freeze is planned for this week: > > https://wiki.qt.io/Qt_Creator_Releases > > Qt Creator 10 > > * String freeze wk9 (~Mar 2 2023) > * RC release wk11 (~Mar 16 2023) > * Final release wk13 (~Mar 30 2023) > > After string freeze, any translatable strings (tr(...)) should stay as they > are, to give translators some time before the release. So if you find wrong > UI texts, now is the last time to fix them. > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 10 string freeze this week
Hi, this is a reminder that Qt Creator 10 string freeze is planned for this week: https://wiki.qt.io/Qt_Creator_Releases Qt Creator 10 * String freeze wk9 (~Mar 2 2023) * RC release wk11 (~Mar 16 2023) * Final release wk13 (~Mar 30 2023) After string freeze, any translatable strings (tr(...)) should stay as they are, to give translators some time before the release. So if you find wrong UI texts, now is the last time to fix them. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 10 feature freeze next week
I have created the 10.0 branch(es). Please start using them. We will still do a merge from master branch back to 10.0 branch for the feature freeze next week, so if you accidentally push to master instead of 10.0 there is no need to cherry-pick. (And the other way round, changes submitted to 10.0 branch will eventually be merged up to master branch, as usual.) You can move existing changes in Gerrit to the new branch with the vertical “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). Br, Eike > Am 24/01/2023 um 15:39 schrieb Eike Ziller via Qt-creator > : > > Hi, > > this is an early reminder that Qt Creator 10 feature freeze is planned for > next week: > > https://wiki.qt.io/Qt_Creator_Releases > > Qt Creator 10 > > * Feature freeze wk5 (~Feb 2 2023) > * Beta release wk7 (~Feb 16 2023) > * String freeze wk9 (~Mar 2 2023) > * RC release wk11 (~Mar 16 2023) > * Final release wk13 (~Mar 30 2023) > > I'll create 10.0 branches later this week. > > Br, Eike > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Testing of own plugin
And when I've already written the code: Plugins: Add documentation about testing https://codereview.qt-project.org/c/qt-creator/qt-creator/+/456340 > Am 25/01/2023 um 12:24 schrieb Eike Ziller via Qt-creator > : > > Hi, > > yes, you can use both. > > A short description would be: > > To add plugin tests, add private slots that start with "test" to your IPlugin > implementation. These are looked for when you run Qt Creator with "-test > ". > Use these if you rely on the Qt Creator infrastructure to be available, e.g. > if your test needs to interact with other parts of Qt Creator. > > Otherwise use auto tests. You can use the add_qtc_test function if you want, > though I'm not sure if that adds anything useful, but it will give you a > similar interface as for plugins and executables. > > I've added a few dummy tests to my example dummy plugin, as a reference for > (one way of solving) the details, that uses the fact that add_qtc_plugin etc > does some helpful things when WITH_TESTS is set: > > https://github.com/e4z9/qtcreator-testplugin/commit/fa8065f580ee5724f8b9afb06e904e1be1c2e343 > > Br, Eike > >> Am 25/01/2023 um 11:21 schrieb Knut Petter Svendsen via Qt-creator >> : >> >> Hi! >> >> I'm writing my own plugin and I want to add tests. I know that QtCreator >> itself has a mechanism with adding tests via slots and WITH_TESTS. How can >> I do the same for my own plugin? >> >> Is this the best way to add tests, or can i add "normal" unit tests as well? >> >> Regards, >> Knut Petter Svendsen >> >> >> >> ___ >> Qt-creator mailing list >> Qt-creator@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator ___ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Testing of own plugin
Hi, yes, you can use both. A short description would be: To add plugin tests, add private slots that start with "test" to your IPlugin implementation. These are looked for when you run Qt Creator with "-test ". Use these if you rely on the Qt Creator infrastructure to be available, e.g. if your test needs to interact with other parts of Qt Creator. Otherwise use auto tests. You can use the add_qtc_test function if you want, though I'm not sure if that adds anything useful, but it will give you a similar interface as for plugins and executables. I've added a few dummy tests to my example dummy plugin, as a reference for (one way of solving) the details, that uses the fact that add_qtc_plugin etc does some helpful things when WITH_TESTS is set: https://github.com/e4z9/qtcreator-testplugin/commit/fa8065f580ee5724f8b9afb06e904e1be1c2e343 Br, Eike > Am 25/01/2023 um 11:21 schrieb Knut Petter Svendsen via Qt-creator > : > > Hi! > > I'm writing my own plugin and I want to add tests. I know that QtCreator > itself has a mechanism with adding tests via slots and WITH_TESTS. How can > I do the same for my own plugin? > > Is this the best way to add tests, or can i add "normal" unit tests as well? > > Regards, > Knut Petter Svendsen > > > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator ___ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 10 feature freeze next week
Hi, this is an early reminder that Qt Creator 10 feature freeze is planned for next week: https://wiki.qt.io/Qt_Creator_Releases Qt Creator 10 * Feature freeze wk5 (~Feb 2 2023) * Beta release wk7 (~Feb 16 2023) * String freeze wk9 (~Mar 2 2023) * RC release wk11 (~Mar 16 2023) * Final release wk13 (~Mar 30 2023) I'll create 10.0 branches later this week. Br, Eike ___ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Fossil plugin for Qt Creator
Hi, thanks for the note, something seems to have gone wrong with the tag. The v9.0.0 is available at https://github.com/qt-creator/plugin-fossil-scm/releases now (there is no 9.0.1 because nothing changed). Br, Eike > Am 24/12/2022 um 19:09 schrieb dougf.ccn : > > I installed the latest version of (Open Source) Qt Creator (9.0.1) but the > Fossil plugin is not available for this version. > > Why not? Is there something I can do to make it available? > Doug Forester > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Closing pinned files
> Am 11 Nov 2022 um 06:55 schrieb Carel Combrink : > > On Mon, 31 Oct 2022 at 09:51, Eike Ziller via Qt-creator > wrote: > > > The idea is to avoid accidentally closing the pinned file via shortcuts. So > > not necessarily about forbidding closing it, but ensuring that it doesn't > > leave the open documents list. > > > I also recently started using the "pin file" feature and was surprised that > after spamming CTRL + W the pinned files were closed. > I have no suggestions yet on what I expect to happen, but that they got > closed was unexpected. > > Thinking about it a bit it might make sense to close all editors and keep the > pinned ones in the open documents list. > It sounds counterproductive since then they are not opened anymore, thus they > don't fit in the list (new list or renamed panel?) Actually "Open Documents" is a lie anyway. Qt Creator reserves the right to unload all data from an (unmodified) "open document" and just keep the entry in the Open Documents. See Preferences > Environment > System > Auto-suspend unmodified files. > > What I don't want is to get 'stuck' on a pinned file when I try to close > everything but the pinned ones with the shortcut. > And then again, perhaps a shortcut to "close all except the pinned ones" is > the correct way to handle this and then get stuck on a pinned one with a > warning or indication as other people mentioned in this discussion. > > Regards, > Carel -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Closing pinned files
> Am 24/10/2022 um 03:28 schrieb EXT Mitch Curtis via Qt-creator > : > [...] >> Do you really want to forbid to actually close the split containing the >> file, or >> do you just want to keep the file name in the Open Documents list? > > The idea is to avoid accidentally closing the pinned file via shortcuts. So > not necessarily about forbidding closing it, but ensuring that it doesn't > leave the open documents list. > >> If the latter is sufficient, then no user question is needed. > > What should happen if the pinned file is the only one open in that case? Can > a document be in the open documents list if it's not actually open in an > editor? Actually yes, that is possible. Check out the document drop down in the editor toolbar: You can switch to "" there, even though all documents stay in the Open Documents view. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 9 feature freeze this week
The last merge from master to 9.0 branch has been done. The 9.0 branch is now in feature freeze. (Merges from 9.0 to master continue to be done as usual.) The 9.0 Beta 1 release is scheduled for in two weeks (around Oct 11). Br, Eike > On 27 Sep 2022, at 08:07, Eike Ziller wrote: > > Hi, > > the feature freeze for Qt Creator 9 is planned for this week. > I have created the 9.0 branch(es). Please start using them. (You can move > existing changes in Gerrit to the new branch with the vertical “…” menu, > “Move change”, on the top right corner in Gerrit (next to “Edit”).) > > I will do a last merge from master to 9.0 branch on Thursday, 29.9.22, and > then Qt Creator 9.0 branch will be in feature freeze. > > Qt Creator 9 > > * Feature freeze wk39 (~Sep 27 2022) > * Beta release wk41 (~Oct 11 2022) > * String freeze wk43 (~Oct 25 2022) > * RC release wk45 (~Nov 8 2022) > * Final release wk47 (~Nov 22 2022) > > https://wiki.qt.io/Qt_Creator_Releases > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 9 feature freeze this week
Hi, the feature freeze for Qt Creator 9 is planned for this week. I have created the 9.0 branch(es). Please start using them. (You can move existing changes in Gerrit to the new branch with the vertical “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”).) I will do a last merge from master to 9.0 branch on Thursday, 29.9.22, and then Qt Creator 9.0 branch will be in feature freeze. Qt Creator 9 * Feature freeze wk39 (~Sep 27 2022) * Beta release wk41 (~Oct 11 2022) * String freeze wk43 (~Oct 25 2022) * RC release wk45 (~Nov 8 2022) * Final release wk47 (~Nov 22 2022) https://wiki.qt.io/Qt_Creator_Releases Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Problem with Creator braces style settings
Do you have the ClangFormat plugin turned on? I can reproduce your issue when that is on. Seems to be a conflict between ClangFormat style settings and our internal style settings. Br, Eike > On 29 Aug 2022, at 06:29, Bob Babcock wrote: > > Running Windows 10, Qt Creator 8.0.1 > > If I edit the code style MyStyle, on the braces tab, no matter what > checkboxes I check, it always reverts to only namespace declarations > being checked. > > Qt Creator 4.15.2 doesn't do this; I don't have any other versions to > check. > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Using own git server (https self signed)
Hi, a late answer: I don’t think that you configure additional parameters for the git command(s) that Qt Creator uses, but since -c just (temporarily) sets a git configuration, you could configure that in either your project’s .git/config with "git config http.sslVerify false", or your user's ~/.git/config with "git config --global http.sslVerify false" Br, Eike > Am 25/07/2022 um 23:17 schrieb Petric Frank : > > Hello, > > Am Montag, 25. Juli 2022, 13:30:24 CEST schrieb Orgad Shaneh: >> On Mon, Jul 25, 2022 at 2:25 PM Konstantin Tokarev >> >> wrote: >>>> Try to configure:git config http.sslVerify false >>> >>> This undermines whole point of using HTTPS (besides buzzword >>> compatibility). >>> Use http.sslCAInfo to verify server certificate, or use different protocol >>> like ssh or plain http. >> >> This is a server in an internal network, so MITM is very unlikely. >> >> I did not suggest to configure it globally, but only for this repository. > > The option > -c http.sslVerify=false > > passed to the git command seems to disable the check. > > But how to configure that in qtcreator ? > > regards > Petric > > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] macOS TCC Permissions
Thank you and sorry: This broke in Qt Creator 8 by https://codereview.qt-project.org/c/qt-creator/qt-creator/+/413978 A fix is up for review and will then hopefully be part of the 8.0.1 snapshots soon. https://codereview.qt-project.org/c/qt-creator/qt-creator/+/423269 Br, Eike > Am 21/07/2022 um 01:36 schrieb Nakyle Wright : > > Looks like a nice fix was added for the TCC headache in this commit: > https://codereview.qt-project.org/gitweb?p=qt-creator/qt-creator.git;a=commit;h=86783985a03752b2205d7d9ee168051003cb64c4 > > But it does not seem to be working for me, I just updated to: > > Qt Creator 8.0.0 > Based on Qt 6.3.1 (Clang 13.0 (Apple), x86_64) > Built on Jul 19 2022 08:17:26 > From revision 5c341854e0 > > And I can see that the bundle includes the disclaim helper, and so I assumed > it would work. > Is there a setting I need to enable? I cleared out my .pro.user and project > build files just to be sure it was starting from a clean slate. > > Also note, that enabling the “Run In Terminal” option or just double-clicking > the built .app bundle works fine, I have all the necessary entries in my apps > Info.plist. > > --- > NaKyle Wright > nwri...@atlaswhd.com > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Requiring Qt 6 for building Qt Creator 9 and later
Hi all, we would like to require Qt 6.2 or later for building Qt Creator itself going forward in master branch, which is Qt Creator 9 and later. We’ll have released 3 versions of Qt Creator based on Qt 6 then (starting with Qt Creator 6) by then, Qt 6 has matured and has its first LTS version with Qt 6.2. It starts to happen that fixes are done in Qt 6 that are no longer backported to Qt 5, and removing support for Qt 5 will allow us to remove hacks and glue code that enabled us to compile against both Qt 5 and Qt 6. This by extension means that the required compilers increase to GCC 9 and MSVC 2019 (from GCC 7 and MSVC 2017). And the supported platforms increase to Ubuntu 20.04, RHEL/CentOS 8, and macOS 10.14, which they already are for our prebuilt binary packages, since these are already Qt 6 based. The corresponding patch is on Gerrit for comments: https://codereview.qt-project.org/c/qt-creator/qt-creator/+/420047 The Qt versions that we support for developing your own applications with, are of course not affected by this change. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] The state of the clang-format plugin
> On 30 Jun 2022, at 20:00, Nikos Chantziaras wrote: > > On 29/06/2022 22:11, Nikos Chantziaras wrote: >> On 29/06/2022 17:33, Eike Ziller wrote: >>> At the moment you can change the setting globally to “Disable” >> Where is that setting found? Can't find it anywhere. > > You probably meant Creator 7. In 8, that option is gone and there's no way to > prevent Creator from forcing my personal coding style everywhere. > > I opened a bug about it: > > https://bugreports.qt.io/browse/QTCREATORBUG-27781 > > IMO, this is a serious show stopper as it makes Creator completely unusable > when working on projects not under your control. I’m confused. I’m talking about Qt Creator 8. The default setting for the ClangFormat plugin is “Indenting Only”. Which does not format on save at all. The setting is (like in Qt Creator 7 unfortunately a bit hidden and that should be changed) in Preferences > C++ > Code Style > Edit. The options for “Formatting mode” are “Indenting Only” (the default), “Full Formatting”, and “Disable”. The only option there that “formats on save” is “Full Formatting”, if you do not want that, switch to e.g. “Disable”, save, switch back on. All that said, Artem reverted to the old checkboxes yesterday, so the RC will have the checkboxes again. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Qt Creator 8 is in string freeze
Qt Creator 8 is now in string freeze, including UI freeze & soft API freeze. https://wiki.qt.io/Qt_Creator_Submission_Policies https://wiki.qt.io/Qt_Creator_Releases Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] The state of the clang-format plugin
> On 29 Jun 2022, at 16:09, Nikos Chantziaras wrote: > > On 29/06/2022 09:40, Eike Ziller wrote: >>> On 29 Jun 2022, at 05:26, Nikos Chantziaras wrote: >>> How are you supposed to deal with lines you didn't edit changing and have >>> no place in a git commit? It's impossible to work on code that's under >>> version control. >> The ClangFormat plugin restricts formatting on save to the regions that you >> edited since last saving (the regions that have a green marker on the side. > > This is unsuitable when you don't want to reformat the code. But more > importantly, when you undo, it breaks down. You edit something, then notice > it formatted when saving, you undo it, but it won't work. No matter what you > do, it will format it. I definitely would like to have an easy way to trigger a save without formatting even while “format on save” is generally turned on. At the moment you can change the setting globally to “Disable”, save the file, and turn the option back on, but it is cumbersome. > I noticed it like an hour too late, when my git diff was a complete mess, as > it formatted code I didn't want touched. > > At that point, I had to switch back to Creator 7. > > This makes it virtually impossible to use Creator. Sure, if you only ever > work on your own code, it's fine. But I work on a ton of projects, most of > them don't even have a clang-format file. > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] The state of the clang-format plugin
> On 29 Jun 2022, at 08:40, Eike Ziller wrote: > > > >> On 29 Jun 2022, at 05:26, Nikos Chantziaras wrote: >> >> On 28/06/2022 12:06, Christian Kandeler wrote: >>> On 6/25/22 10:58, Björn Schäpers wrote: >>>> in the days of yore you had 3 check marks for clang-format (still visible >>>> here >>>> https://doc.qt.io/qtcreator/images/qtcreator-code-style-clang-format.png). >>>> * Format instead of indenting >>>> * Format while typing >>>> * Format edited code on file save >>>> >>>> Nowadays the UI is gone, and at least option 2 is gone >>>> (https://codereview.qt-project.org/c/qt-creator/qt-creator/+/411513) I >>>> asked on why, but no answer yet. >>> I suppose the assumption was that this was not needed. If it turns out >>> there are actually people using that, it can be brought back. >> >> How are you supposed to deal with lines you didn't edit changing and have no >> place in a git commit? It's impossible to work on code that's under version >> control. > > The ClangFormat plugin restricts formatting on save to the regions that you > edited since last saving (the regions that have a green marker on the side. With a red marker, of course, not green. > > Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] The state of the clang-format plugin
> On 29 Jun 2022, at 05:26, Nikos Chantziaras wrote: > > On 28/06/2022 12:06, Christian Kandeler wrote: >> On 6/25/22 10:58, Björn Schäpers wrote: >>> in the days of yore you had 3 check marks for clang-format (still visible >>> here >>> https://doc.qt.io/qtcreator/images/qtcreator-code-style-clang-format.png). >>> * Format instead of indenting >>> * Format while typing >>> * Format edited code on file save >>> >>> Nowadays the UI is gone, and at least option 2 is gone >>> (https://codereview.qt-project.org/c/qt-creator/qt-creator/+/411513) I >>> asked on why, but no answer yet. >> I suppose the assumption was that this was not needed. If it turns out there >> are actually people using that, it can be brought back. > > How are you supposed to deal with lines you didn't edit changing and have no > place in a git commit? It's impossible to work on code that's under version > control. The ClangFormat plugin restricts formatting on save to the regions that you edited since last saving (the regions that have a green marker on the side. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 8 string freeze this week
Hello all Qt Creator developers, we’ll go into string freeze this week. This includes a UI freeze, and soft API freeze. The RC is scheduled for next week already, so please already reduce refactorings to a minimum and have a look at fixing your remaining high priority bugs. https://wiki.qt.io/Qt_Creator_Submission_Policies Qt Creator 8 * String freeze wk26 (~Jun 28 2022) * RC release wk27 (~Jul 5 2022) * Final release wk29 (~Jul 19 2022) Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 8 feature freeze this week
The last merge from master to 8.0 is done (https://codereview.qt-project.org/c/qt-creator/qt-creator/+/414048) From now on master branch is Qt Creator 9.0, and Qt Creator 8.0 is in feature freeze. Br, Eike > On 30 May 2022, at 09:12, Eike Ziller wrote: > > Hi, > > the feature freeze for Qt Creator 8 is planned for this week, so let us go > into feature freeze on Thursday, 2.6.22. I have created the 8.0 branches, > please start using them. I will do a last merge from master branch to 8.0 > branch on Thursday - after that all content in master branch will be for Qt > Creator 9. > > You can move existing changes in Gerrit to the new branch with the vertical > “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). > > Qt Creator 8 > > * Feature freeze wk22 (~May 31 2022) > * Beta release wk24 (~Jun 14 2022) > * String freeze wk26 (~Jun 28 2022) > * RC release wk28 (~Jul 12 2022) > * Final release wk30 (~Jul 26 2022) > > https://wiki.qt.io/Qt_Creator_Releases > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 8 feature freeze this week
Hi, the feature freeze for Qt Creator 8 is planned for this week, so let us go into feature freeze on Thursday, 2.6.22. I have created the 8.0 branches, please start using them. I will do a last merge from master branch to 8.0 branch on Thursday - after that all content in master branch will be for Qt Creator 9. You can move existing changes in Gerrit to the new branch with the vertical “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). Qt Creator 8 * Feature freeze wk22 (~May 31 2022) * Beta release wk24 (~Jun 14 2022) * String freeze wk26 (~Jun 28 2022) * RC release wk28 (~Jul 12 2022) * Final release wk30 (~Jul 26 2022) https://wiki.qt.io/Qt_Creator_Releases Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] List of Available Variable Names for Build Directory
When you put the cursor into that input field, it has a funny A->B button at
its right edge (inside the input field). That pops up a dialog showing a list
of possible values.
Br, Eike
> On 29 Apr 2022, at 15:55, Michael Jackson wrote:
>
> Is there a documented list somewhere that shows all of the variables that I
> can use to setup a build directory? I want to separate build directories
> based on the system architecture. Something like:
>
> ../%{JS:
> Util.asciify("%{Project:Name}-Build/%{BuildConfig:Name}-%{BuildConfig:arch}")}
>
> --
> Mike Jackson
>
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Precheck button now also checks Qt 5 build
The “precheck” button in Gerrit can (and should) be used (afair by Approvers) to schedule a build on COIN to verify that the patch builds successfully. So far that was building Qt Creator on all platforms with Qt 6. Since we still support building Qt Creator with Qt 5, and have seen a few breakages in the past (e.g. for overloaded signals), I’ve added one job that builds it with Qt 5.15.2 on Linux. So, if you get a build failure and wonder why, it might be because of Qt 5. The new job builds on "Linux RHEL_8_4 (gcc-x86_64)” and has “Qt5” mentioned in its "Coin Features”. An example is here (precheck on a merge commit): https://testresults.qt.io/coin/integration/qt-creator/qt-creator/tasks/1649065843 You can see the job details after expanding the “Build” section. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] How to show functions as an alphabetized list in QtCreator 7.0
> On 4 Apr 2022, at 06:43, Christian Stenger wrote: > > Hi Mike, > > Perform a right click on the drop down menu (when it's closed). This will > bring up a mini context menu with a checkable menu item (sort alphabetically) It looks like this is not implemented for clangd (or other lanugage servers). Br, Eike > > BR, > Christian > > > From: Qt-creator on behalf of Michael > Jackson > Sent: Sunday, April 3, 2022 3:16 AM > To: QtCreator List > Subject: [Qt-creator] How to show functions as an alphabetized list in > QtCreator 7.0 > > Downloaded the new version. Over all like the additions (Jumped from > 4.15) but I cannot quite seem to figure out how to make the function > drop down at the top of the editor as an alphabetized list instead of > the order in which the functions appear in the file. > -- > Mike Jackson > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 7 string freeze this week
Qt Creator 7 is in string freeze now. Br, Eike > On 22 Feb 2022, at 08:18, Eike Ziller wrote: > > Qt Creator 7 string freeze (and UI freeze and soft API freeze) are scheduled > for this week, I plan to declare that on the morning of Thursday 24.2. > So this is the last opportunity for fixing things. > > https://wiki.qt.io/Qt_Creator_Releases > > Qt Creator 7 > > * Feature freeze wk04 (~Jan 25 2022) > * Beta release wk06 (~Feb 8 2022) > * String freeze wk08 (~Feb 22 2022) > * RC release wk10 (~Mar 8 2022) > * Final release wk12 (~Mar 22 2022) > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 7 string freeze this week
Qt Creator 7 string freeze (and UI freeze and soft API freeze) are scheduled for this week, I plan to declare that on the morning of Thursday 24.2. So this is the last opportunity for fixing things. https://wiki.qt.io/Qt_Creator_Releases Qt Creator 7 * Feature freeze wk04 (~Jan 25 2022) * Beta release wk06 (~Feb 8 2022) * String freeze wk08 (~Feb 22 2022) * RC release wk10 (~Mar 8 2022) * Final release wk12 (~Mar 22 2022) -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Creator 7 & LLVM 15
> On 11 Feb 2022, at 12:03, Björn Schäpers wrote: > > Hi, > > I updated my system and now have some problems: > - I switched my compiler from MinGW to MinGW with UCRT > - Updated from Qt 5.15.2 to 6.2.3 - switched from qmake to cmake > - Updated Creator from 6.0 beta2 to whatever yesterday was HEAD on the 7.0 > branch - also switched to cmake > - Updated LLVM from some 14 DEV to some 15 DEV (quite recent - with your > patches to it) > > And my problems are: > - Although the clang-format-plugin is loaded (and reported no error to me) in > the settings it's the old code style page, no clang-format. That was merged as a tab into the code style page > - clangd says: Failed to retrieve clangd version: Unexpected clangd output. > From my console (doesn't matter if bash or cmd): > $ clangd --version > clangd version 15.0.0 > (https://github.com/HazardyKnusperkeks/llvm-project.git > 9d5b44357a0bfd06efa676db94b29182dfc24a42) > Features: windows > Platform: x86_64-w64-windows-gnu > > I thought I will take a look into it and open the creator project, just to > see that: :-1: error: CMake version is unsupported. Please update to version > 3.14 (with file-api) or later. > $ cmake --version > cmake version 3.22.2 "CMake version is unsupported” Between “version” and “is” there should be a version number, so it looks like the version parsing failed there too. Or, since especially the cmake version doesn’t seem unusual, maybe Qt Creator failed to execute the processes? Some things to look at: - What do you see in Tools > Options > Kits > CMake ? Is the right cmake binary there, is any error shown, is the version number shown? - What does the “CMake Tool” setting in the kit say? - Maybe running Qt Creator from a terminal shows some enlightening output, or maybe it does when setting QT_LOGGING_RULES=“qtc.utils.qtcprocess.debug=true”. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Updating requirements for building Qt Creator 7+ (master branch)
> On 28 Jan 2022, at 19:42, Иван Комиссаров wrote: > > Hello! > > Are there any plans on updating the minimum required version of Visual studio > and a target platform on Mac? Regarding target platforms we should try to not be more restrictive than the supported target platforms of the Qt versions that we still support building Qt Creator with. So, macOS 10.14 will become minimum when we finally drop support for building with Qt 5. That will still take a while though - we still find quite some Qt-version related regressions. So far no plans for raising the requirement on MSVC, though we could probably go up to 2019 if there are compelling reasons. Br, Eike > Ivan > >> 28 янв. 2022 г., в 11:04, Eike Ziller написал(а): >> >> Another one: >> >> # Bumping the required CMake version for building Qt Creator to CMake 3.16 >> and later >> >> Seems to be available on Ubuntu 20.04 and Debian 11 and others >> (https://pkgs.org/search/?q=cmake), and lets us get rid of some workarounds. >> >> Require CMake 3.16 and remove workarounds (I32500375) · Gerrit Code Review >> https://codereview.qt-project.org/c/qt-creator/qt-creator/+/392678 >> >>> On 14 Jan 2022, at 13:44, Eike Ziller wrote: >>> >>> # Bumping the required Qt version for building Qt Creator from Qt 5.14 to >>> Qt 5.15.2. >>> >>> Qt 5.15.2 contains API that eases the transition to Qt 6. So far we added >>> workarounds for Qt 5.14, that we could remove, and we then also don’t need >>> to add more of them in new code. >>> >>> Regarding Linux distributions, Ubuntu 21 and Debian 11 seem to have Qt >>> 5.15.2, and others too (https://pkgs.org/search/?q=qtbase) >>> >>> Bump requirement to Qt 5.15.2 (I920fdccc) · Gerrit Code Review >>> https://codereview.qt-project.org/c/qt-creator/qt-creator/+/390103 >>> >>> # Removing qmake as a build system for building Qt Creator itself >>> >>> The CMake port is “done”, and official packages are built with CMake. The >>> qmake build is basically untested, and maintaining it in addition is a >>> burden. We also had a nice transitioning period of more than a year (Qt >>> Creator 4.14 being the first version that was released based on the CMake >>> build). >>> >>> Remove qmake build files (I846c6ef6) · Gerrit Code Review >>> https://codereview.qt-project.org/c/qt-creator/qt-creator/+/390104 >>> >>> Br, Eike >>> >>> -- >>> Eike Ziller >>> Principal Software Engineer >>> >>> The Qt Company GmbH >>> Erich-Thilo-Straße 10 >>> D-12489 Berlin >>> eike.zil...@qt.io >>> http://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@qt-project.org >>> https://lists.qt-project.org/listinfo/qt-creator >> >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Erich-Thilo-Straße 10 >> D-12489 Berlin >> eike.zil...@qt.io >> http://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@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Updating requirements for building Qt Creator 7+ (master branch)
Another one: # Bumping the required CMake version for building Qt Creator to CMake 3.16 and later Seems to be available on Ubuntu 20.04 and Debian 11 and others (https://pkgs.org/search/?q=cmake), and lets us get rid of some workarounds. Require CMake 3.16 and remove workarounds (I32500375) · Gerrit Code Review https://codereview.qt-project.org/c/qt-creator/qt-creator/+/392678 > On 14 Jan 2022, at 13:44, Eike Ziller wrote: > > # Bumping the required Qt version for building Qt Creator from Qt 5.14 to Qt > 5.15.2. > > Qt 5.15.2 contains API that eases the transition to Qt 6. So far we added > workarounds for Qt 5.14, that we could remove, and we then also don’t need to > add more of them in new code. > > Regarding Linux distributions, Ubuntu 21 and Debian 11 seem to have Qt > 5.15.2, and others too (https://pkgs.org/search/?q=qtbase) > > Bump requirement to Qt 5.15.2 (I920fdccc) · Gerrit Code Review > https://codereview.qt-project.org/c/qt-creator/qt-creator/+/390103 > > # Removing qmake as a build system for building Qt Creator itself > > The CMake port is “done”, and official packages are built with CMake. The > qmake build is basically untested, and maintaining it in addition is a > burden. We also had a nice transitioning period of more than a year (Qt > Creator 4.14 being the first version that was released based on the CMake > build). > > Remove qmake build files (I846c6ef6) · Gerrit Code Review > https://codereview.qt-project.org/c/qt-creator/qt-creator/+/390104 > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 7 feature freeze next week
Last merge master -> 7.0 is done. Br, Eike > On 26 Jan 2022, at 09:06, Eike Ziller wrote: > > I have created the 7.0 branch(es). > > Please start using the 7.0 branch for anything that is supposed to land in > 7.0. > You can move existing changes to the new branch with the vertical “…” menu, > “Move change”, on the top right corner in Gerrit (next to “Edit”). > > I’ll still merge master branch back to 7.0 tomorrow, for changes that > accidentally landed in the wrong branch. > Qt Creator 7 will then be in feature freeze starting tomorrow. > > Br, Eike > >> On 19 Jan 2022, at 08:40, Eike Ziller wrote: >> >> This is a quick reminder that feature freeze for Qt Creator 7 is planned for >> next week: >> >> Qt Creator 7 >> >> * Feature freeze wk04 (~Jan 25 2022) >> * Beta release wk06 (~Feb 8 2022) >> * String freeze wk08 (~Feb 22 2022) >> * RC release wk10 (~Mar 8 2022) >> * Final release wk12 (~Mar 22 2022) >> >> https://wiki.qt.io/Qt_Creator_Releases >> >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Erich-Thilo-Straße 10 >> D-12489 Berlin >> eike.zil...@qt.io >> http://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@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 7 feature freeze next week
I have created the 7.0 branch(es). Please start using the 7.0 branch for anything that is supposed to land in 7.0. You can move existing changes to the new branch with the vertical “…” menu, “Move change”, on the top right corner in Gerrit (next to “Edit”). I’ll still merge master branch back to 7.0 tomorrow, for changes that accidentally landed in the wrong branch. Qt Creator 7 will then be in feature freeze starting tomorrow. Br, Eike > On 19 Jan 2022, at 08:40, Eike Ziller wrote: > > This is a quick reminder that feature freeze for Qt Creator 7 is planned for > next week: > > Qt Creator 7 > > * Feature freeze wk04 (~Jan 25 2022) > * Beta release wk06 (~Feb 8 2022) > * String freeze wk08 (~Feb 22 2022) > * RC release wk10 (~Mar 8 2022) > * Final release wk12 (~Mar 22 2022) > > https://wiki.qt.io/Qt_Creator_Releases > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Unexpected (?) behaviour for "Files in any project" short-cut
> On 20 Jan 2022, at 17:20, Toralf Lund wrote:
>
> Hi
>
> Under "Keyboard" in Qt Creator Environment Options, I've assigned a keyboard
> shortcut to "Locator - Files in any project". The actual behaviour I get
> looks more like "Files in All Projects", though.. In cases where I have
> "non-project" files e.g. from build inside the project directory, those may
> be listed, too. Is that they way it should be?
>
> I notice that under the "Locator" tab (as opposed to the "Locator" section of
> "Keyboard"), the same prefix ("a") is associated with both functions - I
> guess that may have something to do with it. This is not something I've ever
> changed.
>
> I'm using a not-quite-new version supplied with CentOS stream 8; I could try
> building a newer release, but do you think it would make any difference?
The shortcut setting is probably a bit misleading, because what it does, is to
simply focus the Locator input and set the text to the “prefix” for the locator
filter. You are right that the Files in All Project Directories and Files in
Any Project filters have the same prefix by default - this was for convenience
to have a prefix that shows “all files that are somehow related to all
projects”.
This probably doesn’t fit all possible use cases - as it doesn’t seem to fit
yours ;) . The good thing is that you can just change the prefix for the “Files
in All Project Directories” filter in the settings.
Br, Eike
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Fix line height?
Hi, this is [QTBUG-97818] Huge line spacing when font is Monaco https://bugreports.qt.io/browse/QTBUG-97818 Qt 6.2.3 is unfortunately not released yet. There are other mono-space fonts that are not affected though, that you can choose in Prefs > Text Editor > Font & Colors. (My personal favorite is SF Mono, the font used in Terminal. You need to install that globally first though, by opening the font files from /System/Applications/Utilities/Terminal.app/Contents/Resources/Fonts in the “Font Book” application.) Br, Eike > On 19 Jan 2022, at 20:04, Andy wrote: > > I just switched from QtC 5.0.1 to 6.0.2 and the line height is different. I > find it harder to read now. > > How do I fix it? I can't find any settings for this. > > Before (5.0.1): > > > > After (6.0.2): > > > > Thanks! > > --- > Andy Maloney // https://asmaloney.com > twitter ~ @asmaloney > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Qt creator latest version for Qt 5.15
> On 18 Jan 2022, at 17:12, Ramakanth Kesireddy wrote: > > Hi, > > Can you let me know latest Qt creator version compatible with Qt 5.15? Hi, you can use the latest available Qt Creator to develop your applications with Qt 5.15. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 7 feature freeze next week
This is a quick reminder that feature freeze for Qt Creator 7 is planned for next week: Qt Creator 7 * Feature freeze wk04 (~Jan 25 2022) * Beta release wk06 (~Feb 8 2022) * String freeze wk08 (~Feb 22 2022) * RC release wk10 (~Mar 8 2022) * Final release wk12 (~Mar 22 2022) https://wiki.qt.io/Qt_Creator_Releases -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Updating requirements for building Qt Creator 7+ (master branch)
Yes, the plan would also be to remove the plugin support files. Generally, most of the porting work is to add a CMakeLists.txt file with some CMake preamble and qtc_add_plugin, like described in https://doc-snapshots.qt.io/qtcreator-extending/first-plugin.html#cmake-project Linking to hunspell is not quite so straightforward though. I’ve added something at https://github.com/CJCombrink/SpellChecker-Plugin/pull/133 as a start. Br, Eike > On 15 Jan 2022, at 12:45, Carel Combrink wrote: > > Dear Eike, > > Thank you for the update > > > # Removing qmake as a build system for building Qt Creator itself > > Does this also include building Plugins? > Are there perhaps any guide or tips for plugin creators/mainters on how to > port their existing plugins from qmake to CMake? > > Kind regards, > Carel > Author of the Qt Creator SpellChecker-Plugin > > PS: Resent to include the mailing list, sorry about that -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Updating requirements for building Qt Creator 7+ (master branch)
# Bumping the required Qt version for building Qt Creator from Qt 5.14 to Qt 5.15.2. Qt 5.15.2 contains API that eases the transition to Qt 6. So far we added workarounds for Qt 5.14, that we could remove, and we then also don’t need to add more of them in new code. Regarding Linux distributions, Ubuntu 21 and Debian 11 seem to have Qt 5.15.2, and others too (https://pkgs.org/search/?q=qtbase) Bump requirement to Qt 5.15.2 (I920fdccc) · Gerrit Code Review https://codereview.qt-project.org/c/qt-creator/qt-creator/+/390103 # Removing qmake as a build system for building Qt Creator itself The CMake port is “done”, and official packages are built with CMake. The qmake build is basically untested, and maintaining it in addition is a burden. We also had a nice transitioning period of more than a year (Qt Creator 4.14 being the first version that was released based on the CMake build). Remove qmake build files (I846c6ef6) · Gerrit Code Review https://codereview.qt-project.org/c/qt-creator/qt-creator/+/390104 Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] QtCreator 6 - Line SPacing
Hi, you are most probably hitting this bug in Qt 6.2: [QTBUG-97818] Huge line spacing when font is Monaco - Qt Bug Tracker https://bugreports.qt.io/browse/QTBUG-97818 The only workaround is to choose a different font in Prefs > Text Editor > Fonts & Colors until a fixed version is released - it will be available in Qt 6.2.3 and then whatever Qt Creator version we will release based on that (my guess would be Qt Creator 6.0.2). (I personally like the “SF Mono” font that is used by Xcode and Terminal. You can install that for wider use by opening the “Font Book” app, open /System/Applications/Utilities/Terminal.app/Contents/Resources/Fonts/ , and dragging all the font files there onto Font Book. Will be available in Qt Creator next time you open it.) Br, Eike > On 9 Dec 2021, at 07:47, Denis Shlykov wrote: > > Hi! > > My QtCreator has been updated to version 6. I noticed that the line spacing > has increased and there is no way I can get it back and tweak. How can I > return the line spacing to the previous line spacing in a text editor? > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] clangd parsing time
Hi, I have got a fix for macOS (in LLVM), and a similar patch that _might_ improve things on Windows too https://codereview.qt-project.org/c/clang/llvm-project/+/382042 but since we fail to reproduce the huge difference between "compiling" and "clangd indexing" that you observe in the first place, we have a difficult time verifying that this indeed helps. We have created a build of clangd with the potential fix and I've uploaded it here: https://download.qt.io/development_releases/prebuilt/libclang/testing/ it would be great if you could test if this improves things for you. Set the path to the new clangd in Tools > Options > C++ > Clangd > Path to executable. Br, Eike > On Nov 9, 2021, at 15:26, Eike Ziller wrote: > > I can confirm on macOS, that Qt Creator in Qt Creator takes 2 1/2 hours to > index, on a machine that takes 12 minutes to build it. > clangd uses 12 threads by default, but only 4 out of 8 cores. Turning up the > number of "worker threads" does increase the number of threads used, but > doesn't increase the cores/CPU used and doesn't make indexing faster. > > The good thing is that the full indexing is only done once (cached per build > directory), and further updates just index what has changed. > > It seems to be known in principle in the Clangd project: > > clangd is keeping notify indexing and won't stop in Windows with Chromium · > Issue #643 · clangd/clangd > https://github.com/clangd/clangd/issues/643 > > and seems to be different on Linux. > > Br, Eike > >> On Nov 8, 2021, at 19:57, Adam Light wrote: >> >> Hi >> >> I'm using QtC 6.0.0-beta2 on Windows 10. >> >> I wanted to give clang a try so I enabled the "Use clangd" option. I have >> Enabled background indexing checked, worker thread count set to Automatic, >> and Document update threshold set to 500ms. >> >> I deleted all of the build directories for my project and then opened the >> project in Creator. After a few seconds a "Parsing C/C++ files (clangd)" >> popup appeared with a progress bar and file count. It shows that it needs to >> parse 3495 files. >> >> After having run for 15 minutes now, the popup says that 216 files have been >> parsed. >> >> Building a debug build of this qmake-based project on this Windows machine >> takes about 2 minutes. That is using the MSVC compiler, not clang. The >> machine has a 16 core/32 thread processor and 32GB RAM. Building the same >> project on an older Macintosh machine with 4 cores/8 threads takes about 5-6 >> minutes. In that case clang is the compiler. >> >> I collected some ETW traces and I verified that clangd is running in 16 >> threads. Unfortunately, the debug symbols for Creator >> (https://download.qt.io/development_releases/qtcreator/6.0/6.0.0-beta2/installer_source/windows_x64/qtcreator-debug.7z) >> do not include symbols for clangd, so I have no idea what the bottleneck is. >> >> I realize that clangd is considered experimental, but surely it's not this >> slow for others, right? If this isn't expected, I'm open to helping to debug >> what's going on, if someone has ideas about how to do so. >> >> Thanks >> Adam >> >> PS: As I am about to send this, it's been 26 minutes since parsing started, >> and it's finished only 375 files. >> ___ >> Qt-creator mailing list >> Qt-creator@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] clangd parsing time
> On Nov 10, 2021, at 15:13, Adam Light wrote: > > > > On Wed, Nov 10, 2021 at 12:12 AM Eike Ziller wrote: > >> Well, expected in the current state of clangd, though I'd say that it is a >> bug (and the issue for clangd is still "open", not rejected). >> Unfortunately it is something that we cannot directly fix in Qt Creator, >> though we can try to help the clangd people. >> > One of the responses said "If there's progress I would say everything is > working as expected...", so while it is open it doesn't seem that it's being > treated with any urgency. > > I don't use Linux so I can't test, but it seems that indexing is faster on > Linux? I'm curious to know how long it takes to index Creator's sources, if > you know. I can also confirm that it is much faster on Linux. In my Linux VM, with 4 cores, clangd uses 390% CPU and finishes in something like 45 minutes with the default worker thread setting, which is pretty exactly the time it takes to actually compile the same on that VM. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] clangd parsing time
> On Nov 9, 2021, at 21:31, Adam Light wrote: > >> On Tue, Nov 9, 2021 at 6:27 AM Eike Ziller wrote: >> I can confirm on macOS, that Qt Creator in Qt Creator takes 2 1/2 hours to >> index, on a machine that takes 12 minutes to build it. >> clangd uses 12 threads by default, but only 4 out of 8 cores. Turning up the >> number of "worker threads" does increase the number of threads used, but >> doesn't increase the cores/CPU used and doesn't make indexing faster. >> >> The good thing is that the full indexing is only done once (cached per build >> directory), and further updates just index what has changed. >> > Thanks. It seems like what I am seeing is more or less expected, I guess. Well, expected in the current state of clangd, though I'd say that it is a bug (and the issue for clangd is still "open", not rejected). Unfortunately it is something that we cannot directly fix in Qt Creator, though we can try to help the clangd people. > In the end it took 3 hours 54 minutes to finish parsing my project. Since the > parsing would need to be done separately for different configurations (e.g. > debug and release) and possibly after changes to the build configuration, I > wonder how useful using clangd will ever be. FWIW, I was exploring clangd due > to slow parsing of our project from the clang code model, reported at > https://bugreports.qt.io/browse/QTCREATORBUG-26327, but even the clang code > model doesn't take almost 4 hours to parse the project. To clarify a bit: The non-clangd indexer is not based on libclang/llvm, it is our own, self-written indexer that we already had before the ClangCodeModel. libclang does not support indexing. Even with clangd enabled in Qt Creator, we run our old indexer as a faster fallback solution until the clangd indexing has finished. So, so far the clangd indexing is just a "bonus" - even before it finishes, global searches etc are already enabled and done with our old indexer like without clangd, and after it finished the global searches use the more precise clangd indexer. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] clangd parsing time
I can confirm on macOS, that Qt Creator in Qt Creator takes 2 1/2 hours to index, on a machine that takes 12 minutes to build it. clangd uses 12 threads by default, but only 4 out of 8 cores. Turning up the number of "worker threads" does increase the number of threads used, but doesn't increase the cores/CPU used and doesn't make indexing faster. The good thing is that the full indexing is only done once (cached per build directory), and further updates just index what has changed. It seems to be known in principle in the Clangd project: clangd is keeping notify indexing and won't stop in Windows with Chromium · Issue #643 · clangd/clangd https://github.com/clangd/clangd/issues/643 and seems to be different on Linux. Br, Eike > On Nov 8, 2021, at 19:57, Adam Light wrote: > > Hi > > I'm using QtC 6.0.0-beta2 on Windows 10. > > I wanted to give clang a try so I enabled the "Use clangd" option. I have > Enabled background indexing checked, worker thread count set to Automatic, > and Document update threshold set to 500ms. > > I deleted all of the build directories for my project and then opened the > project in Creator. After a few seconds a "Parsing C/C++ files (clangd)" > popup appeared with a progress bar and file count. It shows that it needs to > parse 3495 files. > > After having run for 15 minutes now, the popup says that 216 files have been > parsed. > > Building a debug build of this qmake-based project on this Windows machine > takes about 2 minutes. That is using the MSVC compiler, not clang. The > machine has a 16 core/32 thread processor and 32GB RAM. Building the same > project on an older Macintosh machine with 4 cores/8 threads takes about 5-6 > minutes. In that case clang is the compiler. > > I collected some ETW traces and I verified that clangd is running in 16 > threads. Unfortunately, the debug symbols for Creator > (https://download.qt.io/development_releases/qtcreator/6.0/6.0.0-beta2/installer_source/windows_x64/qtcreator-debug.7z) > do not include symbols for clangd, so I have no idea what the bottleneck is. > > I realize that clangd is considered experimental, but surely it's not this > slow for others, right? If this isn't expected, I'm open to helping to debug > what's going on, if someone has ideas about how to do so. > > Thanks > Adam > > PS: As I am about to send this, it's been 26 minutes since parsing started, > and it's finished only 375 files. > _______ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] QtCreator don't display custom target in cmake project
> On Oct 28, 2021, at 12:50, kl222 wrote: > > Hello all: Hi, > > Qt Creator version: 4.15.0 > When I am use cmake project, In the Build>Build Step->Target, don't > display custom target. > The old version is ok. That was a regression that should be fixed in 4.15.1 and later: https://bugreports.qt.io/browse/QTCREATORBUG-25726 Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 6 string freeze, UI freeze and soft API freeze coming up
Now that it is about 2 weeks after the Qt Creator 6 Beta, the string freeze, UI freeze & soft API freeze is coming up. https://wiki.qt.io/Qt_Creator_Submission_Policies So let's go into string freeze et al on Friday (29.10.) this week. Qt Creator 6.0 * Feature freeze wk40 (~ Sep 28 2021) * Beta release wk42 (~ Oct 12 2021) * String freeze wk44 (~ Oct 26 2021) * RC release wk46 (~ Nov 9 2021) * Final release wk48 (~ Nov 23 2021) https://wiki.qt.io/Qt_Creator_Releases -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Clang Completion & Format
Hi, > On Oct 25, 2021, at 10:43, Björn Schäpers wrote: > > Hi, > > I'm using a self compiled LLVM (recent main with the format patch) and > QtCreator (d7c7089ff3ff2877fe89ac09cc2afa9a3da041c0). > > I'm not using clangd, but "plain" Clang Code Model and the Clang Format > Plugin. > > I've noticed that completion and highlighting is slower than it was in the > latest 4.x version. Did you compile LLVM in release mode? Otherwise I see that we apply https://code.qt.io/cgit/clang/llvm-project.git/commit/?h=release_130-based=9dabab650113687b3349e4a71eec1b1c223c4df9 "Cache preamble-related data" as well. > But the most annoying thing right now is that my code is not formatted > anymore while typing. Before the last modified lines were formatted when I > entered a ; or }, but now (with the same config) I have manually to start the > formatting and I have to select all the lines I want to format. There have been some changes there, maybe most notably ClangFormat: Sprinkle some more magic pixie dust (Ia78ecb9e) · Gerrit Code Review https://codereview.qt-project.org/c/qt-creator/qt-creator/+/336378 ClangFormat: Prevent adding/removing lines when indenting (Ida6e729f) · Gerrit Code Review https://codereview.qt-project.org/c/qt-creator/qt-creator/+/358178 and ClangFormat: Prepend a space character to our inserted line comment (Ic0b53586) · Gerrit Code Review https://codereview.qt-project.org/c/qt-creator/qt-creator/+/358190 Maybe something broke your case. > Do I have to change my configuration? Do I have to switch to clangd? My > understanding is that that's not complete yet. Clangd should be complete now in Qt Creator 6, and I'm using it for daily development. It can still have some rough edges here or there though. Not sure how it could help with your ClangFormat issue though. Br, Eike > Currently I sady have not the time to look into the sources to fix it myself. > > Kind regards, > Björn. > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Incremental Build after Version Bump
> On Oct 20, 2021, at 21:20, Björn Schäpers wrote: > > Hi, > > I'm compiling QtCreator from sources (with Qt5 and qmake on MinGW) and am > wondering what do I need to delete or invoke to get the correct version > number in the plugins (so that they can be loaded), if Creator's version is > bumped? Just as a side note, that just works when using CMake for building Qt Creator. (That is supposed to work with Qt 5 & MinGW as well.) Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 6 feature freeze next week
Qt Creator 6.0 is now in feature freeze. Final merge master -> 6.0 is done. The content of master branch will land in 7.0 from now on. 6.0 branch will continue to be merged into master branch as usual. Br, Eike > On Sep 28, 2021, at 09:55, Eike Ziller wrote: > > I have created the 6.0 branch(es). > > Please use 6.0 branch for changes that target the 6.0 release now. You can > use "Move change" from the vertical "…" menu in Gerrit to move existing > changes on Gerrit to the 6.0 branch before submitting them. > I'll do a last merge from master -> 6.0 on Thursday morning CEST. After that, > all changes that go into master branch will not be included in 6.0, but only > in 7.0. > Changes in 6.0 will continue to be merged to master as usual. > > Br, Eike > >> On Sep 20, 2021, at 08:56, Eike Ziller wrote: >> >> This is a quick reminder that the feature freeze of Qt Creator 6 is planned >> for next week: >> >> Qt Creator 6.0 >> >> * Feature freeze wk40 (~ Sep 28 2021) >> * Beta release wk42 (~ Oct 12 2021) >> * String freeze wk44 (~ Oct 26 2021) >> * RC release wk46 (~ Nov 9 2021) >> * Final release wk48 (~ Nov 23 2021) >> >> https://wiki.qt.io/Qt_Creator_Releases >> >> Br, Eike >> >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Erich-Thilo-Straße 10 >> D-12489 Berlin >> eike.zil...@qt.io >> http://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@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 6 feature freeze next week
I have created the 6.0 branch(es). Please use 6.0 branch for changes that target the 6.0 release now. You can use "Move change" from the vertical "…" menu in Gerrit to move existing changes on Gerrit to the 6.0 branch before submitting them. I'll do a last merge from master -> 6.0 on Thursday morning CEST. After that, all changes that go into master branch will not be included in 6.0, but only in 7.0. Changes in 6.0 will continue to be merged to master as usual. Br, Eike > On Sep 20, 2021, at 08:56, Eike Ziller wrote: > > This is a quick reminder that the feature freeze of Qt Creator 6 is planned > for next week: > > Qt Creator 6.0 > > * Feature freeze wk40 (~ Sep 28 2021) > * Beta release wk42 (~ Oct 12 2021) > * String freeze wk44 (~ Oct 26 2021) > * RC release wk46 (~ Nov 9 2021) > * Final release wk48 (~ Nov 23 2021) > > https://wiki.qt.io/Qt_Creator_Releases > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 6 feature freeze next week
This is a quick reminder that the feature freeze of Qt Creator 6 is planned for next week: Qt Creator 6.0 * Feature freeze wk40 (~ Sep 28 2021) * Beta release wk42 (~ Oct 12 2021) * String freeze wk44 (~ Oct 26 2021) * RC release wk46 (~ Nov 9 2021) * Final release wk48 (~ Nov 23 2021) https://wiki.qt.io/Qt_Creator_Releases Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] 5.0 RC segfaults when loading compilation db project
Hi, > On Aug 16, 2021, at 16:51, Nikos Chantziaras wrote: > > The 5.0 RC (installed through online installer) segfaults on Linux with > loading a project based on a compile_commands.json file. Trying to get a > backtrace with gdb is not very useful, since there's no debug symbols. The > online installer does not have a download for the debug symbols, like it does > for Creator 4.15.2 (which does not segfault.) Indeed looks like debug info for the pre-release is missing from the online installer. Looks like that was simply forgotten. Created https://bugreports.qt.io/browse/QTCREATORBUG-26130 > So, how do I report this bug? The debug information is available at https://download.qt.io/development_releases/qtcreator/5.0/5.0.0-rc1/installer_source/linux_x64/ (qtcreator-debug.7z). If you unzip that into your Qt Creator installation, you should get better stack traces. Maybe it is better if you create a copy of /Tools/Preview/Qt Creator 5.0.0-rc1 for that purpose, so you don't end up with funny files in your online installation that the online installer knows nothing about (and does not clean up when updates come in). Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] edit - qml and mm files - look disabled
> On Jul 5, 2021, at 16:48, ekke wrote:
>
> Hi Eike,
> looked at it a 2nd time before opening a Bugreport.
>
> you're right about the *.mm files - they are disasbled on Android and enabled
> on iOS
>
> but the *.qml files are always disabled (macOS, Android, iOS)
>
> In my .pro the qml files are not placed under +SOURCES - only in a special
> case:
> lupdate_only {
> SOURCES += qml/main.qml \
> qml/common/*.qml \
> qml/navigation/*.qml \
> qml/pages/*.qml \
> qml/popups/*.qml \
> qml/tabs/*.qml
> }
>
> hase there anything changed with QtC 4.15.1 and Qt 5.15 ?
> has worked last years for me without disabling qml files
Not with the categorization in that regard, not that I know of. But, if you
have the qml files in an lupdate_only scope, they will probaby appear twice in
the tree: Once under the node of the QRC file, and once individually.
If the qml files under the QRC file node are now deeper in the tree than the
qml files from the lupdate_only scope, then I think the latter will be selected
when synchronizing the selection in the project tree with the current document.
That kind of prioritization changed recently I think.
Btw, as far as I know, the need to specify qml files in SOURCES for lupdate is
gone since Qt 5.6:
lupdate: Add qrc resource file support (Id7f95248) · Gerrit Code Review
https://codereview.qt-project.org/c/qt/qttools/+/122940
Br, Eike
>
> thx
> ekke
>
> Am 05.07.21 um 10:47 schrieb Eike Ziller:
>> Qt Creator shows files as disabled if it thinks that they are not part of
>> the current build (e.g. platform, guarded with some qmake scope like
>> “macos:OBJECTIVE_SOURCES+=foo.mm” but building on Windows).
>> If that is not the case, please consider creating a bug report with details (
>> https://bugreports.qt.io/projects/QTCREATORBUG
>> ).
>> Br, Eike
>>
>>
>>> On Jun 28, 2021, at 10:34, ekke
>>> wrote:
>>>
>>> Hi, I'm using QtC 5.14.1
>>>
>>> In Edit Mode if I open a folder like
>>>
>>> sources - qml - pages
>>>
>>> then all entries are listed in grey - like disabled. Only the current file
>>> opened in TextEditor is normal (black).
>>>
>>> sources - cpp and others are always displayed normal (black)
>>>
>>> same behavior with grey listed files is for iOS .mm files
>>>
>>> is there a way to change this ?
>>>
>>> ekke
>>>
>>> ___
>>> Qt-creator mailing list
>>>
>>> Qt-creator@qt-project.org
>>> https://lists.qt-project.org/listinfo/qt-creator
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] edit - qml and mm files - look disabled
Qt Creator shows files as disabled if it thinks that they are not part of the current build (e.g. platform, guarded with some qmake scope like “macos:OBJECTIVE_SOURCES+=foo.mm” but building on Windows). If that is not the case, please consider creating a bug report with details (https://bugreports.qt.io/projects/QTCREATORBUG). Br, Eike > On Jun 28, 2021, at 10:34, ekke wrote: > > Hi, I'm using QtC 5.14.1 > > In Edit Mode if I open a folder like > > sources - qml - pages > > then all entries are listed in grey - like disabled. Only the current file > opened in TextEditor is normal (black). > > sources - cpp and others are always displayed normal (black) > > same behavior with grey listed files is for iOS .mm files > > is there a way to change this ? > > ekke > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 5 feature freeze next week (22.6.)
Last merge master -> 5.0 has been done. Content in master branch will now become 6.0. The usual merges 4.15 -> 5.0 -> master will continue to happen of course. The 5.0 Beta release is scheduled for in 2 weeks. Br, Eike > On Jun 22, 2021, at 15:04, Eike Ziller wrote: > > I have created to 5.0 branch(es) now. > > Please start targeting the 5.0 branch for things that should end up in 5.0. > I’ll do a last merge from master->5.0 tomorrow “end of business”, after that > all content in master branch are for 6.0. > > You can change the target of existing patches on Gerrit/codereview with the > vertical “…” menu on the top-right, “Move change”. > > Br, Eike > >> On Jun 15, 2021, at 09:03, Eike Ziller wrote: >> >> This is a reminder to Qt Creator developers that feature freeze of Qt >> Creator 5 is planned for next week: >> >> https://wiki.qt.io/Qt_Creator_Releases >> >> Qt Creator 5.0 >> >> * Feature freeze wk26 (~ Jun 22 2021) >> * Beta release wk28 (~ Jul 6 2021) >> * String freeze wk30 (~ Jul 20 2021) >> * RC release wk32 (~ Aug 3 2021) >> * Final release wk34 (~ Aug 17 2021) >> >> Br, Eike >> >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Erich-Thilo-Straße 10 >> D-12489 Berlin >> eike.zil...@qt.io >> http://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@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Qt Creator 5 feature freeze next week (22.6.)
I have created to 5.0 branch(es) now. Please start targeting the 5.0 branch for things that should end up in 5.0. I’ll do a last merge from master->5.0 tomorrow “end of business”, after that all content in master branch are for 6.0. You can change the target of existing patches on Gerrit/codereview with the vertical “…” menu on the top-right, “Move change”. Br, Eike > On Jun 15, 2021, at 09:03, Eike Ziller wrote: > > This is a reminder to Qt Creator developers that feature freeze of Qt Creator > 5 is planned for next week: > > https://wiki.qt.io/Qt_Creator_Releases > > Qt Creator 5.0 > > * Feature freeze wk26 (~ Jun 22 2021) > * Beta release wk28 (~ Jul 6 2021) > * String freeze wk30 (~ Jul 20 2021) > * RC release wk32 (~ Aug 3 2021) > * Final release wk34 (~ Aug 17 2021) > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Dev: Qt Creator 5 feature freeze next week (22.6.)
This is a reminder to Qt Creator developers that feature freeze of Qt Creator 5 is planned for next week: https://wiki.qt.io/Qt_Creator_Releases Qt Creator 5.0 * Feature freeze wk26 (~ Jun 22 2021) * Beta release wk28 (~ Jul 6 2021) * String freeze wk30 (~ Jul 20 2021) * RC release wk32 (~ Aug 3 2021) * Final release wk34 (~ Aug 17 2021) Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Unable to Compile QtCreator (4.15)
~~
> [ 90s] clangrefactoringplugin.cpp:96:78: error: cannot convert
> '' to 'int' in initialization
> [ 90s]96 | SymbolQuery
> symbolQuery{statementFactory};
> [ 90s] |
>^
> [ 90s] clangrefactoringplugin.cpp:98:107: error: could not convert
> '{((ClangRefactoring::ClangRefactoringPluginData*)this)->ClangRefactoring::ClangRefactoringPluginData::connectionClient.ClangBackEnd::RefactoringConnectionClient::serverProxy(),
>
> ((ClangRefactoring::ClangRefactoringPluginData*)this)->ClangRefactoring::ClangRefactoringPluginData::refactoringClient,
>
> ((ClangRefactoring::ClangRefactoringPluginData*)this)->ClangRefactoring::ClangRefactoringPluginData::filePathCache,
>
> ((ClangRefactoring::ClangRefactoringPluginData*)this)->ClangRefactoring::ClangRefactoringPluginData::symbolQuery}'
> from '' to
> 'ClangRefactoring::RefactoringEngine'
> [ 90s]98 | RefactoringEngine engine{connectionClient.serverProxy(),
> refactoringClient, filePathCache, symbolQuery};
> [ 90s] |
> ^
> [ 90s] |
> |
> [ 90s] |
> list>
>
>
> Le 23/02/2021 à 17:00, Michael Jackson a écrit :
>>
>> Cool Thanks for the information and steps. I did all steps and patched
>> the code to successfully compile on my end. I created a new branch and
>> pushed that branch to my fork on GitHub (github.com/imikejackson). I
>> also updated the cmake.yml build matrix to also build the
>> clangrefactoringplugin? I’ll check back later this afternoon to
> see if
>> a GitHub action performed the build?
>>
>>
>>
>> --
>>
>> Mike Jackson
>>
>>
>>
>> *From: *Cristian Adam
>> *Date: *Tuesday, February 23, 2021 at 10:41 AM
>> *To: *Michael Jackson , Qt-creator
>>
>> *Subject: *Re: [Qt-creator] Unable to Compile QtCreator (4.15)
>>
>>
>>
>> On 23/02/2021 16:25, Michael Jackson wrote:
>>
>>Oh. Should I not be compiling those plugins? I liked having them around
>> in earlier releases of QtCreator. On a related note is there a web site that
>> shows the results of CI builds and their configurations? Or a place I can
>> submit a build? Would that be the Gerrit site?
>>
>>
>>
>> We have GitHub Actions enabled at
>> https://github.com/qt-creator/qt-creator/actions
>> <https://github.com/qt-creator/qt-creator/actions>
>>
>> If you have a GitHub account you can:
>>
>> 1. Fork https://github.com/qt-creator/qt-creator
>><https://github.com/qt-creator/qt-creator>
>> 2. Add your GitHub fork to your Qt Creator git checkout
>>$ git remote add github https://github.com/
>><https://github.com/>/qt-creator.git
>> 3. Push to your GitHub fork
>>$ git push github --force
>>
>> Your GitHub fork will get its own build of Qt Creator. The build is
>> ccache backed, and after the cache is warm, a build should take ~30
>> minutes. You also get build artifacts for Linux, Window and macOS.
>>
>> Cheers,
>> Cristian.
>>
>>
>> ___
>> Qt-creator mailing list
>> Qt-creator@qt-project.org
>> https://lists.qt-project.org/listinfo/qt-creator
>
>
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Debugging app using Camera on MacOS?
> On May 19, 2021, at 15:36, Jason H wrote:
>
> Ok, I have that rule too, but does it re-invoke make after updating? It seems
> to continue to process the old, out of date Makefile?
> After
> $(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
> It either needs to say something like:
> Makefile updated; run make again
> or:
> make
> So:
>$(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
>make
>
> True there is some risk of an infinite loop if the make `touch`es the
> Makefile, to maybe there is a way to compare hashes?
Make supposedly supports re-creating the Makefile in a rule:
https://www.gnu.org/software/make/manual/html_node/Remaking-Makefiles.html
"If a makefile has a rule which says how to update it (found either in that
very makefile or in another one) or if an implicit rule applies to it (see
Using Implicit Rules), it will be updated if necessary. After all makefiles
have been checked, if any have actually been changed, make starts with a clean
slate and reads all the makefiles over again.”
So it sees the rule for “Makefile: ….”, executes it if required, checks if the
Makefile changed, and restarts itself if so.
>
>
>
>> Sent: Wednesday, May 19, 2021 at 3:34 AM
>> From: "Eike Ziller"
>> To: "Jason H"
>> Cc: "qt-creator"
>> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
>>
>>
>>
>>> On May 18, 2021, at 18:58, Jason H wrote:
>>>
>>>
>>> So I am dumb. I forgot that among all those popups QtCreator gives you when
>>> you save the .pro, running qmake is not one of them
>>> I *thought* running qmake would have been automatic when the .pro changes.
>>> (Or that the Makefile would pick up the .pro was modified and run qmake
>>> automatically) but that doesn't seem to be the case?
>>>
>>
>> The Makefile _should_ have a rule for re-running qmake when the .pro file is
>> changed. My dummy project has
>>
>> Makefile: ../qmake_widgets/qmake_widgets.pro ……
>> ...
>> $(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
>>
>> Which is tricky because while running “make”, the Makefile is changed…. but
>> it is supposed to work.
>>
>> Br, Eike
>>
>>>
>>> Sent: Tuesday, May 18, 2021 at 11:53 AM
>>> From: "Jason H"
>>> To: "Jason H"
>>> Cc: "qt-creator"
>>> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
>>> Accidentally only replied to Lars before, but for the list, for throughness:
>>> Thanks Lars.
>>>
>>> I have added in the .pro
>>> mac {
>>>QMAKE_INFO_PLIST = macos/Info.plist
>>> }
>>>
>>>
>>> And the plist was copied from the build directory, added the key/string
>>> pair:
>>> NSCameraUsageDescription
>>> Reads Barcodes
>>>
>>> And still no joy. The Info.plist in the package contents is not the one
>>> with the added key.
>>> I tried mac, macx, and macos for the platform in .pro. QtCreator shows int
>>> he Project pane:
>>> Other Files /
>>> .. v macos
>>> Info.plist
>>>
>>> So the file is there. It's just not being used. I have NOT set CONFIG -=
>>> app_bundle. Looking at the compile output, Info.plist does not appear in
>>> the compile output pane.
>>>
>>> It seems that something else is needed than QMAKE_INFO_PLIST?
>>>
>>> ...
>>> ANSWER: Yes it needs a manual copy (currently). Then I filed
>>> https://bugreports.qt.io/browse/QTBUG-93832
>>>
>>>
>>> Sent: Tuesday, May 18, 2021 at 11:25 AM
>>> From: "Jason H"
>>> To: "Lars Knoll"
>>> Cc: "qt-creator"
>>> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
>>> I got it working with a manual copy, but also filed:
>>> https://bugreports.qt.io/browse/QTBUG-93832
>>>
>>>
>>>
>>> Sent: Tuesday, May 18, 2021 at 4:40 AM
>>> From: "Lars Knoll"
>>> To: "Eike Ziller"
>>> Cc: "Jason H" , "qt-creator"
>>> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
>>> On 17 May 2021, at 18:50, Eike Ziller wrote:
>>> On May 17, 2021, at 16:27, Jason H wrote:
>>>
>>> Here is the question (asked by someone else) (Note this is specific to
>>> *debugging* the app.)
>>> https://stacko
Re: [Qt-creator] Debugging app using Camera on MacOS?
> On May 18, 2021, at 18:58, Jason H wrote:
>
>
> So I am dumb. I forgot that among all those popups QtCreator gives you when
> you save the .pro, running qmake is not one of them
> I *thought* running qmake would have been automatic when the .pro changes.
> (Or that the Makefile would pick up the .pro was modified and run qmake
> automatically) but that doesn't seem to be the case?
>
The Makefile _should_ have a rule for re-running qmake when the .pro file is
changed. My dummy project has
Makefile: ../qmake_widgets/qmake_widgets.pro ……
...
$(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
Which is tricky because while running “make”, the Makefile is changed…. but it
is supposed to work.
Br, Eike
>
> Sent: Tuesday, May 18, 2021 at 11:53 AM
> From: "Jason H"
> To: "Jason H"
> Cc: "qt-creator"
> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> Accidentally only replied to Lars before, but for the list, for throughness:
> Thanks Lars.
>
> I have added in the .pro
> mac {
> QMAKE_INFO_PLIST = macos/Info.plist
> }
>
>
> And the plist was copied from the build directory, added the key/string pair:
> NSCameraUsageDescription
> Reads Barcodes
>
> And still no joy. The Info.plist in the package contents is not the one with
> the added key.
> I tried mac, macx, and macos for the platform in .pro. QtCreator shows int he
> Project pane:
> Other Files /
> .. v macos
> Info.plist
>
> So the file is there. It's just not being used. I have NOT set CONFIG -=
> app_bundle. Looking at the compile output, Info.plist does not appear in the
> compile output pane.
>
> It seems that something else is needed than QMAKE_INFO_PLIST?
>
> ...
> ANSWER: Yes it needs a manual copy (currently). Then I filed
> https://bugreports.qt.io/browse/QTBUG-93832
>
>
> Sent: Tuesday, May 18, 2021 at 11:25 AM
> From: "Jason H"
> To: "Lars Knoll"
> Cc: "qt-creator"
> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> I got it working with a manual copy, but also filed:
> https://bugreports.qt.io/browse/QTBUG-93832
>
>
>
> Sent: Tuesday, May 18, 2021 at 4:40 AM
> From: "Lars Knoll"
> To: "Eike Ziller"
> Cc: "Jason H" , "qt-creator"
> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> On 17 May 2021, at 18:50, Eike Ziller wrote:
> On May 17, 2021, at 16:27, Jason H wrote:
>
> Here is the question (asked by someone else) (Note this is specific to
> *debugging* the app.)
> https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
> with no good resolution.
>
> It seems the way QtC is launching the debugger is running afoul of the
> NSCameraUsageDescription. Has anyone else figured out a way around this?
> I'm wondering if the Info.plist needs to be applied to LLDB somehow?
>
> I don’t quite understand if this is a Qt Creator specific issue or not.
>
> If the issue is that Qt Creator starts lldb, and lldb starts the app, maybe
> running the app without debugging and then Debug > Start debugging > Attach
> to running application helps.
>
> I’ve been doing some debugging of the camera on macOS lately. You do need to
> add the Info.plist with NSCameraUsageDescription/NSMicrophoneUsageDescription
> to your app to allow camera/microphone access.
>
> After that, you might get a confirmation dialog to allow access on first
> launch. Once that’s confirmed, you should be able to debug the app just fine.
> At least it does work for me using Qt Creator.
>
> Cheers,
> Lars
>
> ___ Qt-creator mailing list
> Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://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@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Question about "Fetch data dynamically" option in new file wizard
> On May 18, 2021, at 09:11, Christian Stenger wrote: > > seems like this is provided only for QAbstractItemModel based classes.. I'd > say this is wrong and will be fixed. > https://codereview.qt-project.org/c/qt-creator/qt-creator/+/349648 > BR, > Christian > > > From: Qt-creator on behalf of Murphy, > Sean > Sent: Wednesday, May 12, 2021 3:58 PM > To: Qt-creator@qt-project.org > Subject: [Qt-creator] Question about "Fetch data dynamically" option in new > file wizard > > I'm creating a model class for a large table, so I would like to use lazy > loading. > > 1. In Qt Creator, I right-click my project and select the "Add New..." option. > 2. In the new file creation wizard that pops up, I select the "Qt" option from >the "Files and Classes" list, and then select the "Qt Item Model", then > pressed >the "Choose..." button. > 3. On the next page, I enter my desired class name, select > "QAbstractTableModel" >as the base class and then ensure the "Customize header row" and >"Fetch data dynamically" checkboxes are checked. > 4. I then completed the remaining steps in the wizard. > > In the resulting class's header file, I only ended up with these functions > defined for me: >explicit viewRawDataTableModel(QObject *parent = nullptr); >QVariant headerData(int section, Qt::Orientation orientation, int role = > Qt::DisplayRole) const override; >int rowCount(const QModelIndex = QModelIndex()) const override; >int columnCount(const QModelIndex = QModelIndex()) const override; >QVariant data(const QModelIndex , int role = Qt::DisplayRole) const > override; > > I kind of expected that in addition to those functions above, the process > would have also added functions like: > virtual bool canFetchMore(const QModelIndex ) const; > virtual void fetchMore(const QModelIndex ); > > Is this a bug, or am I just misunderstanding what that "Fetch data > dynamically" checkbox > is supposed to do when generating a new class? > > Qt Creator 4.14.2 > > Sean > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Debugging app using Camera on MacOS?
> On May 17, 2021, at 16:27, Jason H wrote: > > Here is the question (asked by someone else) (Note this is specific to > *debugging* the app.) > https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera > with no good resolution. > > It seems the way QtC is launching the debugger is running afoul of the > NSCameraUsageDescription. Has anyone else figured out a way around this? > I'm wondering if the Info.plist needs to be applied to LLDB somehow? I don’t quite understand if this is a Qt Creator specific issue or not. If the issue is that Qt Creator starts lldb, and lldb starts the app, maybe running the app without debugging and then Debug > Start debugging > Attach to running application helps. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Offline installer of 4.15 fails with no network connection
This has been reported here: [QTIFW-] QtCreator cannot be installed without Internet connection - Qt Bug Tracker https://bugreports.qt.io/browse/QTIFW- Br, Eike > On May 11, 2021, at 21:25, Robert Löhning wrote: > > Am 11.05.21 um 20:24 schrieb Adam Light: >> I downloaded the offline installer of Creator 4.15 ( >> https://download.qt.io/official_releases/qtcreator/4.15/4.15.0/qt-creator-opensource-windows-x86_64-4.15.0.exe) >> and moved it to a machine without internet access. When I run the >> installer, I see this: >> [image: image.png] >> How is "...or continue without internet connection" supposed to work when >> the Next button is disabled? >> Also, it is not very helpful to have the "Qt Installer FAQ" link to a >> remote web page (https://wiki.qt.io/Ifw_FAQ) when there is no network >> connection in the first place. >> Is it now a requirement to have a live network connection to install Qt >> Creator? If so, that conflicts with this sentence at the link given above: >> "Offline installer will try to connect to internet at startup, but if >> connection is not found you can still continue installation." >> Thanks >> Adam > > Hi Adam, > > could you please report this issue on https://bugreports.qt.io so progress > can be tracked there? Project "Qt Creator", Component "Installer". > > As a workaround, please: > 1. Install Creator on a machine _with_ internet connection. > 2. Copy the file %appdata%\Qt\qtaccount.ini from that machine to the same > directory on the machine _without_ internet connection. > 3. Start the installer on the machine _without_ internet connection. > > I hope this helps. Sorry for the inconvenience. > > Cheers, > Robert > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Turn off "suggest-override" clang-tidy warning?
> On May 11, 2021, at 02:36, Andy wrote: > > Thanks Eike. > > The project is based on Qt 5.15.2. ClangCodeModel is on. > > I have it set in the Analyzer prefs to "Analyze open files". Both clang-tidy > & clazy point to the executables in QtCreator.app. > > When I run "clang-tidy & clazy" manually through the Debug tab, it shows: > > warning: 'metaObject' overrides a member function but is not marked > 'override' [suggest-override] > warning: 'qt_metacall' overrides a member function but is not marked > 'override' [suggest-override] > warning: 'qt_metacast' overrides a member function but is not marked > 'override' [suggest-override] > > And the tooltip on them has the link from my first email. > > But it doesn't show the warning inline in the editor on the Q_OBJECT line. > (I'm fairly sure it was showing those when I reported it? I don't know - I'm > sleep deprived.) We suppress these warnings in the clang code model, because Qt only started suppressing these warnings in some Qt 5.x version. https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/clangcodemodel/clangdiagnosticfilter.cpp#n59 > Adding "-Wno-suggest-override" to analyzer's Clang Warnings DOES fix it, so > thank you! Still don't understand where it's coming from though. It looks like Clang got this new warning (that already existed for GCC) in Clang 11 (which we ship with Qt Creator). Q_OBJECT seems to only suppress suggest-override for GCC though: https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/kernel/qobjectdefs.h?h=5.15#n155 I fail to reproduce this warning here though. > I'm also confused why we have Clang Warning "Diagnostic Configurations" under > both the "C++ -> Code Model" and "Analyzer". So you could have a small, most important set of clang warnings for the code model, and a wider set of clang warnings when you trigger the Analyzer manually. Br, Eike > > --- > Andy Maloney // https://asmaloney.com > twitter ~ @asmaloney > > > > On Mon, May 10, 2021 at 2:58 AM Eike Ziller wrote: > > > > On May 7, 2021, at 23:26, Andy wrote: > > > > How do I turn off the "suggest-override" tidy warning? The tooltip for it > > points at a non-existent clang-tidy page: > > > > > > https://releases.llvm.org/11.0.0/tools/clang/tools/extra/docs/clang-tidy/checks/suggest-override.html > > > > It is triggered by every use of Q_OBJECT. > > Do you have a bit more information? > Are you using an old Qt version? I remember Q_OBJECT triggering override > related compilation warnings once upon a time. > Does it go away if you remove all clang-tidy and clazy checks? > I wonder if this isn’t actually a compiler warning from clang (the clang code > model, -Wsuggest-override). Does adding -Wno-suggest-override to the _clang > warnings_ help? > Though I wonder how Qt Creator comes up with that URL above. > > Br, Eike > > > > > The only clang-tidy option I can find relating to overrides is called > > "modernize-use-override" which I have turned off. > > > > > > https://releases.llvm.org/11.0.0/tools/clang/tools/extra/docs/clang-tidy/checks/modernize-use-override.html > > > > Using the clang-tidy included with Qt Creator 4.15 > > macOS 10.14.6 > > > > --- > > Andy Maloney // https://asmaloney.com > > twitter ~ @asmaloney > > > > ___ > > Qt-creator mailing list > > Qt-creator@qt-project.org > > https://lists.qt-project.org/listinfo/qt-creator > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Jouni Lintunen > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, > HRB 144331 B > -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Turn off "suggest-override" clang-tidy warning?
> On May 7, 2021, at 23:26, Andy wrote: > > How do I turn off the "suggest-override" tidy warning? The tooltip for it > points at a non-existent clang-tidy page: > > > https://releases.llvm.org/11.0.0/tools/clang/tools/extra/docs/clang-tidy/checks/suggest-override.html > > It is triggered by every use of Q_OBJECT. Do you have a bit more information? Are you using an old Qt version? I remember Q_OBJECT triggering override related compilation warnings once upon a time. Does it go away if you remove all clang-tidy and clazy checks? I wonder if this isn’t actually a compiler warning from clang (the clang code model, -Wsuggest-override). Does adding -Wno-suggest-override to the _clang warnings_ help? Though I wonder how Qt Creator comes up with that URL above. Br, Eike > > The only clang-tidy option I can find relating to overrides is called > "modernize-use-override" which I have turned off. > > > https://releases.llvm.org/11.0.0/tools/clang/tools/extra/docs/clang-tidy/checks/modernize-use-override.html > > Using the clang-tidy included with Qt Creator 4.15 > macOS 10.14.6 > > --- > Andy Maloney // https://asmaloney.com > twitter ~ @asmaloney > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Android AVD/SDK manager integration issue
Probably the output of the tool has changed and Qt Creator chokes on it…. https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/android/androidsdkmanager.cpp#n1026 looks very fancy. Of course it should preferably not lock up, and it would be better if it told the user to run that manually in the worst case, if our fancy parsing fails. I’ve created https://bugreports.qt.io/browse/QTCREATORBUG-25667 Br, Eike > On May 3, 2021, at 18:02, Jason H wrote: > > I'm trying to set up android for Qt, and QtC is doing great at it, but it > tells me that it's missing packages, which it then attempts to > download(awesome!) > > But it never gets past the "Checking pending licenses..." step. The progress > bar gets to the right, and nothing happens. > > Instead, I install these from Android Studio, I hit "cancel" and it picks up > that AS installed them and works. > > This is on Mac with AS 4.1.3 > > > > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] QtCreator Markdown Plugin
utside Qt > Creator. > I think litehtml should suffice to display the html rendered by a markdown > parser. > > Cheers, > Cristian. > > On 19/03/2021 09:17, ahmet erdinc yilmaz wrote: >> Hi all, >> >> I have been developing a markdown plugin for QtCreator. I think it is time >> to announce :-). You can reach from >> https://github.com/erdinc09/MarkdownEditView. >> >> I also published releases for all three platforms. I hope you like it. >> >> Features: >> • Syntax highlighting in editor >> • Html preview >> • Code highlighting in preview >> • Theme aware preview and editor >> • Bidirectional vertical scroll synchronization between editor and >> preview >> >> Dark Theme: >> >> >> >> Classic Theme: >> >> >> I have already announced it on the forum.qt.io. >> >> Best regards, >> >> // Erdinç >> >> >> ___ >> Qt-creator mailing list >> >> Qt-creator@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Qt Creator 4.15 in string freeze
With the Qt Creator 4.15 beta2 released, we also go into string freeze with 4.15 now. This includes UI freeze and soft API freeze as well. https://wiki.qt.io/Qt_Creator_Releases https://wiki.qt.io/Qt_Creator_Submission_Policies Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Switching to more "semantic" versioning scheme
> On Mar 25, 2021, at 09:25, Dmitriy Purgin wrote: > > Hi, > > have you considered a date-based versioning scheme? It would have practically > the same features as the proposed one, but additionally carries the > information how old a particular Qt Creator version is. Yes that was another option under discussion. See also https://bugreports.qt.io/browse/QTCREATORBUG-25486 . A date-based versioning scheme does not carry any information about compatibility (not more than we already had, at least). Granted, that is only relevant to a minority of plugin developers. Another reason is that Qt Creator would be the odd one with date-based versioning in the Qt Project realm. Changing Qt Creator to actual semantic versioning is basically bringing Qt Creator to the same versioning _scheme_. Br, Eike > > Cheers > Dmitriy > > On Wed, Mar 24, 2021 at 10:06 AM Eike Ziller wrote: > We want to switch Qt Creator to semantic versioning, which means bumping the > major version for each feature release, since we don’t keep binary > compatibility between these. > > - Next release after 4.15 is Qt Creator 5. > - Followed by Qt Creator 6 in December 2021. > - Qt Creator 7 in spring 2022 > - and so on. > > The major version of Qt Creator doesn’t have any meaning at the moment, so > we’d like to give it one. We almost always do incremental changes instead of > major overhauls in one go, so basing the major version on some kind of > feature change doesn’t make much sense. Bumping the major version for each > feature release sounds more sensible because of this, and fits the semantic > versioning scheme. > > Bump version to 5.0 beta1 (Id8510dd7) · Gerrit Code Review > https://codereview.qt-project.org/c/qt-creator/qt-creator/+/339992 > > changes the version used in the master branch. > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Switching to more "semantic" versioning scheme
> On Mar 24, 2021, at 21:38, Pablo Rogina wrote: > >> Using Qt version numbers as a base for Qt Creator version numbers creates an >> impression of coupling between Qt Creator and Qt that does not exist. > > Yes, you're right. But it's absolutely amazing how people in the Qt > Forum immediately replies with the Qt Creator version when asked about > what Qt version they're using. Yes. That makes it even more important to have distinct version numbers for Qt and for Qt Creator. If they say that they use 8.0.2 it’s easier to realize that this is a Qt Creator version and not a Qt version and they are actually using Qt 5.12, than if they say 6.0.1 but actually use Qt 5.12. Br, Eike > Pablo > > On Wed, Mar 24, 2021 at 12:11 PM Eike Ziller wrote: >> >> >>> On Mar 24, 2021, at 15:18, Jason H wrote: >>> >>>> Sent: Wednesday, March 24, 2021 at 5:05 AM >>>> From: "Eike Ziller" >>>> To: "qt-creator" >>>> Subject: [Qt-creator] Switching to more "semantic" versioning scheme >>>> >>>> We want to switch Qt Creator to semantic versioning, which means bumping >>>> the major version for each feature release, since we don’t keep binary >>>> compatibility between these. >>>> >>>> - Next release after 4.15 is Qt Creator 5. >>>> - Followed by Qt Creator 6 in December 2021. >>>> - Qt Creator 7 in spring 2022 >>>> - and so on. >>> >>> Though I understand the reasoning, I think this would be confusing. >>> Qt Creator has definite impact on Qt code, w.r.t. parsing. I'm thinking of >>> how many >>> releases it took QtC to support QML Enums. >> >> Hi, >> >> this has nothing to do with the Qt version that was used to build Qt Creator >> with. >> >>> I think a more meaningful system would >>> be to version it with the Qt build version, with the Z (x.y.z) being the >>> Qt Creator release with Qt version x.y. >> >> The Qt version that was used to build Qt Creator is mostly irrelevant for >> its functionality. >> Qt Creator built with Qt 5.14 has the same functionality as built with Qt >> 5.15, and after we finished support for building Qt Creator with Qt 6, that >> will still have the same functionality as Qt Creator built with Qt 5.15 or >> 5.14. We don’t need to build Qt Creator with Qt 6 to support Qt 6, and >> building Qt Creator with Qt 6 is no advantage for supporting Qt 6. >> >> Using Qt version numbers as a base for Qt Creator version numbers creates an >> impression of coupling between Qt Creator and Qt that does not exist. >> >> Additionally there are 3 Qt Creator “feature” releases per year, whereas >> there are 2 Qt minor releases. >> >>> Examples: >>> Qt Creator 5.15.4 (5th release based on Qt 5.15.2) >>> Qt Creator 6.0.1. (2nd release based on 6.0) >>> >>> Compared to: >>> Qt Creator 7 in 2022, >>> Qt Creator 9 in 2023, >>> Qt Creator 13 in 2025, >>> Qt Creator 23 in 2030. >>> Qt Creator 33 in 2040. >>> >>> >>> Or maybe no one cares about the QtCreator Qt built-with version? And maybe >>> I shouldn't care either? >>> I just always wonder "What is an appropriate version of QtC to be using >>> with Qt x.y?" >> >> Usually the latest Qt Creator has best support for latest Qt, and for >> previous Qt versions as well. >> >> Br, Eike >> >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Erich-Thilo-Straße 10 >> D-12489 Berlin >> eike.zil...@qt.io >> http://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@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Switching to more "semantic" versioning scheme
> On Mar 24, 2021, at 15:18, Jason H wrote: > >> Sent: Wednesday, March 24, 2021 at 5:05 AM >> From: "Eike Ziller" >> To: "qt-creator" >> Subject: [Qt-creator] Switching to more "semantic" versioning scheme >> >> We want to switch Qt Creator to semantic versioning, which means bumping the >> major version for each feature release, since we don’t keep binary >> compatibility between these. >> >> - Next release after 4.15 is Qt Creator 5. >> - Followed by Qt Creator 6 in December 2021. >> - Qt Creator 7 in spring 2022 >> - and so on. > > Though I understand the reasoning, I think this would be confusing. > Qt Creator has definite impact on Qt code, w.r.t. parsing. I'm thinking of > how many > releases it took QtC to support QML Enums. Hi, this has nothing to do with the Qt version that was used to build Qt Creator with. > I think a more meaningful system would > be to version it with the Qt build version, with the Z (x.y.z) being the > Qt Creator release with Qt version x.y. The Qt version that was used to build Qt Creator is mostly irrelevant for its functionality. Qt Creator built with Qt 5.14 has the same functionality as built with Qt 5.15, and after we finished support for building Qt Creator with Qt 6, that will still have the same functionality as Qt Creator built with Qt 5.15 or 5.14. We don’t need to build Qt Creator with Qt 6 to support Qt 6, and building Qt Creator with Qt 6 is no advantage for supporting Qt 6. Using Qt version numbers as a base for Qt Creator version numbers creates an impression of coupling between Qt Creator and Qt that does not exist. Additionally there are 3 Qt Creator “feature” releases per year, whereas there are 2 Qt minor releases. > Examples: > Qt Creator 5.15.4 (5th release based on Qt 5.15.2) > Qt Creator 6.0.1. (2nd release based on 6.0) > > Compared to: > Qt Creator 7 in 2022, > Qt Creator 9 in 2023, > Qt Creator 13 in 2025, > Qt Creator 23 in 2030. > Qt Creator 33 in 2040. > > > Or maybe no one cares about the QtCreator Qt built-with version? And maybe I > shouldn't care either? > I just always wonder "What is an appropriate version of QtC to be using with > Qt x.y?" Usually the latest Qt Creator has best support for latest Qt, and for previous Qt versions as well. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
[Qt-creator] Switching to more "semantic" versioning scheme
We want to switch Qt Creator to semantic versioning, which means bumping the major version for each feature release, since we don’t keep binary compatibility between these. - Next release after 4.15 is Qt Creator 5. - Followed by Qt Creator 6 in December 2021. - Qt Creator 7 in spring 2022 - and so on. The major version of Qt Creator doesn’t have any meaning at the moment, so we’d like to give it one. We almost always do incremental changes instead of major overhauls in one go, so basing the major version on some kind of feature change doesn’t make much sense. Bumping the major version for each feature release sounds more sensible because of this, and fits the semantic versioning scheme. Bump version to 5.0 beta1 (Id8510dd7) · Gerrit Code Review https://codereview.qt-project.org/c/qt-creator/qt-creator/+/339992 changes the version used in the master branch. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Getting results from network in LocatorFilter
You could have a look at the “spotlightlocatorfilter”
src/plugins/coreplugin/locator/spotlightlocatorfilter.cpp from 4.15 branch or
later:
https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/coreplugin/locator/spotlightlocatorfilter.cpp
The SpotlightIterator class creates a QProcess in the main thread, processes
its output in the main thread, posts that in a queue of results, and informs
the locator thread with QWaitCondition::wakeAll() while the locator thread is
waiting for new results with QWaitCondition::wait(…) (in
SpotlightIterator::ensureNext(), which is called from the filter’s base class,
BaseFileFilter::matchesFor).
The additional SpotlightIterator class is not necessary in your case - it is
part of the spotlight filter’s superclass, BaseFileFilter, API. You’d probably
start the request directly in your filter’s prepareSearch(…) method, and wait
for results directly in matchesFor(…).
Hope that gives you some ideas,
Br, Eike
> On Mar 7, 2021, at 11:16, Mikhail Bryukhovets wrote:
>
> Hello!
>
> I am trying to add suggestions functionality to my QtCerator plugin: When
> user types search request in the locator there will be a displayed list of
> suggested search queries based on entered text. Similar as it is done in
> browsers or search engines. Suggestions are obtained from network as results
> of GET requests to remote server. For example:
> QNetworkRequest request;
> request.setUrl(QUrl::fromUserInput("https://example.com/user_input?action=suggest;));
> auto reply = network_manager_.get(request);
> QObject::connect(reply, ::readyRead, [&](){
> qDebug() << "reply:" << reply->readAll();
> });
>
> So as I understand it I should make a network request inside matchesFor()
> function of my class derived from Core::ILocatorFilter.
> The first issue is: How and where do I obtain a result of a request to return
> it to the user?
> The second is: It seems that QNetworkAccessManager can't process
> QNetworkRequest created in another thread (QObject: Cannot create children
> for a parent that is in a different thread.
> (Parent is QNetworkAccessManager(0x163c4d0), parent's thread is
> QThread(0x6cc0d0), current thread is QThread(0x28b5810))
> I didn't find similar cases in plugins provided with QtCreator so I hope
> someone can point me in the right direction.
>
> Mikhail.
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Reminder of 4.15 feature freeze
> On Feb 23, 2021, at 09:20, Eike Ziller wrote: > > I have created the 4.15 branch(es). Please start submitting to 4.15 for the > 4.15 release. > You can use Gerrit’s “Move change” feature (from the vertical ‘…’ menu) to > move changes that you have originally pushed for master. > > Tomorrow the feature freeze will go into effect. I’ll do a last merge from > master -> 4.15 then. After that, all changes in the master branch will be for > Qt Creator 4.16. 4.15 is in feature freeze now. master branch will become 4.16. 4.15 beta1 is planned for in 2 weeks time from now (~ Mar 9 2021) Happy hacking ;) Br, Eike > >> On Feb 15, 2021, at 10:47, Eike Ziller wrote: >> >> This is a reminder to Qt Creator developers that the Qt Creator 4.15 feature >> freeze is approaching (next week): >> >> Qt Creator 4.15 >> >> * Feature freeze wk9 (~ Feb 23 2021) >> * Beta release wk11 (~ Mar 9 2021) >> * String freeze wk13 (~ Mar 23 2021) >> * RC release wk15 (~ Apr 6 2021) >> * Final release wk17 (~ Apr 20 2021) >> >> >> https://wiki.qt.io/Qt_Creator_Releases >> >> Br, >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Erich-Thilo-Straße 10 >> D-12489 Berlin >> eike.zil...@qt.io >> http://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@qt-project.org >> https://lists.qt-project.org/listinfo/qt-creator > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator ___ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Unable to Compile QtCreator (4.15)
.dir/qtcreatorsearchhandle.cpp.o > -c > /Users/Shared/OpenSource/qt-creator/src/plugins/clangrefactoring/qtcreatorsearchhandle.cpp > /Users/Shared/OpenSource/qt-creator/src/plugins/clangrefactoring/qtcreatorsearchhandle.cpp:45:39: > error: too many arguments to function call, expected single argument 'item', > have 3 arguments >searchResult->addResult(fileName, lineText, textRange); >~~~ ^~~ > /Users/Shared/OpenSource/qt-creator/src/plugins/coreplugin/find/searchresultwindow.h:79:5: > note: 'addResult' declared here >void addResult(const SearchResultItem ); >^ > 1 error generated. > [884/2446] Building CXX object > src/plugins/clangrefactoring/CMakeFiles/ClangRefactoring.dir/clangrefactoringplugin.cpp.o > ninja: build stopped: subcommand failed. > > > My configuration is macOS 10.15.7, Xcode 12.4, Qt 5.14.2 (using prebuilt from > download.qt.io) and clang prebuilt libs version 11. > > > This is the general set of commands that I follow: > >cd /Users/Shared/OpenSource >curl > "http://qt.mirror.constant.com/development_releases/prebuilt/libclang/libclang-release_100-based-mac.7z; > --output libclang-release_110-based-mac.7z >open libclang-release_110-based-mac.7z >export BRANCH=4.15 >git clone -b $BRANCH ssh://g...@github.com/qt-creator/qt-creator >mkdir -p qt-creator-builds/Relase >cd qt-creator-builds/Relase >export PATH=/Users/Shared/IMF_SDK/Qt5.14.2/5.14.2/clang_64/bin:$PATH >cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug > -DCMAKE_INSTALL_PREFIX=/Users/mjackson/Applications/QtCreator-$BRANCH > -DBUILD_PLUGIN_CLANGREFACTORING=ON -DBUILD_PLUGIN_CLANGPCHMANAGER=ON > -DCMAKE_PREFIX_PATH=/Users/Shared/OpenSource/libclang ../../qt-creator >ninja >ninja install > > > since I am not seeing any traffic on the list I'll assume that I have missed > an update or something? > -- > Michael A. Jackson 400 S. Pioneer Blvd > Owner, President Springboro, Ohio 45066 > BlueQuartz Software, LLC EMail: mike.jack...@bluequartz.net > Voice: 937-790-1601Web: http://www.bluequartz.net > Fax: 937-746-0783 > > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Dev: Reminder of 4.15 feature freeze
I have created the 4.15 branch(es). Please start submitting to 4.15 for the 4.15 release. You can use Gerrit’s “Move change” feature (from the vertical ‘…’ menu) to move changes that you have originally pushed for master. Tomorrow the feature freeze will go into effect. I’ll do a last merge from master -> 4.15 then. After that, all changes in the master branch will be for Qt Creator 4.16. Br, Eike > On Feb 15, 2021, at 10:47, Eike Ziller wrote: > > This is a reminder to Qt Creator developers that the Qt Creator 4.15 feature > freeze is approaching (next week): > > Qt Creator 4.15 > > * Feature freeze wk9 (~ Feb 23 2021) > * Beta release wk11 (~ Mar 9 2021) > * String freeze wk13 (~ Mar 23 2021) > * RC release wk15 (~ Apr 6 2021) > * Final release wk17 (~ Apr 20 2021) > > > https://wiki.qt.io/Qt_Creator_Releases > > Br, > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://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@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qt-creator] Follow Symbol Under Cursor always takes me to the header file
> On Feb 19, 2021, at 00:04, Michael Jackson > wrote: > > I have a .cpp file opened. I am sitting at a piece of code and I want to jump > to the method definition, I right click and select "Follow Symbol Under > Cursor", QtCreator takes me to the "declaration" in the header file. How do I > get it to jump to the definition instead? It should, and it does here, so I think your best shot is to open a bug report and provide details. Br, Eike > > As a side note: This has *never* worked for me since I have started using > QtCreator. I just put up with it. But this has got to be a "user error" on my > part but I can't figure out what should be doing instead. > > -- > Mike Jackson > > > ___ > Qt-creator mailing list > Qt-creator@qt-project.org > https://lists.qt-project.org/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Erich-Thilo-Straße 10 D-12489 Berlin eike.zil...@qt.io http://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@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
