Install debugger engine
I'm an old user of Visual studio express 2015 for C++ under Windows 10. I now try to install Qt for making Android apps, having come so far as to build and run the welcome example programs with output on the laptop screen.
When I try to Start debugging I get the message "Unable to create a debugger engine ...". Also under Tools->Options->Build&run->Debuggers there is none auto-detected. I have followed every step in Setting up debugger in the Qt documentation (installing Debugging tools for Windows/CDP and Symbol server, setting CDP paths, etc etc). Can I have a hint of what is wrong?
Thx in advance for any advice.
Hi and welcome to devnet,
Do I understand you correctly, you are trying to setup your environment for Android development but want to use VS2015 for compiling the application ?
In any case, what exact version(s) of Qt did you install ?
@SGaist Yes, I want to build for Android and use the Visual studio compiler (as suggested by the installation). I have installed 5.6, 5.7 and 5.8 (with msvc2015_64).
You can't do that like that, Android development requires the Android SDK and NDK.
You can find more information on how to setup your machine for Android development in the Getting Started with Qt for Android chapter of Qt's documentation.
@SGaist I have also installed Android SDK and NDK, as well as Android SDK tools, JDK, Gradle and USB drivers.
And Qt for Android development ?
@SGaist I think so ...
Qt Creator -> Tools -> Options -> Devices -> Android says "Found 10 toolchains for this NDK. " and after "Automatically create kits ..." it says "Warning Qt versions for 5 architectures are missing." I do not succeed to add Qt versions selecting Options -> Build&Run -> Qt versions. Is that a clue? I have C:\Qt\5.8\msvc2015_64\bin\qmake.exe (and corresponding for 5.7 and 5.6) auto-detected there.
You have installed Qt for Visual Studio 2015.
You need to install Qt for Android.
If you used the online installer, just start the maintenance tool and add Qt for Android.
@SGaist Thank you -- that helped.
Now the problem is that, when I try to run the untitled project appearing when you create a new project, qglobal.h seems to be missing and I cannot find it anywhere in my installation.
C:\Qt\5.8\android_x86\include\QtCore\qglobal.h:45: error: type_traits: No such file or directory
@PA-F Try to add this line to pro file , run qmake again and rebuild:
CONFIG += c++11
@jsulm CONFIG += c++11 was already there and running qmake again did not help.
I can see now that it is not qglobal.h that is missing, but type_traits, as well as cstddef, algorithm and maybe others.
Which version of the NDK did you install ?
Take a look at the Kit you are using. Check whether there's any warning or error message related to the NDK.
They've had some disruptive update recently which might be a possible cause.
@SGaist Under Devices -> Android, after Android NDK location I have a warning "Qt versions for 3 architectures are missing". No other warnings.
I saw somewhere (can't find it again) about a problem similar to mine, related to NDK version 13, related to the order of includes in GCC. However no solution was presented.
Where in my installation are type_traits, cstddef and algorithm supposed to be found? How do I give the appropriate directive in the .pro file (or anywhere)? May type_traits, cstddef and algorithm not be installed (Windows search can't find them)??
These files should be provided by the Android SDK/NDKs
The tool chains missing is a warning that is harmless in the sense that you are not likely going to build your application for these missing architectures. Unless of course the warning concerns the targets you want to build for.
@SGaist Do you have a suggestion for what I should do?
@PA-F Sorry -- I should have given some further information to give you a chance to help.
When I try to build untitled.pro I get the messages:
In file included from C:\Qt\5.8\android_x86\include/QtGui/qtguiglobal.h:43:0,
type_traits: No such file or directory
In qglobal.h there are error marks for
but not for
For instance <stddef.h> is found in
Does this give you any idea?
Following that wiki entry, recent versions of the Android NDK are problematic. It is recommended to use ndk-r10e.