I haven't played with that system recently but AFAIR, you should be able to build the sysroot for your system on your desktop machine. Then you could use scp to copy the bits you need over to your device.
Doesn't your system provide a possibility to start from another device like a SD card or even a nfs ?
I got it to work by changing 2 things
export CPPFLAGS="-Os"
And by removing the prefix in the configure, and installing it twice ( one in the sysroot of the toolchain ) and the other in the filesystem for the target
sh $ICU_SOURCE_DIR/source/configure --host=arm-cortex_a8-linux-gnueabi -with-cross-build=$ICU_HOST_DIR --prefix=""
if ! make -j5 DESTDIR=$SYSROOT install; then
echo -e "${RED}Error making ICU Target ( sysroot )!${NC}"
exit 1
fi
if ! make -j5 DESTDIR=$PREFIX install; then
echo -e "${RED}Error Installing ICU Target ( filesystem )!${NC}"
exit 1
fi
You have an error in your .pro file. Right after the QT += opengl line you have QT = core gui which resets the content of the variable to core gui. That's why you can't get the OpenGL module.
Okay... finally i solved it. Nothing to do with .pro file or PLUGIN macro. It was a basic PATH issue. qmake was searching for 'plugin' directory in /PREFIX path not in /SYSROOT/PREFIX path. I just copied all plugin directory from /SYSROOT/PREFIX to /PREFIX directory. I know this may not be the right way, but it temporarily solved my issue. If someone could suggest the correct solution please let me know.
@zappy
Hello.
Have you looked at the bug report in the other thread you were following? Apparently there were some bug in the static building for Qt 5.5 and it's fixed in Qt 5.6.1 (https://bugreports.qt.io/browse/QTBUG-51071). So aside from upgrading, am at a loss ...
@mvuori yes i did check these solutions but i have no idea about these compiler directives. How do i use them in QtCreator. And it throws error for only one project and my other projects are working fine.
Hi,
Because usually, it's the central widget of a QMainWindow that will have the keyboard focus thus get the keyPress/Release etc. events.
You can put an event filter on that widget to do what you want.
Hope it helps
@Ryan-Lee Set QT_DEBUG_PLUGINS variable before starting your app and analysehttps://doc.qt.io/qt-5.10/debug.html its output.
See https://doc.qt.io/qt-5.10/debug.html
