Qt Creator and other tools

@J-Hilk said in How to disable ""shadow build" ?: thats not true, you can specify the path of your shodow build and nothing is preventing you of using a subfolder of your source folder Well, then this has changed. It still shows a warning when I do that. And I believe that this initially didn't work.

@cristian-adam I tried the version 11.0.2 from the GitHub release, and indeed, the issue was not present. It appears to be a problem with Qt 6. Looking forward to the next official update being able to completely resolve this issue. Thank you! [image: db85d3ac-86f9-49b8-93dd-95c9da8e7d66.png]

@Robert-Hairgrove said in Qt Creator bug with braces matching: I have to close Qt Creator and reopen it, at which point everything is fine once again. I never encountered such issues with earlier versions of Qt Creator, I must say. Sadly I most certainly have always experienced syntax highlighting going wrong. And having to exit and re-enter and then it sorts itself out. Over a number of Qt Creator versions, and I haven't gone anywhere near 11.x. So whether it's any worse or better I don't know :)

It looks like you are on a Linux system. On a Ubuntu system you need to do a sudo apt-get install build-essential to get the compiler / make / debugger tools. You should also do a sudo apt-get install cmake ninja-build.

@AnneRanch I am confused about one thing: you say you are cloning, right? How exactly? How and what do you configure, compile? If you are cloning qt5.git, the latest dev (i.e. 6.7) is downloaded. If you then check out a version below 6.7, artifacts of sub modules existing only in dev will remain in your source tree. These would also produce the error messages mentioned. They have to be deleted with git clean -xdf. To answer your final question: yes.

We're facing the same problem, depending how the certificates are been created and fixed it using the following code. QOpcUaApplicationIdentity QOpcUaPkiConfiguration::applicationIdentity() const { ... if (extension.name() == QLatin1String("subjectAltName")) { // OID: 2.5.29.17 QString uri; const QMap<QString, QVariant> valueMap = extension.value().toMap(); if(valueMap.count()>0) { uri = valueMap[QLatin1String("URI")].toString(); } else { QByteArray valBytes = extension.value().toByteArray(); qsizetype urnStartInd = valBytes.indexOf(QStringLiteral("urn:").toUtf8()); //TODO[QT6]: use QByteArrayView here in QT6 qsizetype urnEndInd = (urnStartInd < 0) ? -1 : valBytes.indexOf('0x82', urnStartInd); if(urnStartInd != -1) { uri = valBytes.mid(urnStartInd, (urnEndInd < 0) ? -1 : urnEndInd-urnStartInd); } } const QStringList token = uri.split(':', QString::SkipEmptyParts);

Notice the Qt Version: None part. That's the reason you can't select the kit. In the Qt Versions you need to either click on Link with Qt ... or configure manually a Qt version.

I would say as soon as you link against OpenSSL and thus ship it with your application you would have to comply with the OpenSSL license. If you don't want to think about this you'd need a Qt version that does not link against OpenSSL (may compile it yourself). I don't think a license only applies if you actually call a function from that library. (But I'm not a lawyer.) Solely relying only on http is going to be difficult. This will only work for software you write for yourself on both ends. Most webservers will only allow https connections and even browser are moving in that direction. Not using a secure connection will hinder interoperability in the future.

@thinkingfl So your code itself does not create any console. Maybe I'm mistaken, but aren't you supposed to tick Run in terminal? Else what is the point of that? Without it std::cin won't be open hence it runs to completion.

@J-Hilk Thanks. It does work. I still have to close and reopen the file for the display to update but it does what I wanted.

@aamp So, did you do what the error message suggests: "Check the Issues view for details"?

I think the button @Flaviu-0 is talking about has an icon of a monitor on it. On opening it, a two-column menu appears to the right. In the right hand column of this menu under "Run" Is a list of the executable in the project. Each line has a button which which will launch the executable. I was able to choose the startup with a right click on one of these executable, which would highlight that line. With that line highlighted, I could back out and use the debug button, and it would launch the executable which I'd left highlighted.

Please do create a bugreport at https://bugreports.qt.io/ and attach the core file.

If you built Qt yourself, you should see the enabled backends in the configure output. You should also get some hints when enablign the qt.network.ssl category, e.g. by setting QT_LOGGING_RULES=qt.network.ssl=true environment variable before launching your application.

@Creaperdown said in Debugging: "warning: process x is already traced by process y": process 5260 is already traced by process 5258 Can you try the solution described here: https://rajeeshknambiar.wordpress.com/2015/07/16/attaching-debugger-and-ptrace_scope/ ? Thanks!

@Paul-Colby Thanks, Paul. I use Perforce, and it's often the only thing that saves me in these situations. But in a better world, Qt's logging would let me know the module and line number of the error.

@1XU7 I fail to understand the problem. You prefer NeoVim. It looses its settings when you format your computer. That's why you want to use Qt Creator as a simple editor (without "such modern things"), expecting that its settings survive re-formatting? I am afraid, that's not gonna happen. NeoVim typically saves its settings in the $XDG_CONFIG_HOME/nvim directory, which very likely translates into ~/.config/nvim/. I'd save that directory on a memory stick before re-formatting the PC, and recover it from there.

Hi, Might be a silly question but, is your main project already based on the subproject template ?