Is the cppcheck plugin for QtCreator still doing something? - c++

Here I am on:
macOS Monterey 12.6
Qt Creator 8.01 - Based on Qt 6.3.1 (Clang 13.0, arm64)
Cppcheck plugin 8.0.1 (8.0.0)
And Cppcheck seems to be stuck, after opening/building and closing a few different small projects multiple times I see on the bottom right corner the following:
What should I do?
If I re-open QtCreator then those Cppcheck instances disappear. However they also come back again after repeating the steps mentioned above.

Related

Can not set android clang compilers for Qt Android on Ubuntu

I installed Qt Android 5.15.2 on Ubuntu but there is problem with the compilers. This is what I have set:
And here is what QtCreator detects as compilers:
The first error is displayed here in the Qt version tab:
and also in the Kit tab I see this errors no matter which compilers I set from the available:
Why I got this errors? Can please someone that has android kit on Ubuntu already set, tell me which compilers is using and which paths are for the compilers?
I will add more information for the current compilers or kits if needed.
The problem is that you are trying to use a x86 compiler for Android. You need to install the specific compiler from the Android SDK/NDK. So the good news is that you might be only missing one step (step 2 below)
I tried to install from the Ubuntu stock packages. That was impossible to get to work.
I was able to set it up in the following way:
Download the Qt online installer. Login and DO NOT choose individual packages, install Qt for desktop and Qt for mobile (check the last 3 options). This will install Qt 6 + QtCreator
Run QtCreator after everything finishes (+1.2Gb download). Go to Tools>Options>Devices>Android. Check that Java SDK is ok. On the Android section, choose "Set up Android". Accept all licenses.
This is what you should see in the end:

Debugger with Eclipse on a macOS Catalina

I've macOS Catalina and Eclipse IDE for C/C++ Developer, Version: 2021-03 (4.19.0) and I need to use EclipseCDT debugger. Following the steps at macOS 10.15 Catalina gdb problem for C++ Debugging in Eclipse I still have problems. Namely, the Debug window doesn't show up.
The only difference between my steps and the ones from the tutorial is the gdb version: mine is 10.1, while the other is 8.3.
I've found this FAQ link: https://wiki.eclipse.org/CDT/User/FAQ, where seems to be possible to use LLDB debugger, but I can't find the detailed instructions. Any approach is fine to me, I just need a working debugger

QT enable cross-compiling using MinGW (precompiled)

Good day all
I have been searching for a method of cross-compiling for QT-Creator in Linux for sometime now, and I have been having alot of trouble with it.
Background info
please note: I am on a Linux machine, and would like to cross compile Windows Apps
My system:
Ubuntu Gnome 16.10
QT Creator 4.0.2 (based on QT 5.7)
I have came across a few SO links, a few blogs with broken instructions, etc and one seeming helpful but dependencies could not be found.
I have also attempted another compiler MXE and cloned and attempted to build the MXE compiler from the GIT repo, which failed (no solution for the build error - VTK build error)
I decided to download precompiled MinGW compilers (i686 and x86_x64 versions) from sourceforge
Issue:
In QT Creator, adding the compiler is done without an issue, adding the "Kit" and selecting the newly added compiler, an red exclamation gives an error
The Compiler (x86_windows_msys_pe_64bit) cannot produce code for QT version 5.7.0 GCC 64Bit (x86_linux_generic_elf_64bit)
This occurs for both 32 + 64 bit compilers.
I think that you should have a QT version that matches your compiler ABI. The error tells you that the MinGW compiler doesn't match the Linux version of QT you have used. Therefore, get a windows version of QT and use it instead (just as you've added WinGW).
You can download Qt Binaries from here.

Why is the Analyze menu disabled in QtCreator

I'm trying to analyse (valgrind) a program on linux using QtCreator. But the menu in qt creator is disabled.
I have OpenSuse 13.1. linux on 64bit. This is what i tried so far:
I've checked the plugins dialogue and the Valgrind plugin is greyed out, but selected.
I've checked the installation directory and the plugin is there.
Valgrind is installed (valgrind --version -> valgrind-3.8.1)
valgrind works (valgrind --tool=callgrind ./myprog)
I tried the stock version of QtCreator (2.8.1) and a newer installation in ~/bin/Qt.. (3.4.0)
I tried it with a qmake and a cmake project.
I tried to re-enable the QtQuick plugins. This made the menu work and the Analyse icon on the left appeared, but still no valgrind support.
Can anybody help?
You might need to enable the Devices->RemoteLinux plugin as well.

Mountain Lion no working gdb debugger

I got a new Macbook Air and installed XCode 5 on it. To my surprise Apple does no longer ship gdb with the command line tools. As I am doing lots of c++ coding I am dependent on a good debugger.
What I tried so far:
Install gdb 7.6 via macports and signed the binary.
Debugging from QT-Creator is possible. It stops at the breakpoints but I see no information at all about the stack. Using lldb not possible, I get a weird python error.
Debugging from Netbeans is not possible at all. The Debugger is not stopping at any breakpoint. Apart from that Netbeans is not working with lldb.
Working with XCode is no problem. Everything works as expected.
Problem is I need an IDE that can do remote debugging as I have several Raspberry Pi projects. Developing software directly on the pi with vim is fun but not suitable for bigger projects.
So the question is, has anyone a working debugger on Mountain Lion with XCode 5 installed? IDE in question needs to support remote debugging (eg QT-Creator, Netbeans, Eclipse)
Thank you!
Install Xcode 4.6.3. If you have a developer's account it's available for download at http://developer.apple.com
Encountered the same problem. Finally installed command line tools from xcode 4.6.1 on ML. This package is available on Apple site. It installed GCC-LLVM 4.2.1 and GDB 6.5. Qt Creator was able to build application and start debugging. Debugging is not stable too much; but i can to see call stacks, values and stop on breakpoints. I use it for 32bits build - maybe it matters.
You could also switch from GDB to using the LLDB debugger (although the Qt support is early for this).
See http://stanford.edu/~rawatson/lair/mac.html