Mobile and Embedded

Hi and welcome to devnet, I think you are going to be interested by the QtAndroidExtras. It does provide tools to facilitate JNI code writing.

Hello, I faced the same problem and searched everywhere for hours. At the end found out that when i created new project i didn't add the preferred choice of devices like arm64-v8 and all other. Make sure you did while creating new project.

@sgaist said in Android Project - Make.exe parallel jobs: The ordered keyword is a quick and easy way to build the subprojects in the order you want. The correct way is described in the documentation but also on this nice article. @SGaist thanks for the article, it is very interesting and useful, anyway even by switching to the suggested configuration (avoiding ORDERED) did not solve the issue for me. @koahnig said in Android Project - Make.exe parallel jobs: @paolot Basically you should be able to start the Android make on a command prompt outside of Qt creator at the same location where qt creator does. When it would be concurrent under these conditions it would point to some specifics of the Qt run environment for starting Android make. I have not experienced such a behaviour so far. Therefore I consider as odd. I completely agree with you, my only fear is that QMake is doing something wrong when creating the top-level Makefile and it's somehow preventing the build process to go parallel. I could try writing a custom Makefile just building the subfolders, I'll let you know!

@themts said in run as root on target device (cross compile raspberry): I'm using this lib I know. But this lib simply access the device file for the gpio. That's why I suggested to change the access rights for it or add your user to the group set on the device file. Did you check the link I provided?

@bogong For me it's normal develop qt (also for mobile application), but in this time I must develop a strange case, I must use a native controller (that it can't be emulate in qt/qml) and from this I must start the qml GUI. It's all ok, I see the qml elements but I can't catch the user interaction, not press button, nothing. I started from Qt project where I added native object-c files, AppDelegate, other native controller, etc.

I tried follow above link, but error still happens as I mentioned in second comment.

Look at this topic: https://forum.qt.io/topic/77166/unique-android-device-id/5

I'm not sure that it is possible with qmake. But, you can try to use the next version of QtC (I hope, it is 4.11?). There are added new MSP430 architecture. You can use e.g. future QBS 1.15? instead of make, because I know that it will work. You even can take a look the baremetal examples, comes with that QBS. There are provided simple example for MSP430. PS: Maybe, you also can use CMake instead of QBS, but I'm not sure.

What do you mean by own application ? I thought you were using the notification example ? Just one thing, your thread title mentions push notifications, this example doesn't implement them.

@ali1377 In my idea maybe with connecting to a server made by my code with nextPendingConnection function we don't loose port but with this software it change. That is my idea and maybe it's no true.

@sekhar said in arm-linux-gnueabihf-g++: Command not found: but it does't work. It doesn't look like a good troubleshooting report... What does not work? didn't it brew coffee for instance? Please provide any error output if you mind.

Yes, it works well with xkbcommon enabled. Thanks a lot. Best regards, Eric

@closx said in How Can I Run a Script That Won't Terminate With Qt App?: That worked. Great. Please mark your post as solved! Thanks.

@tolik said in LOCAL_SHORT_COMMANDS for QMake: CreateProcess(F:... .... make: *** [libA.so] Error 87 You should also post what is between these two lines (where you have "...." now)...

I used the Qt app on my smartphone because It allows porting an application to multiple platforms through simple recompilation.

@raven-worx yes, exactly. And I also tried Keys.onNumberSignPressed, but no effect yet

Hi, Did you check if there's a kernel panic/warning in your logs ?