Hi,
Currently libformat is statically linked into the ClangFormat plugin because we
require a custom patch for it.
In theory we can make our stuff work through the clang-format binary like it's
done in Beautifier but the indentation won't work properly with different
binary (for example the
Hi,
Should be possible to do. "file a feature request in JIRA" - yes, please. You
can assign it to me, I think I touched this part the last time.
Also please specify what do you mean by "change the compatibilty in our .pro
file to MSVC2013".
Kind regards,
Ivan
Hi!
It seems you are using ClangFormat plugin and it crashes in applyReplacements
call.
It's highly experimental in the first beta so I can imagine it malfunctioning.
So the best thing to do at least until beta2 is to disable it temporarily :)
Kind regards,
Ivan
Hi!
We use defines we get from the compiler which is set in your current Kit. It
might be possible that we have some bug in the process of getting them.
Please create a bugreport (bugreports.qt.io) with a small code example so we
can reproduce the issue and fix it.
Kind regards,
Ivan
Hi!
If the initial parsing time is absolutely crucial for you you can turn
ClangCodeModel plugin off (it's turned on be default since 4.7). ClangCodeModel
provides more precise results but takes longer to parse files. We did some work
to make it faster but the most recent part of it was mostly
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:
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@qt-project.org
Subject: Re: [Qt-creator] What are your favorite clang-tidy
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"
mailto:qt-creator-bounces+mike.jackson=bluequa
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@qt-project.org
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
Hi!
Currently we don't have a public page where we put all packages revisions.
But I've already mentioned in some of the mailing list questions that it
currently should be fine to use master branch of Clazy.
In the nearest future we want to switch to our LLVM fork instead (which will be
esday, April 24, 2018 5:17:42 PM
To: qt-creator@qt-project.org
Subject: Re: [Qt-creator] Building LLVM/Clang with Clazy
Hi,
I used Clazy 1.3, tagged release.
Can you tell me which exact commit you used?
--
Best regards / Pozdrawiam,
Andrzej Telszewski
On 24/04/18 17:07, Ivan Donchevskii wrote:
iam,
Andrzej Telszewski
On 24/04/18 16:43, Ivan Donchevskii wrote:
> Hi!
> But you wrote that
>
> "I applied all the patches except for 1*0_QTCREATORBUG-15157*, i.e. I
> built LLVM without Clazy support."
>
>
> Without these patches you won't be able to build claz
Hi!
You write that you want to build it without clazy but you issue comes from
clazy folder.
Just remove this folder, it does not come with clang_tools_extra package :)
Regards,
Ivan
From: Qt-creator
As far as I know store expects both in the same apk.
So as I understand you suggest having two different versions in store for
different platforms?
That may work. Thanks for one more workaround :)
Regards,
Ivan
From: Qt-creator
Good question!
I also did not find a way to do that. I assume that it's not possible currently
because several kits are involved at the same time to support such feature.
Prove me wrong or let's think how to solve that.
As a temporary solution you can build only arm - it is still supported
Hi!
I also saw that clang-tidy can break code model in some files. If you want to
fix clang-tidy you can try to run it with the same flags as a standalone tool.
Then if clang-tidy standalone also breaks you can try to fix it. If not please
report at bugreports.qt.io and ideally provide a
Hi!
In fact we currently build clang only once with all plugins since it has become
possible to put clazy in clang/tools/extra folder.
All steps are in our clang build script
(https://github.com/qtproject/qtsdk/blob/master/packaging-tools/build_clang.py)
It's still pretty complicated so
ctly:
https://i.imgur.com/3fSaHnQ.png
On 16/02/18 09:13, Ivan Donchevskii wrote:
> ClangCodeModel should work fine if you have set up your Android toolkit
> properly.
>
>
> I'm able to reproduce your issue when I have wrong NDK location set in
> the Android settings (settings
ClangCodeModel should work fine if you have set up your Android toolkit
properly.
I'm able to reproduce your issue when I have wrong NDK location set in the
Android settings (settings->devices->android).
Point the proper folder and your errors should be gone.
Kind regards,
Ivan
Btw. - it would be nice if the QtCreator clang-tidy plugin would (optionally)
make use of a .clang-tidy config file (to share it with clang power tools for
example).
It's definitely in our plans. We've already discussed how we can support
different ways of configuring tidy (with file and with
Hi!
Options are disabled because they've become part of the code model
configuration and are turned off by default.
So to be able to set clazy options in recent builds you need to create your own
configuration (you can press Copy... button for example).
We are still thinking how to improve
22 matches
Mail list logo