From Eike.Ziller at qt.io Fri Jun 1 07:59:42 2018 From: Eike.Ziller at qt.io (Eike Ziller) Date: Fri, 1 Jun 2018 05:59:42 +0000 Subject: [Qt-creator] Qt Creator plugin distribution - best practices and future plans In-Reply-To: References: Message-ID: <6940D90D-B28E-4F50-9E41-044E6FB847AB@qt.io> > On May 31, 2018, at 15:47, Davide Coppola wrote: > > Hi, > > I am about to release a plugin for Qt Creator and even if I have no problem in releasing the source code, I would like to release binaries as well for quick installing. > > I have the impression that this is not an easy task as I should release a different binary per Qt Creator version and that wouldn't even cover all the combinations of application/compiler. Platform/compiler combinations that we use for our Qt Project prebuilt binaries are currently: MSVC2015 32&64 bit Linux / GCC 5.3(?) 64 bit macOS / Clang / 64 bit You also have to use a Qt version that is compatible with the Qt version that the prebuilt binary uses. (4.6 == Qt 5.10, i.e. it should work if you compile with Qt <= 5.10). You can find the detailed information on which compiler & Qt was used for a Qt Creator binary in its Help > About Qt Creator dialog. > For example a friend tested my plugin with the Qt Creator package provided by Arch Linux and it was crashing for him, likely because they build Qt Creator with gcc 7 and I built the plugin with gcc 5.4. I doubt that you’ll be able to create a single prebuilt binary that works on all Linux distributions. Already the locations and versions of standard libraries can differ, as well as Qt versions etc etc. > Are they any best practices or "standard" ways to handle this? > > Is there any plan from the Qt Creator developers to relax the version parity requirement? > Ideally I would like to build a plugin for 4.6 and have it running with all 4.6.x versions at least, instead of having to build it for 4.6.0, 4.6.1, etc… We try to keep patch releases _backwards_ compatible to the .0 release, and the version compatibility information reflects that (i.e. 4.6.1 states that it is compatible with 4.6.0). That means: - If you build your plugin against 4.6.0, it will run in 4.6.1 and 4.6.2. - If you build your plugin against 4.6.1, it will run in 4.6.2, but _not_ in 4.6.0. > I also noticed an abandoned Qt Creator plugin scripting project in the Qt repos. Any chance something like that will be restarted? Maybe using the new/upcoming improved Python integration? We talked about the potential of PySide for platform independent plugins for Qt Creator recently, but we don’t have concrete plans for it yet. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From vivaladav at gmail.com Tue Jun 5 15:32:24 2018 From: vivaladav at gmail.com (Davide Coppola) Date: Tue, 5 Jun 2018 15:32:24 +0200 Subject: [Qt-creator] Qt Creator plugin distribution - best practices and future plans In-Reply-To: <6940D90D-B28E-4F50-9E41-044E6FB847AB@qt.io> References: <6940D90D-B28E-4F50-9E41-044E6FB847AB@qt.io> Message-ID: Thanks Eike and Carel for your replies. All you said makes sense, even if I have to confirm that when building my plugin for 4.6.0 I can't run it with 4.6.1 as it crashes the program with the following error: ./qtcreator: symbol lookup error: /home/m3xican/.local/share/data/QtProject/qtcreator/plugins/4.6.1/libSIGBUILD.so: undefined symbol: _ZN4Core12IOptionsPageC2EP7QObject Not a huge deal, but apparently the backward compatibility was broken in 4.6.1 Cheers On Fri, 1 Jun 2018 at 07:59, Eike Ziller wrote: > > > On May 31, 2018, at 15:47, Davide Coppola wrote: > > > > Hi, > > > > I am about to release a plugin for Qt Creator and even if I have no > problem in releasing the source code, I would like to release binaries as > well for quick installing. > > > > I have the impression that this is not an easy task as I should release > a different binary per Qt Creator version and that wouldn't even cover all > the combinations of application/compiler. > > Platform/compiler combinations that we use for our Qt Project prebuilt > binaries are currently: > > MSVC2015 32&64 bit > Linux / GCC 5.3(?) 64 bit > macOS / Clang / 64 bit > > You also have to use a Qt version that is compatible with the Qt version > that the prebuilt binary uses. (4.6 == Qt 5.10, i.e. it should work if you > compile with Qt <= 5.10). > > You can find the detailed information on which compiler & Qt was used for > a Qt Creator binary in its Help > About Qt Creator dialog. > > > For example a friend tested my plugin with the Qt Creator package > provided by Arch Linux and it was crashing for him, likely because they > build Qt Creator with gcc 7 and I built the plugin with gcc 5.4. > > I doubt that you’ll be able to create a single prebuilt binary that works > on all Linux distributions. Already the locations and versions of standard > libraries can differ, as well as Qt versions etc etc. > > > Are they any best practices or "standard" ways to handle this? > > > > Is there any plan from the Qt Creator developers to relax the version > parity requirement? > > Ideally I would like to build a plugin for 4.6 and have it running with > all 4.6.x versions at least, instead of having to build it for 4.6.0, > 4.6.1, etc… > > We try to keep patch releases _backwards_ compatible to the .0 release, > and the version compatibility information reflects that (i.e. 4.6.1 states > that it is compatible with 4.6.0). > That means: > - If you build your plugin against 4.6.0, it will run in 4.6.1 and 4.6.2. > - If you build your plugin against 4.6.1, it will run in 4.6.2, but _not_ > in 4.6.0. > > > I also noticed an abandoned Qt Creator plugin scripting project in the > Qt repos. Any chance something like that will be restarted? Maybe using the > new/upcoming improved Python integration? > > We talked about the potential of PySide for platform independent plugins > for Qt Creator recently, but we don’t have concrete plans for it yet. > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > eike.ziller at qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Mika Harjuaho > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht > Charlottenburg, HRB 144331 B > > -- *Davide Coppola* *website:* http://www.davidecoppola.com *blog:* http://blog.davidecoppola.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From carel.combrink at gmail.com Tue Jun 5 17:43:31 2018 From: carel.combrink at gmail.com (Carel Combrink) Date: Tue, 5 Jun 2018 17:43:31 +0200 Subject: [Qt-creator] Qt Creator plugin distribution - best practices and future plans In-Reply-To: References: <6940D90D-B28E-4F50-9E41-044E6FB847AB@qt.io> Message-ID: Hi, That is exactly the same error that I saw on Linux (and crash), on Windows at least Qt Creator complained that it did not want to load the plugin (did not crash) Regards, On Tue, Jun 5, 2018 at 3:32 PM, Davide Coppola wrote: > Thanks Eike and Carel for your replies. > > All you said makes sense, even if I have to confirm that when building my > plugin for 4.6.0 I can't run it with 4.6.1 as it crashes the program with > the following error: > > ./qtcreator: symbol lookup error: /home/m3xican/.local/share/ > data/QtProject/qtcreator/plugins/4.6.1/libSIGBUILD.so: undefined symbol: _ > ZN4Core12IOptionsPageC2EP7QObject > > Not a huge deal, but apparently the backward compatibility was broken in > 4.6.1 > > Cheers > > On Fri, 1 Jun 2018 at 07:59, Eike Ziller wrote: > >> >> > On May 31, 2018, at 15:47, Davide Coppola wrote: >> > >> > Hi, >> > >> > I am about to release a plugin for Qt Creator and even if I have no >> problem in releasing the source code, I would like to release binaries as >> well for quick installing. >> > >> > I have the impression that this is not an easy task as I should release >> a different binary per Qt Creator version and that wouldn't even cover all >> the combinations of application/compiler. >> >> Platform/compiler combinations that we use for our Qt Project prebuilt >> binaries are currently: >> >> MSVC2015 32&64 bit >> Linux / GCC 5.3(?) 64 bit >> macOS / Clang / 64 bit >> >> You also have to use a Qt version that is compatible with the Qt version >> that the prebuilt binary uses. (4.6 == Qt 5.10, i.e. it should work if you >> compile with Qt <= 5.10). >> >> You can find the detailed information on which compiler & Qt was used for >> a Qt Creator binary in its Help > About Qt Creator dialog. >> >> > For example a friend tested my plugin with the Qt Creator package >> provided by Arch Linux and it was crashing for him, likely because they >> build Qt Creator with gcc 7 and I built the plugin with gcc 5.4. >> >> I doubt that you’ll be able to create a single prebuilt binary that works >> on all Linux distributions. Already the locations and versions of standard >> libraries can differ, as well as Qt versions etc etc. >> >> > Are they any best practices or "standard" ways to handle this? >> > >> > Is there any plan from the Qt Creator developers to relax the version >> parity requirement? >> > Ideally I would like to build a plugin for 4.6 and have it running with >> all 4.6.x versions at least, instead of having to build it for 4.6.0, >> 4.6.1, etc… >> >> We try to keep patch releases _backwards_ compatible to the .0 release, >> and the version compatibility information reflects that (i.e. 4.6.1 states >> that it is compatible with 4.6.0). >> That means: >> - If you build your plugin against 4.6.0, it will run in 4.6.1 and 4.6.2. >> - If you build your plugin against 4.6.1, it will run in 4.6.2, but _not_ >> in 4.6.0. >> >> > I also noticed an abandoned Qt Creator plugin scripting project in the >> Qt repos. Any chance something like that will be restarted? Maybe using the >> new/upcoming improved Python integration? >> >> We talked about the potential of PySide for platform independent plugins >> for Qt Creator recently, but we don’t have concrete plans for it yet. >> >> Br, Eike >> >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Rudower Chaussee 13 >> D-12489 Berlin >> eike.ziller at qt.io >> http://qt.io >> Geschäftsführer: Mika Pälsi, >> Juha Varelius, Mika Harjuaho >> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht >> Charlottenburg, HRB 144331 B >> >> > > -- > *Davide Coppola* > > *website:* http://www.davidecoppola.com > *blog:* http://blog.davidecoppola.com > > > > > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eike.Ziller at qt.io Wed Jun 6 09:30:39 2018 From: Eike.Ziller at qt.io (Eike Ziller) Date: Wed, 6 Jun 2018 07:30:39 +0000 Subject: [Qt-creator] Qt Creator plugin distribution - best practices and future plans In-Reply-To: References: <6940D90D-B28E-4F50-9E41-044E6FB847AB@qt.io> Message-ID: > On 5. Jun 2018, at 15:32, Davide Coppola wrote: > > Thanks Eike and Carel for your replies. > > All you said makes sense, even if I have to confirm that when building my plugin for 4.6.0 I can't run it with 4.6.1 as it crashes the program with the following error: > > ./qtcreator: symbol lookup error: /home/m3xican/.local/share/data/QtProject/qtcreator/plugins/4.6.1/libSIGBUILD.so: undefined symbol: _ZN4Core12IOptionsPageC2EP7QObject > > Not a huge deal, but apparently the backward compatibility was broken in 4.6.1 Indeed. Very sorry about that. We should look into at least half-automated testing for this in the future. > Cheers > > On Fri, 1 Jun 2018 at 07:59, Eike Ziller wrote: > > > On May 31, 2018, at 15:47, Davide Coppola wrote: > > > > Hi, > > > > I am about to release a plugin for Qt Creator and even if I have no problem in releasing the source code, I would like to release binaries as well for quick installing. > > > > I have the impression that this is not an easy task as I should release a different binary per Qt Creator version and that wouldn't even cover all the combinations of application/compiler. > > Platform/compiler combinations that we use for our Qt Project prebuilt binaries are currently: > > MSVC2015 32&64 bit > Linux / GCC 5.3(?) 64 bit > macOS / Clang / 64 bit > > You also have to use a Qt version that is compatible with the Qt version that the prebuilt binary uses. (4.6 == Qt 5.10, i.e. it should work if you compile with Qt <= 5.10). > > You can find the detailed information on which compiler & Qt was used for a Qt Creator binary in its Help > About Qt Creator dialog. > > > For example a friend tested my plugin with the Qt Creator package provided by Arch Linux and it was crashing for him, likely because they build Qt Creator with gcc 7 and I built the plugin with gcc 5.4. > > I doubt that you’ll be able to create a single prebuilt binary that works on all Linux distributions. Already the locations and versions of standard libraries can differ, as well as Qt versions etc etc. > > > Are they any best practices or "standard" ways to handle this? > > > > Is there any plan from the Qt Creator developers to relax the version parity requirement? > > Ideally I would like to build a plugin for 4.6 and have it running with all 4.6.x versions at least, instead of having to build it for 4.6.0, 4.6.1, etc… > > We try to keep patch releases _backwards_ compatible to the .0 release, and the version compatibility information reflects that (i.e. 4.6.1 states that it is compatible with 4.6.0). > That means: > - If you build your plugin against 4.6.0, it will run in 4.6.1 and 4.6.2. > - If you build your plugin against 4.6.1, it will run in 4.6.2, but _not_ in 4.6.0. > > > I also noticed an abandoned Qt Creator plugin scripting project in the Qt repos. Any chance something like that will be restarted? Maybe using the new/upcoming improved Python integration? > > We talked about the potential of PySide for platform independent plugins for Qt Creator recently, but we don’t have concrete plans for it yet. > > Br, Eike > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > eike.ziller at qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Mika Harjuaho > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B > > > > -- > Davide Coppola > > website: http://www.davidecoppola.com > blog: http://blog.davidecoppola.com -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From smurphy at walbro.com Fri Jun 8 20:07:13 2018 From: smurphy at walbro.com (Murphy, Sean) Date: Fri, 8 Jun 2018 18:07:13 +0000 Subject: [Qt-creator] How to break on an assert? Message-ID: <4cf68973edae40a7ada1a132ef210bb3@walbro.com> I'm sure I'm doing something stupid, but I'm not sure how to find it. I've got an existing codebase that we've just discovered fails on a new type of input - basically we crossed over the signed/unsigned boundary of a single byte field. So previous runs on the application always had this variable <= 127, now we're providing an input where the variable should be >= 128. I fixed the first place I found the issue, but that has changed where the problem occurs to somewhere later in my code I'm getting an assertion, but I'm having trouble figuring out where. When running a debug build inside Qt Creator, all I get in the Application Output pane is: ASSERT failure in QList::at: "index out of range", file C:\Qt_5_3_2\5.3\mingw482_32\include/QtCore/qlist.h, line 479 But I have no idea where in my code this is happening, and gdb isn't breaking on this assert, allowing me to see where in my call stack this is happening. I've got plenty of QList's all over the place, and I'm fairly certain this issue is happening after a bunch of different signals fire, which is leading to the difficulty of tracking down where this happens. Is there some setting in gdb/Qt Creator that would automatically break on this assertion? Sean This message has been scanned for malware by Forcepoint. www.forcepoint.com From steve at blighty.com Fri Jun 8 20:21:41 2018 From: steve at blighty.com (Steve Atkins) Date: Fri, 8 Jun 2018 11:21:41 -0700 Subject: [Qt-creator] How to break on an assert? In-Reply-To: <4cf68973edae40a7ada1a132ef210bb3@walbro.com> References: <4cf68973edae40a7ada1a132ef210bb3@walbro.com> Message-ID: <9E147F3A-39FC-416D-BD91-8F3E57AF30A0@blighty.com> > On Jun 8, 2018, at 11:07 AM, Murphy, Sean wrote: > > I'm sure I'm doing something stupid, but I'm not sure how to find it. I've got an existing codebase that we've just discovered fails on a new type of input - basically we crossed over the signed/unsigned boundary of a single byte field. So previous runs on the application always had this variable <= 127, now we're providing an input where the variable should be >= 128. I fixed the first place I found the issue, but that has changed where the problem occurs to somewhere later in my code I'm getting an assertion, but I'm having trouble figuring out where. > > When running a debug build inside Qt Creator, all I get in the Application Output pane is: > ASSERT failure in QList::at: "index out of range", file C:\Qt_5_3_2\5.3\mingw482_32\include/QtCore/qlist.h, line 479 > > But I have no idea where in my code this is happening, and gdb isn't breaking on this assert, allowing me to see where in my call stack this is happening. I've got plenty of QList's all over the place, and I'm fairly certain this issue is happening after a bunch of different signals fire, which is leading to the difficulty of tracking down where this happens. > > Is there some setting in gdb/Qt Creator that would automatically break on this assertion? Q_ASSERT uses qFatal(), so you can break on that and get a stack trace. Preferences... -> Debugger -> GDB Extended has "Stop when qFatal() is called", which might do what you need. Cheers, Steve From smurphy at walbro.com Fri Jun 8 20:46:11 2018 From: smurphy at walbro.com (Murphy, Sean) Date: Fri, 8 Jun 2018 18:46:11 +0000 Subject: [Qt-creator] How to break on an assert? In-Reply-To: <9E147F3A-39FC-416D-BD91-8F3E57AF30A0@blighty.com> References: <4cf68973edae40a7ada1a132ef210bb3@walbro.com> <9E147F3A-39FC-416D-BD91-8F3E57AF30A0@blighty.com> Message-ID: <241f4c17b7e04840b77e53bc9b063b3b@walbro.com> > > Is there some setting in gdb/Qt Creator that would automatically break on > this assertion? > > Q_ASSERT uses qFatal(), so you can break on that and get a stack trace. > > Preferences... -> Debugger -> GDB Extended has "Stop when qFatal() is > called", which might do what you need. Thanks! That did the trick. I notice at the top of that tab it says "The options below should be used with care.", can anyone talk me through the harm of leaving this option enabled (and maybe the "Stop when abort() is called") as well? Sean This message has been scanned for malware by Forcepoint. www.forcepoint.com From apoenitz at t-online.de Fri Jun 8 22:39:03 2018 From: apoenitz at t-online.de (=?iso-8859-1?Q?Andr=E9_P=F6nitz?=) Date: Fri, 8 Jun 2018 22:39:03 +0200 Subject: [Qt-creator] How to break on an assert? In-Reply-To: <241f4c17b7e04840b77e53bc9b063b3b@walbro.com> References: <4cf68973edae40a7ada1a132ef210bb3@walbro.com> <9E147F3A-39FC-416D-BD91-8F3E57AF30A0@blighty.com> <241f4c17b7e04840b77e53bc9b063b3b@walbro.com> Message-ID: <20180608203903.GA17944@klara.mpi.htwm.de> On Fri, Jun 08, 2018 at 06:46:11PM +0000, Murphy, Sean wrote: > > > Is there some setting in gdb/Qt Creator that would automatically break on > > this assertion? > > > > Q_ASSERT uses qFatal(), so you can break on that and get a stack trace. > > > > Preferences... -> Debugger -> GDB Extended has "Stop when qFatal() is called", > > which might do what you need. > > Thanks! That did the trick. I notice at the top of that tab it says "The options > below should be used with care.", can anyone talk me through the harm of leaving > this option enabled (and maybe the "Stop when abort() is called") as well? The harm is mostly startup performance degradation, especially in cases where the symbol is not found or even present (e.g. in non-Qt applications). While this is in general true for any breakpoint, it gets more prominent for functions that may or may not belong to a Qt configured with -qtnamespace as trying to determine the configured namespace may trigger excessive scans of debug information. On Windows there seems also be a problem when that search kicks in very early in the application startup due to an unrelated interruption either gdb or the dynamic loader gets confused to a degree that continuation is not possible. So it's not an option to leave on by default, use it only when you notice you need it. But it won't eat kittens, if that's what you are afraid of. Andre' From chgans at gmail.com Sun Jun 10 10:06:06 2018 From: chgans at gmail.com (Christian Gagneraud) Date: Sun, 10 Jun 2018 20:06:06 +1200 Subject: [Qt-creator] 'Proper' Python support Message-ID: Hi there, With the upcoming "Python for Qt" release, is there any plan to have a more advanced python editor? There's a "Python Language Server" available[1], an implementation of the "Language Server Protocol" [2] for python. I personally hate companies like Palentir [3], and i'm not a Microsoft fanboy (to say the least) , but these open source component could be useful to QtCreator. Visual Code is the new "Revolution" according to Microsoft fanboys (trying to mimick Apple fanboys), where does QtCreator stand in this? I'm working in a 98% MS environment, but every developer has a Linux VM. Yet, what is the first thing they install in their Linux VM? Visual Code! What drive me nuts, is that they all have a Qt License, yet they don't give a sh*t about QtC, way better to require a MS Visual Studio license as well... But i'm diverging. The only reason i can think of, is that they are completely brain-washed and addicted to MS technologies, to a point that they won't even look at something else, even if it's better. Now when it comes to python, Visual Code is actually way better than QtCreator, thanks to their "Language Server Protocol". It's actually a brilliant idea [4] I do lot of C++, Qt and Python, often, but not always mixed together. I can't wait for the new "Python for Qt" and I would love QtCreator to have way better support for python, in the mean time emacs is still my editor of choice, but i'm seriously thinking about using Visual Code for editing python. I use as well the Squish tool [5], a test framework, driven in python, to test Qt/C++ applications. But I cannot use QtCreator, I have to use an Eclipse based IDE... Some of my colleagues don't use the so called "Squis IDE", instead they prefer a mix of command line and ... Visual Code. Again! Any thoughts? Chris [1] https://github.com/palantir/python-language-server [2] https://github.com/Microsoft/language-server-protocol [3] https://en.wikipedia.org/wiki/Palantir_Technologies#Controversies [4] https://microsoft.github.io/language-server-protocol/ [5] https://www.froglogic.com/squish/ From Eike.Ziller at qt.io Mon Jun 11 09:41:03 2018 From: Eike.Ziller at qt.io (EXT Eike Ziller) Date: Mon, 11 Jun 2018 07:41:03 +0000 Subject: [Qt-creator] 'Proper' Python support In-Reply-To: References: Message-ID: <10A83850-1EE2-4C17-B292-004CF206F9B6@qt.io> > On 10. Jun 2018, at 10:06, Christian Gagneraud wrote: > > Hi there, > > With the upcoming "Python for Qt" release, is there any plan to have a > more advanced python editor? > > There's a "Python Language Server" available[1], an implementation of > the "Language Server Protocol" [2] for python. We currently work on support for the language server protocol. https://bugreports.qt.io/browse/QTCREATORBUG-20284 It doesn’t really solve all problems with supporting another language ((semantic) highlighting, building & running, etc), but should make supporting additional languages much easier. > I personally hate companies like Palentir [3], and i'm not a Microsoft > fanboy (to say the least) , but these open source component could be > useful to QtCreator. > > Visual Code is the new "Revolution" according to Microsoft fanboys > (trying to mimick Apple fanboys), where does QtCreator stand in this? I don’t understand what your question is. > I'm working in a 98% MS environment, but every developer has a Linux > VM. Yet, what is the first thing they install in their Linux VM? > Visual Code! What drive me nuts, is that they all have a Qt License, > yet they don't give a sh*t about QtC, way better to require a MS > Visual Studio license as well... But i'm diverging. > > The only reason i can think of, is that they are completely > brain-washed and addicted to MS technologies, to a point that they > won't even look at something else, even if it's better. > > Now when it comes to python, Visual Code is actually way better than > QtCreator, thanks to their "Language Server Protocol". It's actually a > brilliant idea [4] > > I do lot of C++, Qt and Python, often, but not always mixed together. > I can't wait for the new "Python for Qt" and I would love QtCreator to > have way better support for python, in the mean time emacs is still my > editor of choice, but i'm seriously thinking about using Visual Code > for editing python. As a side note there seems to be a language server support lib + python support for emacs too: https://github.com/emacs-lsp/lsp-mode https://github.com/emacs-lsp/lsp-python I haven’t checked if and how they work though. Br, Eike > > I use as well the Squish tool [5], a test framework, driven in python, > to test Qt/C++ applications. But I cannot use QtCreator, I have to use > an Eclipse based IDE... Some of my colleagues don't use the so called > "Squis IDE", instead they prefer a mix of command line and ... Visual > Code. Again! > > Any thoughts? > > Chris > > [1] https://github.com/palantir/python-language-server > [2] https://github.com/Microsoft/language-server-protocol > [3] https://en.wikipedia.org/wiki/Palantir_Technologies#Controversies > [4] https://microsoft.github.io/language-server-protocol/ > [5] https://www.froglogic.com/squish/ > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From martonmiklosqdev at gmail.com Mon Jun 11 14:47:12 2018 From: martonmiklosqdev at gmail.com (=?UTF-8?B?TcOhcnRvbiBNaWtsw7Nz?=) Date: Mon, 11 Jun 2018 14:47:12 +0200 Subject: [Qt-creator] Debugging code built with SDCC Message-ID: Hello all, I am trying to put together a toolchain for a STM8 (bare metal) target based on QtCreator, openOCD, SDCC and GDB. I am proceeding great so far: the debugging of the target works, but I only able to debug the code at assembly level (even when the Debug menu -> Operate by instruction is unchecked). I am using the following command to build the elf file: sdcc -lstm8 -mstm8 blinky.c --out-fmt-elf --all-callee-saves --debug --verbose --stack-auto --fverbose-asm --float-reent --no-peep If I debug it separately from QtCreator with GDB it shows the C code when it stops at the breakpoint for e.g. Here is the output of the debugger log pane: https://pastebin.com/Nzi7YQ7w The only suspicious thing what I see is the following section: >&"set disassembly-flavor att\n" >&"No symbol \"disassembly\" in current context.\n" >2117^error,msg="No symbol \"disassembly\" in current context." Any help/hint about the further things to check would be highly appreciated! Kind regards, Miklos Marton -------------- next part -------------- An HTML attachment was scrubbed... URL: From smurphy at walbro.com Mon Jun 11 21:31:29 2018 From: smurphy at walbro.com (Murphy, Sean) Date: Mon, 11 Jun 2018 19:31:29 +0000 Subject: [Qt-creator] List of applications spawned by Qt Creator Message-ID: I'm in a fight with my corporate IT guys about anti-virus software that they've put on my machine which is absolutely killing performance when attempting to debug software I'm developing. It takes more than 5 minutes from clicking File->Open in my application to having a working file dialog - and that has been timed with a stopwatch, it's not an exaggeration. They've agreed to try whitelisting certain .exe's if I can get them a list, so I'm trying to figure out a comprehensive list of what Qt Creator spawns when compiling and debugging on Windows. Is there a list of the executables somewhere? By watching Task Manager, I can see things like "mingw-make32.exe" while compiling and "gdb.exe" and "gdborig.exe" while debugging, just not sure if there are others. This message has been scanned for malware by Forcepoint. www.forcepoint.com From apoenitz at t-online.de Mon Jun 11 09:49:23 2018 From: apoenitz at t-online.de (=?iso-8859-1?Q?Andr=E9_P=F6nitz?=) Date: Mon, 11 Jun 2018 09:49:23 +0200 Subject: [Qt-creator] Debugging code built with SDCC In-Reply-To: References: Message-ID: <20180611074923.GA14528@klara.mpi.htwm.de> On Mon, Jun 11, 2018 at 02:47:12PM +0200, Márton Miklós wrote: > Hello all, > > I am trying to put together a toolchain for a STM8 (bare metal) target > based on QtCreator, openOCD, SDCC and GDB. > > I am proceeding great so far: the debugging of the target works, but I only > able to debug the code at assembly level (even when the Debug menu -> > Operate by instruction is unchecked). > > I am using the following command to build the elf file: > > sdcc -lstm8 -mstm8 blinky.c --out-fmt-elf --all-callee-saves --debug > --verbose --stack-auto --fverbose-asm --float-reent --no-peep > > If I debug it separately from QtCreator with GDB it shows the C code when > it stops at the breakpoint for e.g. > > Here is the output of the debugger log pane: > > https://pastebin.com/Nzi7YQ7w > > The only suspicious thing what I see is the following section: > >&"set disassembly-flavor att\n" > >&"No symbol \"disassembly\" in current context.\n" > >2117^error,msg="No symbol \"disassembly\" in current context." This one is harmless. > Any help/hint about the further things to check would be highly appreciated! It looks like there is debug information available, and interestingly enough it is able to resolve the blinky.c:6 breakpoint to 0x8024. The breakpoint is hit later, the response has file="blinky.c",fullname="/home/mm/Projektek/sdcc-examples-stm8/blinky.c" Does /home/mm/Projektek/sdcc-examples-stm8/blinky.c exist? If not, do you have a blinky.c file elsewhere? If so, does setting up a source path mapping under Tools->Options->Debugger->General help? If not, does moving/linking your sources so that /home/mm/Projektek/sdcc-examples-stm8/blinky.c exists help? Andre' From orgads at gmail.com Mon Jun 11 21:48:36 2018 From: orgads at gmail.com (Orgad Shaneh) Date: Mon, 11 Jun 2018 22:48:36 +0300 Subject: [Qt-creator] List of applications spawned by Qt Creator In-Reply-To: References: Message-ID: On Mon, Jun 11, 2018 at 10:31 PM Murphy, Sean wrote: > I'm in a fight with my corporate IT guys about anti-virus software that > they've put on my machine which is absolutely killing performance when > attempting to debug software I'm developing. It takes more than 5 minutes > from clicking File->Open in my application to having a working file dialog > - and that has been timed with a stopwatch, it's not an exaggeration. > > They've agreed to try whitelisting certain .exe's if I can get them a > list, so I'm trying to figure out a comprehensive list of what Qt Creator > spawns when compiling and debugging on Windows. Is there a list of the > executables somewhere? By watching Task Manager, I can see things like > "mingw-make32.exe" while compiling and "gdb.exe" and "gdborig.exe" while > debugging, just not sure if there are others. > >From my experience, anti-viruses tend to be intolerable, and worse than the viruses they should protect against. I had several AVs installed on my machine by IT (we had Checkpoint, then Kaspersky). They all magically ended up disabled (shhhh... don't tell anyone). In practice, if you need a whitelist, I can think of the following: mingw32-make.exe, gcc.exe, g++.exe, cc1plus.exe, gdb.exe, nmake.exe, jom.exe, cl.exe, *.cpp, *.c, *.h, *.hpp Good luck! - Orgad -------------- next part -------------- An HTML attachment was scrubbed... URL: From smurphy at walbro.com Mon Jun 11 22:05:25 2018 From: smurphy at walbro.com (Murphy, Sean) Date: Mon, 11 Jun 2018 20:05:25 +0000 Subject: [Qt-creator] List of applications spawned by Qt Creator In-Reply-To: References: Message-ID: > From my experience, anti-viruses tend to be intolerable, and worse than the viruses > they should protect against. 100% agree > I had several AVs installed on my machine by IT (we had Checkpoint, then Kaspersky). > They all magically ended up disabled (shhhh... don't tell anyone). In my case, the worst offender is a program called CrowdStrike Falcon Sensor. I used to be able to "magically" disable it as well, but now they've password protected the uninstaller, so I don't seem to have a way to uninstall it anymore... > In practice, if you need a whitelist, I can think of the following: > mingw32-make.exe, gcc.exe, g++.exe, cc1plus.exe, gdb.exe, > nmake.exe, jom.exe, cl.exe, *.cpp, *.c, *.h, *.hpp Keep them coming, thanks! Sean This message has been scanned for malware by Forcepoint. www.forcepoint.com From martonmiklosqdev at gmail.com Mon Jun 11 22:08:29 2018 From: martonmiklosqdev at gmail.com (Miklos Marton) Date: Mon, 11 Jun 2018 22:08:29 +0200 Subject: [Qt-creator] Debugging code built with SDCC In-Reply-To: <20180611074923.GA14528@klara.mpi.htwm.de> References: <20180611074923.GA14528@klara.mpi.htwm.de> Message-ID: > Does /home/mm/Projektek/sdcc-examples-stm8/blinky.c exist? If not, do you > have a blinky.c file elsewhere? Yes it exists. It is a flat single file example, nothing fancy. I will give a try to the source path mapping tomorrow. Many thanks for the tips! -- Best regards, Miklos Marton From pfrank at gmx.de Mon Jun 11 23:24:57 2018 From: pfrank at gmx.de (Petric Frank) Date: Mon, 11 Jun 2018 23:24:57 +0200 Subject: [Qt-creator] Debugging a specific program in a project with subprojects Message-ID: <3043611.lgz3VnvMsV@main> Hello, i have a (master-)project containing some sub-projects. Some sub-projects generate shared libraries other applications. Running a specific application is easy: In the projects window use the right mouse button on a sub-project and select execute. But there is not menu item for debug. Am i mssing something. My master *.pro file looks like this: ------------------ cut ------------------- TEMPLATE = subdirs CONFIG += ordered SUBDIRS = \ shared1 \ shared2 \ app1 \ app2 \ app3 ------------------ cut ------------------- If i simply go to the main menu and select debug the question is which one of the apps it will execute to debug ? Followup: how to set the app to debug ? The only way i found so far is to comment out the other two apps and run qmake. kind regards Petric From giuseppe.dangelo at kdab.com Tue Jun 12 00:15:22 2018 From: giuseppe.dangelo at kdab.com (Giuseppe D'Angelo) Date: Tue, 12 Jun 2018 00:15:22 +0200 Subject: [Qt-creator] Debugging a specific program in a project with subprojects In-Reply-To: <3043611.lgz3VnvMsV@main> References: <3043611.lgz3VnvMsV@main> Message-ID: Il 11/06/2018 23:24, Petric Frank ha scritto: > If i simply go to the main menu and select debug the question is which one of > the apps it will execute to debug ? > Followup: how to set the app to debug ? Click on button 2 and select the target to run/debug, then you can just run/debug it: > https://doc.qt.io/qtcreator/images/qtcreator-breakdown.png HTH, -- Giuseppe D'Angelo | giuseppe.dangelo at kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4007 bytes Desc: Firma crittografica S/MIME URL: From s.r.alavizadeh at gmail.com Tue Jun 12 00:44:08 2018 From: s.r.alavizadeh at gmail.com (Seyyed Razi Alavizadeh) Date: Tue, 12 Jun 2018 03:14:08 +0430 Subject: [Qt-creator] List of applications spawned by Qt Creator In-Reply-To: References: Message-ID: "File->Open" takes a big time to open default open dialog on Windows, since it loads a lots of DLL files. For example, a list of DLLs loaded for "File->Open" of an application on my computer (Win10) is here [1]. I just copy (with a little cleanup) the output of WinDbg. [1] http://www.beepaste.io/paste/view/gH8yQR Alavizadeh, Sayed Razi My Blog: http://pozh.org Saaghar (نرم‌افزار شعر): http://saaghar.pozh.org/ ​​ Saaghar Telegram Channel: @Saaghar ​ Saaghar Telegram Bot: @SaagharBot ​ ‫‪Murphy, Sean‬‏ <‪smurphy at walbro.com‬‏> در تاریخ سه‌شنبه ۱۲ ژوئن ۲۰۱۸ ساعت ۰:۳۵ نوشت:‬ > > From my experience, anti-viruses tend to be intolerable, and worse than > the viruses > > they should protect against. > > 100% agree > > > I had several AVs installed on my machine by IT (we had Checkpoint, then > Kaspersky). > > They all magically ended up disabled (shhhh... don't tell anyone). > > In my case, the worst offender is a program called CrowdStrike Falcon > Sensor. I used > to be able to "magically" disable it as well, but now they've password > protected the > uninstaller, so I don't seem to have a way to uninstall it anymore... > > > In practice, if you need a whitelist, I can think of the following: > > mingw32-make.exe, gcc.exe, g++.exe, cc1plus.exe, gdb.exe, > > nmake.exe, jom.exe, cl.exe, *.cpp, *.c, *.h, *.hpp > > Keep them coming, thanks! > Sean > > > > This message has been scanned for malware by Forcepoint. > www.forcepoint.com > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eike.Ziller at qt.io Tue Jun 12 07:06:49 2018 From: Eike.Ziller at qt.io (EXT Eike Ziller) Date: Tue, 12 Jun 2018 05:06:49 +0000 Subject: [Qt-creator] List of applications spawned by Qt Creator In-Reply-To: References: Message-ID: <96E638CF-7DF4-493A-BF7A-9B3A03621D60@qt.io> > On Jun 11, 2018, at 22:05, Murphy, Sean wrote: > >> From my experience, anti-viruses tend to be intolerable, and worse than the viruses >> they should protect against. > > 100% agree > >> I had several AVs installed on my machine by IT (we had Checkpoint, then Kaspersky). >> They all magically ended up disabled (shhhh... don't tell anyone). > > In my case, the worst offender is a program called CrowdStrike Falcon Sensor. I used > to be able to "magically" disable it as well, but now they've password protected the > uninstaller, so I don't seem to have a way to uninstall it anymore... > >> In practice, if you need a whitelist, I can think of the following: >> mingw32-make.exe, gcc.exe, g++.exe, cc1plus.exe, gdb.exe, >> nmake.exe, jom.exe, cl.exe, *.cpp, *.c, *.h, *.hpp One of the issues with antivirus software can be if you create a lot of files (AFAIK), which of course is true when compiling, so you might want to ask for an ignored development directory where you can put all your project’s build directories. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From orgads at gmail.com Tue Jun 12 07:13:50 2018 From: orgads at gmail.com (Orgad Shaneh) Date: Tue, 12 Jun 2018 08:13:50 +0300 Subject: [Qt-creator] List of applications spawned by Qt Creator In-Reply-To: References: Message-ID: On Mon, Jun 11, 2018 at 11:05 PM Murphy, Sean wrote: > > I had several AVs installed on my machine by IT (we had Checkpoint, then > Kaspersky). > > They all magically ended up disabled (shhhh... don't tell anyone). > > In my case, the worst offender is a program called CrowdStrike Falcon > Sensor. I used > to be able to "magically" disable it as well, but now they've password > protected the > uninstaller, so I don't seem to have a way to uninstall it anymore... > Nothing is impossible when you have a live linux with chntpw on a USB stick, and the option to boot from USB ;) > In practice, if you need a whitelist, I can think of the following: > > mingw32-make.exe, gcc.exe, g++.exe, cc1plus.exe, gdb.exe, > > nmake.exe, jom.exe, cl.exe, *.cpp, *.c, *.h, *.hpp > > Keep them coming, thanks! > Sean > I forgot to mention also qtcreator_process_stub.exe, and of course your application :) - Orgad -------------- next part -------------- An HTML attachment was scrubbed... URL: From pfrank at gmx.de Tue Jun 12 08:51:50 2018 From: pfrank at gmx.de (Petric Frank) Date: Tue, 12 Jun 2018 08:51:50 +0200 Subject: [Qt-creator] Debugging a specific program in a project with subprojects In-Reply-To: References: <3043611.lgz3VnvMsV@main> Message-ID: <3831272.r6jQC5jyvQ@main> Hello, Am Dienstag, 12. Juni 2018, 00:15:22 CEST schrieb Giuseppe D'Angelo via Qt- creator: > Il 11/06/2018 23:24, Petric Frank ha scritto: > > If i simply go to the main menu and select debug the question is which one > > of the apps it will execute to debug ? > > Followup: how to set the app to debug ? > > Click on button 2 and select the target to run/debug, then you can just > > run/debug it: > > https://doc.qt.io/qtcreator/images/qtcreator-breakdown.png aaaaahhhhh .... thats the the thing i missed. Thank you very much for your hint. regards Petric From b.terrier at gmail.com Tue Jun 12 11:46:55 2018 From: b.terrier at gmail.com (Benjamin TERRIER) Date: Tue, 12 Jun 2018 11:46:55 +0200 Subject: [Qt-creator] Qt Quick Compiler vs qrc files vs project explorer In-Reply-To: References: Message-ID: Le jeu. 24 mai 2018 à 17:01, Benjamin TERRIER a écrit : > > Hi, > > I am trying the Qt Quick Compiler that comes with Qt 5.11. > When I enable it in a .pro file (`CONFIG += qtquickcompiler`) then, in the > project explorer, > all the qrc files that contains qml of js file are replaced by a cache qrc > that is located in the build directory. > > For instance if I have `myqmlfiles.qrc`, the project explorer shows > `/myqmlfiles_myqmlfiles_qmlcache.qrc` instead of > `myqmlfiles.qrc`. > > Is it a known issue? > Could it be link to https://bugreports.qt.io/browse/QTCREATORBUG-19993 ? After upgrading to Qt Creator 4.6.2 the issue is still here. It can be reproduced either by adding "CONFIG += qtquickcompiler" in the pro file or by checking the "Enable Qt Quick Compiler" checkbox in the project tab. BR, Benjamin From mitch.curtis at qt.io Tue Jun 12 11:57:46 2018 From: mitch.curtis at qt.io (EXT Mitch Curtis) Date: Tue, 12 Jun 2018 09:57:46 +0000 Subject: [Qt-creator] Qt Quick Compiler vs qrc files vs project explorer In-Reply-To: References: Message-ID: > -----Original Message----- > From: Qt-creator [mailto:qt-creator-bounces+mitch.curtis=qt.io at qt- > project.org] On Behalf Of Benjamin TERRIER > Sent: Thursday, 24 May 2018 5:02 PM > To: qt-creator > Subject: [Qt-creator] Qt Quick Compiler vs qrc files vs project explorer > > Hi, > > I am trying the Qt Quick Compiler that comes with Qt 5.11. > When I enable it in a .pro file (`CONFIG += qtquickcompiler`) then, in the > project explorer, all the qrc files that contains qml of js file are replaced by a > cache qrc that is located in the build directory. > > For instance if I have `myqmlfiles.qrc`, the project explorer shows > `/myqmlfiles_myqmlfiles_qmlcache.qrc` instead of > `myqmlfiles.qrc`. > > Is it a known issue? > Could it be link to https://bugreports.qt.io/browse/QTCREATORBUG-19993 ? This looks awfully similar to https://bugreports.qt.io/browse/QTCREATORBUG-20103 - I would hazard a guess that qtquickcompiler uses the same syntax internally which results in that kind of structure in the project explorer. > Regards, > > Benjamin > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator From smurphy at walbro.com Tue Jun 12 13:56:20 2018 From: smurphy at walbro.com (Murphy, Sean) Date: Tue, 12 Jun 2018 11:56:20 +0000 Subject: [Qt-creator] List of applications spawned by Qt Creator In-Reply-To: <96E638CF-7DF4-493A-BF7A-9B3A03621D60@qt.io> References: <96E638CF-7DF4-493A-BF7A-9B3A03621D60@qt.io> Message-ID: <1793e9fbf9354af387c707be0c048ffe@walbro.com> > One of the issues with antivirus software can be if you create a lot of files > (AFAIK), which of course is true when compiling, so you might want to ask for > an ignored development directory where you can put all your project’s build > directories. Supposedly we have that in place already, but it doesn't seem to make much difference. I'll double check with them that it is actually setup that way though. Sean This message has been scanned for malware by Forcepoint. www.forcepoint.com From smurphy at walbro.com Tue Jun 12 14:25:43 2018 From: smurphy at walbro.com (Murphy, Sean) Date: Tue, 12 Jun 2018 12:25:43 +0000 Subject: [Qt-creator] List of applications spawned by Qt Creator In-Reply-To: References: Message-ID: <7db8263622c54f699a815660b3027097@walbro.com> > > In my case, the worst offender is a program called CrowdStrike Falcon Sensor. I used > > to be able to "magically" disable it as well, but now they've password protected the > > uninstaller, so I don't seem to have a way to uninstall it anymore... > > Nothing is impossible when you have a live linux with http://www.chntpw.com/download/ > on a USB stick, and the option to boot from USB ;) I'll probably pass on this option, since if discovered, I'd probably lose my job. Good to know it exists though! > I forgot to mention also qtcreator_process_stub.exe, and of course your application :) Our applications are already on the list, but I'm adding qtcreator_process_stub.exe Sean This message has been scanned for malware by Forcepoint. www.forcepoint.com From ivan.donchevskii at qt.io Wed Jun 13 09:44:23 2018 From: ivan.donchevskii at qt.io (Ivan Donchevskii) Date: Wed, 13 Jun 2018 07:44:23 +0000 Subject: [Qt-creator] What are your favorite clang-tidy checks Message-ID: Hi! On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. Kind regards, Ivan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ivan.donchevskii at qt.io Wed Jun 13 11:39:54 2018 From: ivan.donchevskii at qt.io (Ivan Donchevskii) Date: Wed, 13 Jun 2018 09:39:54 +0000 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: Message-ID: You can also check the full list of Clang-Tidy 6.0 checks at https://releases.llvm.org/6.0.0/tools/clang/tools/extra/docs/clang-tidy/checks/ ________________________________ From: Qt-creator on behalf of Ivan Donchevskii Sent: Wednesday, June 13, 2018 9:44:23 AM To: qt-creator at qt-project.org Subject: [Qt-creator] What are your favorite clang-tidy checks Hi! On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. Kind regards, Ivan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhihn at gmx.com Thu Jun 14 16:56:37 2018 From: jhihn at gmx.com (Jason H) Date: Thu, 14 Jun 2018 16:56:37 +0200 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From vperetokin at gmail.com Thu Jun 14 16:57:43 2018 From: vperetokin at gmail.com (Vadim Peretokin) Date: Thu, 14 Jun 2018 16:57:43 +0200 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: Message-ID: I have not had issues with modernize-loop-convert not detecting that variables are used by other things in a well-established codebase - ymmv. On Thu, Jun 14, 2018 at 4:56 PM Jason H wrote: > My LEAST favorite is > modernize-loop-convert > > It seems to be blindly applied. If I am using the loop increment variable > for aother things, that is a not good to recommend. It doesn't seem to > detect that. > > *Sent:* Wednesday, June 13, 2018 at 4:39 AM > *From:* "Ivan Donchevskii" > *To:* "qt-creator at qt-project.org" > *Subject:* Re: [Qt-creator] What are your favorite clang-tidy checks > > You can also check the full list of Clang-Tidy 6.0 checks at > https://releases.llvm.org/6.0.0/tools/clang/tools/extra/docs/clang-tidy/checks/ > ------------------------------ > *From:* Qt-creator qt.io at qt-project.org> on behalf of Ivan Donchevskii < > ivan.donchevskii at qt.io> > *Sent:* Wednesday, June 13, 2018 9:44:23 AM > *To:* qt-creator at qt-project.org > *Subject:* [Qt-creator] What are your favorite clang-tidy checks > > > Hi! > > > > On the contributors summit I mentioned that we want to introduce the > "default" set of flags for Clang-Tidy which can be used as a starting point > for analysis and is good enough for some random project developed in Qt > Creator. > > We have an example of it in https://codereview.qt-project.org/#/c/230400/ but > not sure if it is actually the proper list. > > > > Here's the list itself - > "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" > > > > Let us know if there's something you would like to add or remove from it. > You can check the whole tree of currently available checks in 4.7 beta or > in one of our latest Qt Creator snapshots. > > > > Kind regards, > > Ivan > _______________________________________________ Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.jackson at bluequartz.net Thu Jun 14 18:03:37 2018 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Thu, 14 Jun 2018 12:03:37 -0400 Subject: [Qt-creator] What are your favorite clang-tidy checks Message-ID: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> I tend to go back and forth between turning it off so that code completion actually completes in a reasonable amount of time (~1 second) or having all the helpful insights into my code base. It is almost like QtCreator needs to have 2 threads running. One for the code completion and one for the clang-tidy stuff. -- Mike Jackson On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" wrote: Hi! On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. Kind regards, Ivan _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator -------------- next part -------------- An HTML attachment was scrubbed... URL: From ivan.donchevskii at qt.io Thu Jun 14 18:10:40 2018 From: ivan.donchevskii at qt.io (Ivan Donchevskii) Date: Thu, 14 Jun 2018 16:10:40 +0000 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> Message-ID: In Qt Creator 4.7 there's a separate tool (Analyze menu) that runs Clang-Tidy checks over the selected files which does not affect your opened documents. I hope it solves your problem at least partially :) ________________________________ From: Qt-creator on behalf of Michael Jackson Sent: Thursday, June 14, 2018 6:03:37 PM To: qt-creator at qt-project.org Subject: Re: [Qt-creator] What are your favorite clang-tidy checks I tend to go back and forth between turning it off so that code completion actually completes in a reasonable amount of time (~1 second) or having all the helpful insights into my code base. It is almost like QtCreator needs to have 2 threads running. One for the code completion and one for the clang-tidy stuff. -- Mike Jackson On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" on behalf of ivan.donchevskii at qt.io> wrote: Hi! On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. Kind regards, Ivan _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator -------------- next part -------------- An HTML attachment was scrubbed... URL: From vperetokin at gmail.com Thu Jun 14 18:42:00 2018 From: vperetokin at gmail.com (Vadim Peretokin) Date: Thu, 14 Jun 2018 18:42:00 +0200 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> Message-ID: That's a great addition! Can it also run fixits? On Thu, 14 Jun 2018, 6:10 pm Ivan Donchevskii, wrote: > In Qt Creator 4.7 there's a separate tool (Analyze menu) that runs > Clang-Tidy checks over the selected files which does not affect your opened > documents. I hope it solves your problem at least partially :) > ------------------------------ > *From:* Qt-creator qt.io at qt-project.org> on behalf of Michael Jackson < > mike.jackson at bluequartz.net> > *Sent:* Thursday, June 14, 2018 6:03:37 PM > *To:* qt-creator at qt-project.org > > *Subject:* Re: [Qt-creator] What are your favorite clang-tidy checks > > > I tend to go back and forth between turning it off so that code completion > actually completes in a reasonable amount of time (~1 second) or having all > the helpful insights into my code base. It is almost like QtCreator needs > to have 2 threads running. One for the code completion and one for the > clang-tidy stuff. > > > > -- > > Mike Jackson > > > > On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" < > qt-creator-bounces+mike.jackson=bluequartz.net at qt-project.org on behalf > of ivan.donchevskii at qt.io> wrote: > > > > Hi! > > > > On the contributors summit I mentioned that we want to introduce the > "default" set of flags for Clang-Tidy which can be used as a starting point > for analysis and is good enough for some random project developed in Qt > Creator. > > We have an example of it in https://codereview.qt-project.org/#/c/230400/ but > not sure if it is actually the proper list. > > > > Here's the list itself > - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" > > > > Let us know if there's something you would like to add or remove from it. > You can check the whole tree of currently available checks in 4.7 beta or > in one of our latest Qt Creator snapshots. > > > > Kind regards, > > Ivan > > _______________________________________________ Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ivan.donchevskii at qt.io Thu Jun 14 18:55:44 2018 From: ivan.donchevskii at qt.io (Ivan Donchevskii) Date: Thu, 14 Jun 2018 16:55:44 +0000 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> , Message-ID: Yes, there are checkboxes for fix-its so you can apply selected ones. ________________________________ From: Vadim Peretokin Sent: Thursday, June 14, 2018 6:42 PM To: Ivan Donchevskii Cc: Michael Jackson; qt-creator at qt-project.org Subject: Re: [Qt-creator] What are your favorite clang-tidy checks That's a great addition! Can it also run fixits? On Thu, 14 Jun 2018, 6:10 pm Ivan Donchevskii, > wrote: In Qt Creator 4.7 there's a separate tool (Analyze menu) that runs Clang-Tidy checks over the selected files which does not affect your opened documents. I hope it solves your problem at least partially :) ________________________________ From: Qt-creator > on behalf of Michael Jackson > Sent: Thursday, June 14, 2018 6:03:37 PM To: qt-creator at qt-project.org Subject: Re: [Qt-creator] What are your favorite clang-tidy checks I tend to go back and forth between turning it off so that code completion actually completes in a reasonable amount of time (~1 second) or having all the helpful insights into my code base. It is almost like QtCreator needs to have 2 threads running. One for the code completion and one for the clang-tidy stuff. -- Mike Jackson On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" on behalf of ivan.donchevskii at qt.io> wrote: Hi! On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. Kind regards, Ivan _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator -------------- next part -------------- An HTML attachment was scrubbed... URL: From vperetokin at gmail.com Thu Jun 14 19:23:48 2018 From: vperetokin at gmail.com (Vadim Peretokin) Date: Thu, 14 Jun 2018 19:23:48 +0200 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> Message-ID: Excellent. As for the default, I'm not that experienced with all the flags, but the ones you pick will influence a sizeable portion of Qt code in the future :) On Thu, Jun 14, 2018 at 6:55 PM Ivan Donchevskii wrote: > Yes, there are checkboxes for fix-its so you can apply selected ones. > > ------------------------------ > *From:* Vadim Peretokin > *Sent:* Thursday, June 14, 2018 6:42 PM > *To:* Ivan Donchevskii > *Cc:* Michael Jackson; qt-creator at qt-project.org > > *Subject:* Re: [Qt-creator] What are your favorite clang-tidy checks > That's a great addition! Can it also run fixits? > > On Thu, 14 Jun 2018, 6:10 pm Ivan Donchevskii, > wrote: > > In Qt Creator 4.7 there's a separate tool (Analyze menu) that runs > Clang-Tidy checks over the selected files which does not affect your opened > documents. I hope it solves your problem at least partially :) > ------------------------------ > *From:* Qt-creator qt.io at qt-project.org> on behalf of Michael Jackson < > mike.jackson at bluequartz.net> > *Sent:* Thursday, June 14, 2018 6:03:37 PM > *To:* qt-creator at qt-project.org > > *Subject:* Re: [Qt-creator] What are your favorite clang-tidy checks > > > I tend to go back and forth between turning it off so that code completion > actually completes in a reasonable amount of time (~1 second) or having all > the helpful insights into my code base. It is almost like QtCreator needs > to have 2 threads running. One for the code completion and one for the > clang-tidy stuff. > > > > -- > > Mike Jackson > > > > On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" < > qt-creator-bounces+mike.jackson=bluequartz.net at qt-project.org on behalf > of ivan.donchevskii at qt.io> wrote: > > > > Hi! > > > > On the contributors summit I mentioned that we want to introduce the > "default" set of flags for Clang-Tidy which can be used as a starting point > for analysis and is good enough for some random project developed in Qt > Creator. > > We have an example of it in https://codereview.qt-project.org/#/c/230400/ but > not sure if it is actually the proper list. > > > > Here's the list itself > - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" > > > > Let us know if there's something you would like to add or remove from it. > You can check the whole tree of currently available checks in 4.7 beta or > in one of our latest Qt Creator snapshots. > > > > Kind regards, > > Ivan > > _______________________________________________ Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.jackson at bluequartz.net Thu Jun 14 23:19:36 2018 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Thu, 14 Jun 2018 17:19:36 -0400 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> Message-ID: <3DAA51F3-E42C-45C7-B883-A2AE071E1F7D@bluequartz.net> Can I just have it blanket fix ALL issues that it finds in a file? Kind of like “Clang Format” but for Clang-Tidy? I have been toying with writing a script that would attempt to do that for our code base. I guess I should download the latest QtCreator and give that a spin. -- Mike Jackson On 6/14/18, 12:55 PM, "Ivan Donchevskii" wrote: Yes, there are checkboxes for fix-its so you can apply selected ones. From: Vadim Peretokin Sent: Thursday, June 14, 2018 6:42 PM To: Ivan Donchevskii Cc: Michael Jackson; qt-creator at qt-project.org Subject: Re: [Qt-creator] What are your favorite clang-tidy checks That's a great addition! Can it also run fixits? On Thu, 14 Jun 2018, 6:10 pm Ivan Donchevskii, wrote: In Qt Creator 4.7 there's a separate tool (Analyze menu) that runs Clang-Tidy checks over the selected files which does not affect your opened documents. I hope it solves your problem at least partially :) From: Qt-creator on behalf of Michael Jackson Sent: Thursday, June 14, 2018 6:03:37 PM To: qt-creator at qt-project.org Subject: Re: [Qt-creator] What are your favorite clang-tidy checks I tend to go back and forth between turning it off so that code completion actually completes in a reasonable amount of time (~1 second) or having all the helpful insights into my code base. It is almost like QtCreator needs to have 2 threads running. One for the code completion and one for the clang-tidy stuff. -- Mike Jackson On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" wrote: Hi! On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. Kind regards, Ivan _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator -------------- next part -------------- An HTML attachment was scrubbed... URL: From Riitta-Leena.Miettinen at qt.io Fri Jun 15 09:34:41 2018 From: Riitta-Leena.Miettinen at qt.io (Riitta-Leena Miettinen) Date: Fri, 15 Jun 2018 07:34:41 +0000 Subject: [Qt-creator] Reviewing the Qt Creator Manual version 4.7 Message-ID: Hello, I’ve been updating the Qt Creator Manual to reflect the changes made to version 4.7 and now I need your help. Please review the doc snapshot at: https://doc-snapshots.qt.io/qtcreator-4.7/index.html If you find bugs or omissions, please create a patch, report the issues in JIRA, or send me email. Cheers, Leena Leena Miettinen Sr. Documentation Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin riitta-leena.miettinen at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 28A9388BC07A4643A4AA6B83F8558CB8.png Type: image/png Size: 16379 bytes Desc: 28A9388BC07A4643A4AA6B83F8558CB8.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 84FE8B5C999845469503D278EE5F4644.png Type: image/png Size: 1496 bytes Desc: 84FE8B5C999845469503D278EE5F4644.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3EE45EC61B4F429D850645FFA30005E2.png Type: image/png Size: 1794 bytes Desc: 3EE45EC61B4F429D850645FFA30005E2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4B7944C67D8448D7A3FF3AAFCAEA4D0A.png Type: image/png Size: 1645 bytes Desc: 4B7944C67D8448D7A3FF3AAFCAEA4D0A.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D457A20F2AD34DDDB7A07C895A1B2CBD.png Type: image/png Size: 2123 bytes Desc: D457A20F2AD34DDDB7A07C895A1B2CBD.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7FA9F9C104E743B790913B1EB1004849.png Type: image/png Size: 1796 bytes Desc: 7FA9F9C104E743B790913B1EB1004849.png URL: From Eike.Ziller at qt.io Fri Jun 15 09:40:34 2018 From: Eike.Ziller at qt.io (Eike Ziller) Date: Fri, 15 Jun 2018 07:40:34 +0000 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: <3DAA51F3-E42C-45C7-B883-A2AE071E1F7D@bluequartz.net> References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> <3DAA51F3-E42C-45C7-B883-A2AE071E1F7D@bluequartz.net> Message-ID: In 4.7 the code completion should also no longer be slowed down by the checks. So it would be great if you could check that out :) Br, Eike > On 14. Jun 2018, at 23:19, Michael Jackson wrote: > > Can I just have it blanket fix ALL issues that it finds in a file? Kind of like “Clang Format” but for Clang-Tidy? I have been toying with writing a script that would attempt to do that for our code base. > > I guess I should download the latest QtCreator and give that a spin. > -- > Mike Jackson > > On 6/14/18, 12:55 PM, "Ivan Donchevskii" wrote: > > Yes, there are checkboxes for fix-its so you can apply selected ones. > > > From: Vadim Peretokin > Sent: Thursday, June 14, 2018 6:42 PM > To: Ivan Donchevskii > Cc: Michael Jackson; qt-creator at qt-project.org > Subject: Re: [Qt-creator] What are your favorite clang-tidy checks > > That's a great addition! Can it also run fixits? > > On Thu, 14 Jun 2018, 6:10 pm Ivan Donchevskii, wrote: >> In Qt Creator 4.7 there's a separate tool (Analyze menu) that runs Clang-Tidy checks over the selected files which does not affect your opened documents. I hope it solves your problem at least partially :) >> >> From: Qt-creator on behalf of Michael Jackson >> Sent: Thursday, June 14, 2018 6:03:37 PM >> To: qt-creator at qt-project.org >> >> Subject: Re: [Qt-creator] What are your favorite clang-tidy checks >> >> I tend to go back and forth between turning it off so that code completion actually completes in a reasonable amount of time (~1 second) or having all the helpful insights into my code base. It is almost like QtCreator needs to have 2 threads running. One for the code completion and one for the clang-tidy stuff. >> >> -- >> Mike Jackson >> >> On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" wrote: >> >> Hi! >> >> >> >> On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. >> >> We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. >> >> >> >> Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" >> >> >> >> Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. >> >> >> >> Kind regards, >> >> Ivan >> >> _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.orghttp://lists.qt-project.org/mailman/listinfo/qt-creator >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From mike.jackson at bluequartz.net Fri Jun 15 17:07:56 2018 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Fri, 15 Jun 2018 11:07:56 -0400 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> <3DAA51F3-E42C-45C7-B883-A2AE071E1F7D@bluequartz.net> Message-ID: <52249028-6B80-48B8-8D18-A2CB5F1D3875@bluequartz.net> That is Great news. I'll pull it down when I get back from holiday. I really love/hate the clang-tidy checks. Love them because it is like having a really experienced C++ programmer looking over your shoulder the whole time. Hate them because it shows us just how many things we need to fix in our code base. With QtCreator 4.7 looks like I can turn them back on. -- Mike Jackson On 6/15/18, 3:40 AM, "Eike Ziller" wrote: In 4.7 the code completion should also no longer be slowed down by the checks. So it would be great if you could check that out :) Br, Eike > On 14. Jun 2018, at 23:19, Michael Jackson wrote: > > Can I just have it blanket fix ALL issues that it finds in a file? Kind of like “Clang Format” but for Clang-Tidy? I have been toying with writing a script that would attempt to do that for our code base. > > I guess I should download the latest QtCreator and give that a spin. > -- > Mike Jackson > > On 6/14/18, 12:55 PM, "Ivan Donchevskii" wrote: > > Yes, there are checkboxes for fix-its so you can apply selected ones. > > > From: Vadim Peretokin > Sent: Thursday, June 14, 2018 6:42 PM > To: Ivan Donchevskii > Cc: Michael Jackson; qt-creator at qt-project.org > Subject: Re: [Qt-creator] What are your favorite clang-tidy checks > > That's a great addition! Can it also run fixits? > > On Thu, 14 Jun 2018, 6:10 pm Ivan Donchevskii, wrote: >> In Qt Creator 4.7 there's a separate tool (Analyze menu) that runs Clang-Tidy checks over the selected files which does not affect your opened documents. I hope it solves your problem at least partially :) >> >> From: Qt-creator on behalf of Michael Jackson >> Sent: Thursday, June 14, 2018 6:03:37 PM >> To: qt-creator at qt-project.org >> >> Subject: Re: [Qt-creator] What are your favorite clang-tidy checks >> >> I tend to go back and forth between turning it off so that code completion actually completes in a reasonable amount of time (~1 second) or having all the helpful insights into my code base. It is almost like QtCreator needs to have 2 threads running. One for the code completion and one for the clang-tidy stuff. >> >> -- >> Mike Jackson >> >> On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" wrote: >> >> Hi! >> >> >> >> On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. >> >> We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. >> >> >> >> Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" >> >> >> >> Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. >> >> >> >> Kind regards, >> >> Ivan >> >> _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.orghttp://lists.qt-project.org/mailman/listinfo/qt-creator >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From jhihn at gmx.com Mon Jun 18 16:08:56 2018 From: jhihn at gmx.com (Jason H) Date: Mon, 18 Jun 2018 16:08:56 +0200 Subject: [Qt-creator] What are your favorite clang-tidy checks In-Reply-To: <52249028-6B80-48B8-8D18-A2CB5F1D3875@bluequartz.net> References: <4BC0827E-5A1F-465E-8483-78BEA5C5CD9B@bluequartz.net> <3DAA51F3-E42C-45C7-B883-A2AE071E1F7D@bluequartz.net> <52249028-6B80-48B8-8D18-A2CB5F1D3875@bluequartz.net> Message-ID: One thing I would like is a fix-it for a implicit conversion. I'm old school and like the short, easy, old casts: (type) x; (gives "use of old-style cast" message) but the new style: static_cast (val) is much harder to type. It's got _ and <> and I've got to edit behind the variable, which if in an argument list has be dodging commas. If there was a way to click and use the new style, I'd use it. From jhihn at gmx.com Wed Jun 20 19:25:44 2018 From: jhihn at gmx.com (Jason H) Date: Wed, 20 Jun 2018 19:25:44 +0200 Subject: [Qt-creator] Clang-tidy and QML Message-ID: I just noticed that QML is not highlighting the same as QML... property _var_ x: 0 // (underscores added, because it's underlined in green) produces the message "use int or real to improve performance (M311)" Whereas the C++ side is using lightbulbs. Is there/should there be/ a plan to use consistency? Maybe provide fixits? Just something I noticed. From Eike.Ziller at qt.io Fri Jun 22 09:05:20 2018 From: Eike.Ziller at qt.io (Eike Ziller) Date: Fri, 22 Jun 2018 07:05:20 +0000 Subject: [Qt-creator] Qt Creator 4.7 in string freeze Message-ID: <2FD5A54D-FACE-4B88-B89F-7CC3291BDC6F@qt.io> It is roughly two weeks before the planned Qt Creator 4.7 RC, and we have released 4.7 beta2 yesterday, so Qt Creator 4.7 is in string freeze now. Br, Eike -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From jhihn at gmx.com Wed Jun 27 15:58:57 2018 From: jhihn at gmx.com (Jason H) Date: Wed, 27 Jun 2018 15:58:57 +0200 Subject: [Qt-creator] Beta2 Android debugging regression? Message-ID: So this was a bug allegedly fixed, but it seems to have re-appeared. When I run an android app, all I get in the "Application output" pane is "com.company.project" died. "com.company.project" died. "com.company.project" died. I no longer see my debugging output. I did not observe this with beta 1. I'm using Qt Creator 4.7.0-beta2 (4.6.83) Based on Qt 5.11.1 (Clang 8.0 (Apple), 64 bit) Built on Jun 20 2018 05:24:03 >From revision a0083d06fd From steve at blighty.com Sat Jun 30 02:27:29 2018 From: steve at blighty.com (Steve Atkins) Date: Fri, 29 Jun 2018 17:27:29 -0700 Subject: [Qt-creator] clang-tidy segv Message-ID: <59019909-0AA4-4662-96E4-62A8C7B33D14@blighty.com> If clang-tidy with the bundled clang-6.0 in 4.7.0-beta2 fairly reliably SEGVs in clang::DiagnosticRenderer::emitDiagnostic (apparently for any combination of source file and checks that produces an output) is that a bug report to the Creator team or to the LLVM folks? Cheers, Steve From ivan.donchevskii at qt.io Sat Jun 30 23:10:15 2018 From: ivan.donchevskii at qt.io (Ivan Donchevskii) Date: Sat, 30 Jun 2018 21:10:15 +0000 Subject: [Qt-creator] clang-tidy segv In-Reply-To: <59019909-0AA4-4662-96E4-62A8C7B33D14@blighty.com> References: <59019909-0AA4-4662-96E4-62A8C7B33D14@blighty.com> Message-ID: Hi! Ideally both. It should be definitely fixed in Clang but we can help that from our side if we have qt creator bug for that. Kind regards, Ivan ________________________________ From: Qt-creator on behalf of Steve Atkins Sent: Saturday, June 30, 2018 2:27:29 AM To: qt-creator Subject: [Qt-creator] clang-tidy segv If clang-tidy with the bundled clang-6.0 in 4.7.0-beta2 fairly reliably SEGVs in clang::DiagnosticRenderer::emitDiagnostic (apparently for any combination of source file and checks that produces an output) is that a bug report to the Creator team or to the LLVM folks? Cheers, Steve _______________________________________________ Qt-creator mailing list Qt-creator at qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator -------------- next part -------------- An HTML attachment was scrubbed... URL: