Unable to debug Android App (Windows + Qt Creator 12 + LLDB)

[CodesInChaoss]

@CodesInChaoss

The exact version of UBUNTU as advised by QT documentation....

Now,' hilarious' is not a word which would do justice, or is it..

[CodesInChaoss]

The above is shown... On a fresh Ubuntu installation... on default 5.15.16 settings...... online installer...

after the installation is finished and when attempting to launch Creator 12

[JoeCFD]

@CodesInChaoss Install Qt 5.15.2 and use Qt Creator which comes with Qt 5.15.2 on Ubuntu 22.04 That is what I did with my project for Android. No issues with debugging. I will have a shot at Qt 6.6.2 with Qt Creator 12 for Android on Monday. I know it is messy and too many settings.

[CodesInChaoss]

@JoeCFD

Thank you kindly for your reply, so few people here willing to give a helpful hand.

Yet, since we decided to pay for QT to in order to avoid the inherent bogs of open source (which we've been using years) we rather stick to QT creator which is compatible with QT 5.15.16 (and the prior version which you suggested is not).

Follow instructions above.

Would be nice for Qt team to improve installer as they state no additional libraries would be needed on this very Ubuntu.

Follow steps above to install missing libs.

[CodesInChaoss]

@CodesInChaoss

another incompatibility

Ubuntu comes with TSL 3.0 not 1.1.

[JoeCFD]

@CodesInChaoss Ubuntu 22.04 may be better. Ubuntu 20.04 is kind of old. At home I installed 23.04.

[CodesInChaoss]

@JoeCFD

well we know very well BUT that's what QT recommends for 5.15.16, and we want simply to be able to debug above anything else.

[CodesInChaoss]

We've now compiled OpenSSL 1.1.1 from sources , installed fired up QT Creator 12, the Android SDK autonomous installation process now commenced fine.. let us hope for the best.

Fingers crossed.

[CodesInChaoss]

@CodesInChaoss

[CodesInChaoss]

@CodesInChaoss

[CodesInChaoss]

@CodesInChaoss

so we've downloaded by hand; looking good;

but

The Kits... not so much...

[CodesInChaoss]

Restarting QT Creator help for the kits to properly initialize:

now the only warning is that a device is missing.. well because it's missing as of now

[CodesInChaoss]

@CodesInChaoss

We've got a single Multi-Abi kit, let's look inside

same settings as on Windows.

we would switch compiler to aarch64, which we believe should be by default by now. Few 32 bit devices around.

Now the question.. on Linux... we should be after LLDB correct? not gdb

it's the freedom oriented realm where all the Linux level latest goodies are expected to shine, right?

Let the Microsoft burdens be upon us no more.

Fingers crossed.

let's try to debug.

[CodesInChaoss]

@CodesInChaoss

eh.. it's been long since I've seen password field neither encrypted nor 'asterixed'...

[CodesInChaoss]

Yet another bug

Subversion sub-system would recognize that the 'svn' command might not be available and indicate in red.

When subversion is installed on system it would be red no more... but QT Creator 12 would still deem the sub-version NOT TO BE CONFIGURED.

No error message. 'svn' in red NO MORE.

only once user provided an explicit absolute path would Creator assume SVN to be configured and shown the -subversion- sub-menu in Tools.

[CodesInChaoss]

Even on Linux, after a single restart of the machine the Debugger settings within of a Kit - these were GONE.

haven't tried to debug yet.

[CodesInChaoss]

@CodesInChaoss

no idea what it's about?

[CodesInChaoss]

@CodesInChaoss it's f*** nightmare the QT experience coooome oonnnnn..

[CodesInChaoss]

@CodesInChaoss

the above helped

1. install dos2unix
2. cd android && dos2unix ./gradlew

(...)) f**** !

[CodesInChaoss]

@CodesInChaoss
at least now it compiled (..)

Now.. to debug.. over a network... DO I DARE?