@MLeone said in Using qmake and it can't find qtquickcontrols2: @SGaist I create a folder inside the src folder, called qt-biuld. Then I do -prefix ../qtbase You are installing (make install) into qtbase, so it's not a clean build. Pick a different install target directory, like $PWD or something entirely different.

I am able to compile the project with serialport now after reinstalling qt5 > sudo apt-get install qt5-default But I've got different error now which I think is a different issue altogether. Unable to query physical screen size, defaulting to 100 dpi. To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters). QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader Could not link shader program: "" QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShaderProgram::uniformLocation( texture ): shader program is not linked

@SGaist said: mkspecs/device/linux-rasp-pi2-g++ Shouldn't it maybe be mkspecs/device/linux-rasp-pi-g++ (without the 2)? In his makefile there is this line: INCPATH = -I../threadtest -I. -I/usr/local/qt5/mkspecs/devices/linux-rasp-pi-g++

Old post but I had the same error; I had to build qtdeclarative BEFORE qwebchannel to solve this error.

@Zevero I had the same problem, is there a solution for the mouse click that doesn't work in the web pages.

Realised buildroot hadn't copied over a config.txt to the boot partition of the SD card. Copied across a minimal config and set configured a few arguments as stated in this thread. hdmi_ignore_edid=0xa5000080 hdmi_group=1 hdmi_mode=16 That forced the RPi into 1080p mode and now my QT app is displaying correctly at 1920x1080.

@Wieland Yes, that seems a better idea, I'll do that, thanks for your help :)

@mrjj Yes, What I did was QFontDatabase::addApplicationFont("/usr/share/fonts/truetype/Open_Sans/OpenSans-Regular.ttf"); and then select "Open Sans" on the QtDesigner

@SGaist Indeed :)

https://forum.qt.io/post/561514 Please Solve this bug also related to this

Hi and welcome to devnet, Qt 4.6.7 ? Looks pretty outdated, IIRC you should have at least a Qt 4.8 version available. Are you compiling directly on the Pi ?

Hi, Did you compile your application with your desktop Qt and then copied it over the RPi2 ?

You're welcome ! Don't hesitate to ask them in separated threads (don't forget to search the forum though, there are already a lot of questions related to the RPi) :) If you're not lost anymore, please mark the thread as solved using the "Topic Tool" button so that other forum uses may know a solution has been found :)

I never got around to solve this issue, so due to time constraints i reverted to compile natively on the Raspberry Pi.

Hi, You have several wiki pages about Qt and the Raspberry Pi, see here for a start.

Were you able to solve this issue? I ran into the same problem on a Virtual Machine with Ubuntu Server 14.04

Hi and welcome to devnet, Did you double check the that sudo apt-get install qtcreator ran successfully ?

Welp, I'm VERY close at this point thanks to some helpful information on the ODROID forums (I am building using a Pi2 and an ODROID C1). At this point, I'm stumbling on Chromium, which the current set up seems to be setting it for a Linux desktop build running gyp_run.pro. The problem is that this causes the following error: gyp name 'target_arch' is not defined while evaluating condition 'use_qt==1 and target_arch=="ia32"' in /home/flame/builds/qt5/qtwebengine/src/3rdparty/chromium/base/base.gyp I'm still trying to solve the KHR issue on the Pi (despite already updating the header), but for now, the chromium situation is what has me in a gridlock. I can override the desktop build and instead recommend a cross compile in reference to itself, but I'm unsure as to how well this will go. I am making documentation of what is going on so far so that I can relay an easier to follow guide for people who also are trying ot compile natively for the Pi.

@Dan90 You are assigning a value to a pointer, but data is actually an array of "unsigned char": unsigned char *data = 0b10000000; Instead you should do (C++11): unsigned char data[] = { (unsigned char)0b10000000 };

Hi and welcome to devnet, Glad you found out and thanks for sharing your findings. Since you have it working now, please update the thread title prepending [solved] so that other forum users may know a solution has been found :)

Good ! Since you have it working now, please update the thread title prepending [solved] so other forum users may know a solution has been found :) Also, while browsing the forum, consider up-voting answer that helped you, that will make them easier to find for everybody :)