Add Qt6 ready dev-qt/qt-creator-9999

[Peter-Levine]

• dev-qt/qttranslations: SLOT=6 initial commit

• dev-qt/qt-creator: bump 9999
  Switched from the qmake to cmake buildsystem. Added support for the
  Coco code coverage tool. The 'git' USE flag now also builds the gitlab
  plugin. The 'wayland' flag was added to enforce built-with-use
  dependency. 'imageviewer' flag is added for conditional dependence on
  dev-qt/qtsvg. clangd functionality now depends on >=clang-14.*.

Closes: #252
Signed-off-by: Peter Levine plevine457@gmail.com

[AdelKS]

Hello!

Thanks for this work ! It compiles fine and well. I unmasked the Qt 6 packages so it pulled them off as a dependency, I suppose that's on purpose.

Something that is more important to me, did you find a way to enable static analysis of C++ 20 code ? Including for example string_view through #include <string_view> makes the code analysis complain. Probably because it's limited to C++17. I also got this message, complains about stddef.h not existing when including vector.

Clang Code Model: Error: The clangbackend executable "/usr/libexec/qtcreator/clangbackend" does not exist.

In Qt creator 6.0 it works with a simple CONFIG += console c++2a in the .pro file.

[AdelKS]

Okay the ClangCodeModel doesn't work even without trying to enable C++ 20, it gives errors with this

test-cpp.pro

TEMPLATE = app
CONFIG += console
CONFIG -= app_bundle
CONFIG -= qt

SOURCES += \
        main.cpp

main.cpp

#include <iostream>

using namespace std;
int main()
{
    cout << "Hello world!" << endl;
    return 0;
}

it shows these error messages:

main.cpp:1:10: In included file: 'stddef.h' file not found
wchar.h:35:10: error occurred here

main.cpp:6:10: Invalid operands to binary expression ('std::ostream' (aka 'int') and 'const char[13]')

[AdelKS]

I checked in vscodium with clangd and it does not issue the same error messages. So the issues is most likely not with clangd, but maybe with how it's getting configured by Qt Creator.

[Peter-Levine]

@AdelKS It looks like I might have overlooked the necessity of certain tools by placing all of them behind a default-disabled tools USE flag. clandbackend should be governed by the clang USE flag, among other issues. Please rebuild with tools enabled and confirm whether you can still observe the issue.

[AdelKS]

Hello, enabling the tools use flag did not solve the issue. However, putting this in ~/.config/clangd

CompileFlags:
  # Treat code as C++, use C++20 standard, enable more warnings.
  Add: [-xc++, -std=c++20, -Wall, -I/usr/lib/clang/14.0.4/include]

especially the -I/usr/lib/clang/14.0.4/include, solves it. Maybe the build can fix this, because it used to work in Qt Creator 6.0 without user intervention.

[Peter-Levine]

Can you confirm in Tools -> Options -> C++ -> Clangd that Path to executable is /usr/lib/llvm/14/bin/clangd and Insert header files on completion is checked?

[Peter-Levine]

I have run into this: QTCREATORBUG-27623: clangd says it can't find stddef.h.

[AdelKS]

Can you confirm in Tools -> Options -> C++ -> Clangd that Path to executable is /usr/lib/llvm/14/bin/clangd and Insert header files on completion is checked?

Yeah, it does not fix it by doing that alone. It looks like I really need to do the workaround I shown above by setting a file in the .config folder.

[Peter-Levine]

Try with 11.0.2.

[Peter-Levine]

Given that the latest qt-creator ebuild was pushed without plugin-enabling USE flags, it seems that the previous resistance to such an approach (eg., gentoo/gentoo#26675 (comment)) has been reversed.

Closing.