Mobile and Embedded

@1XU7 On Windows, if you install Qt you will get a preconfigured terminal in start menu - try to use that one to build.

@Prabhakaran said in need help on build for android:

give me any sample codes for android

What sample code do you need?
Also take a look at:

https://doc.qt.io/qt-6/android-getting-started.html https://doc.qt.io/qt-6/android.html

SOLVED: I had to type this command:
sudo chmod $USER:$USER $ANDROID_SDK_ROOT
I hope this will help unfortunate people like me, who couldn't figure this out for days or even months.

Android is crazy man.... is crazy... look... i use Unreal Engine and it setups Android SDK too.. that was enought to take down Qt Android SDK configuration... i can not understand why Android has so many versions of versions, why don't they have some universal platform or something like that..

i have the table error too.. toggled off API 35.. but still Qt tries to use it..
i guess i will make a clean (another) Windows install and try again..

@jsulm , Thank you so much. Now I understood. You got a new follower now.

I have resolved the issue, as the /usr/share directory was not included in the sysroot.

Here is the same code using appDataLocation

void DatabaseManager::OpenConnection() { // Configure the database connection parameters for SQLite m_db = QSqlDatabase::addDatabase("QSQLITE"); // Use QStandardPaths to get the application data location QString dbName = "identifier.sqlite"; QString dbLocation = QStandardPaths::writableLocation(QStandardPaths::AppDataLocation); QString fullDbPath = dbLocation + "/" + dbName; QDir dbDir(dbLocation); if (!dbDir.exists()) { if (dbDir.mkpath(dbLocation)) { qDebug() << "Created application data directory:" << dbLocation; } else { qDebug() << "Failed to create application data directory:" << dbLocation; return; // Exit if the directory cannot be created } } // Set the SQLite database file location m_db.setDatabaseName(fullDbPath); // Check if the database file exists in the application data location if (!QFile::exists(fullDbPath)) { qDebug() << "Database does not exist in AppDataLocation, copying from resources."; // Path to the resource database file QString resourceDbPath = ":/resources/identifier.sqlite"; // Adjust the path to your resource file // Attempt to copy the database from resources to the writable location if (QFile::copy(resourceDbPath, fullDbPath)) { qDebug() << "Database copied successfully to AppDataLocation."; // Set file permissions to writable (necessary for some platforms) QFile::setPermissions(fullDbPath, QFileDevice::ReadOwner | QFileDevice::WriteOwner); } else { qDebug() << "Failed to copy database from resources."; return; // Exit if the database cannot be copied } } // Open the database connection and handle success or failure if (m_db.open()) { qDebug() << "Database opened successfully."; // Sample query to verify the database contents } else { // Handle connection error qDebug() << "Database failed to open."; qDebug() << m_db.lastError().text(); } }

My workaround for the time being is as follows:

Construct the Java class when the related C++ class is constructed Set Activity for the class Call static methods like before

Java:

private static Activity m_activity = null; public void setActivity(Activity activity) { m_activity = activity; return; }

also change all methods that previously called QtNative.activity() to now check for and use m_activity instead.

C++:

mJNIInstance = QJniObject("the/qualified/ClassPath"); if (mJNIInstance.isValid()) { mJNIInstance.callMethod<void>("setActivity", "(Landroid/app/Activity;)V", QNativeInterface::QAndroidApplication::context().object()); } else { // output a warning or error }

I needed to add developer mode and trust the developer on my iphone

@devin_qt i'm may find out how to solve this problem,you can fix it by changing the NDK_ROOT in qmake.conf.although must using Absolute path to build the project.
qmake.conf in my set is C:\Qt\5.15.2\android\mkspecs\android-clang

@Qreator35 Are you aware of Qt's CAN support?

Hi, jsulm,

Thanks for your reply.

Yeap, I want the app to always stay on top.
Because the Android system have a Activate Window always on the top of the screen.
My program app must be in front of the Activate Window. And I must.
I implemented a demo in Android Studio by using TYPE_SYSTEM_ALERT to on the top.
But my full program is implemented using Qt.

Need your advice.
Daniel

Hi, AnQuter,

Is your question solved?
// setContentView(R.layout.dream); - how to use Qt app layout?

How can I load Qt mainwindow.ui in java code?
Thanks a lot.

Hi and welcome to devnet,

From the looks of it, no there's nothing directly in Qt for that.
You should take a look at the bug report system to see if there's something related to that.

I am now facing a problem with NetworkAuth and WebAssembly. I opened another request but got left behind
https://forum.qt.io/topic/159704/how-to-install-qtnetworkauth-for-webassemby/8?_=1732390034893

Just as I posted that I found a workaround, but I would still like to know how to correct this.

For those that are having the same issue and just "want it done" here's what I did: On a fresh bitbake run, when gn-native failed, it showed me the command-line that it ran, which looked something like this:

cd /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/build && /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/recipe-sysroot-native/usr/bin/python3-native/python3 /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/git/src/3rdparty/gn/build/gen.py --no-last-commit-position --out-path /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/build/ --cc /home/aaron/yocto/build-raspberrypi-armv8/tmp/hosttools/gcc --cxx /home/aaron/yocto/build-raspberrypi-armv8/tmp/hosttools/g++ --ld /home/aaron/yocto/build-raspberrypi-armv8/tmp/hosttools/g++ --platform linux --ar /home/aaron/yocto/sources/poky/scripts/native-intercept/ar --qt-version 6.8.0.qtwebengine.qt.io && /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/recipe-sysroot-native/usr/bin/ninja -C /home/aaron/yocto/build-raspberrypi-armv8/tmp/work/x86_64-linux/gn-native/6.8.0/build/ gn

Right around where it says gen.py notice there's a bunch of flags: --no-commit-position --out-path etc. Somewhere in those flags, add --allow-warnings and re-run that command. gn-native will (hopefully) build successfully, with warnings, and you will be able to proceed with your Yocto build.