I'd recommend using some other prefix for your environment variable. At some point it could be used by the project or some colleague of you might think it's an official environment variable used by the Qt project.
Damn, I was hoping differntely x), but it is super easy, and in my opinion not promoted enough, before that Tweet I had no idea what Qt For Device Creation would support. I knew it existed, but that was as far as it got.
There's still the 30 day test trial I could use, and I'll contact the support, maybe theres a single/private device license that can be negotiate...
I'm not convinced that any proactive action ought to be required, but I have verified that adding qputenv("DISPLAY", ":0"); before creating the QApplication instance does indeed work.
Why would you like to cross-compile the WiringPi library? I guess the usual way is to compile WiringPi locally on the Pi, which is quite simple and fast. During cross-compile of your app you just need the header and an additional
LIBS += -lwiringPi
in your pro file. (Assuming proper paths for the system directories of your pi are set in your cross compile environment.)
Check, if you already have WiringPi binaries on your Pi. If yes, you should get something like
thx for your reply, yes i try to set all QT_QPA_EGLFS_PHYSICAL_WIDTH = 194, QT_QPA_EGLFS_PHYSICAL_HEIGHT= 110
QT_QPA_EGLFS_DEPTH= 20 (all im mm for 7" Touchscreem Display). But i'm still having the same problems.
Fixed this issue myself. Took some crash course learning but I realized fixQualfiedLibraryPaths in the cross compile repo in the aforementioned Raspberry Pi Beginners Guide, just don't work. Running this, it wasn't fixing any symlinks at all, and I was not sophisiticated enough to understand it wasn't doing anything...
I have now found a solution where i shutdown my system properly after getting a Can Message from my controller, and added an external power suply which stays 4 secs longer than the rest of the system . So that is enough time to shutdown.
Everything works perfect now.
Thanks a lot
I guess you cross-compile on a host. I once tried to cross-compile a newer Qt version for Pi while my host had an older release installed. Although I tried to keep both source trees well separated, i never managed to get a successful build. Then I started from scratch with Qt5.6.2 for both host and Raspberry and everything went fine.
Probably you use unintentionally header and implementation files from different Qt versions.
Please double check you -sysroot in the configure command line and which sources are visible from where you execute configure.
I have solved my problem by myself. So if anyone has the same problem. Here is the way I found my solution and at the end (last line of text) the solution, which will probably work for the first tutorial, too.
I have tried again using this tutorial https://www.ics.com/blog/configuring-qt-creator-raspberry-pi
So I have used Qt 5.7.0 in my current try. Because this caused errors during compile of some webengine stuff, i only compiled qtbase and qtmultimedia (using make module-qtbase and make module-qtmultimedia). Also you should use make install from the according sub directories.
However after getting that solution to work, I got the same error message from the first tutorial
PulseAudioService: pa_context_connect() failed
ps. could you also post the result of 'cat /var/log/syslog | grep pulseaudio' – ovangle Nov 17 '11 at 9:51
In the log I found the following error:
org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
Googling after that error led me here: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=148395
And there I found this answer:
by spl23 » Mon May 16, 2016 9:11 pm
Officially, PulseAudio requires X to be running - a standard install of PulseAudio launches the pulseaudio daemon only when the desktop is launched.
If you want to use Pulse from a command-line without launching the desktop, you will need to start the daemon manually before you attempt to connect a Bluetooth device (type "pulseaudio -D" at the CLI prompt).
Using the command pulseaudio -D before starting my application solved the issue and now the sound is working.
I have tried your source code. I am having waveshare 10" screen with raspberry pi. Which runs a kiosk qt application. When I touch on screen it returns me the following logs. here is the link for product http://www.waveshare.com/wiki/10.1inch_HDMI_LCD
@BruceNaylor Hmm that's interesting! I posted on the C++ Gurus forum and a couple guys there suggested I use the MinGW that gets installed with QT Creator (when you select that option) and that actually fixed my issue with registry keys. I was going to give cross compiling another try on Windows, maybe your fudges will fix some other issues I've into. I appreciate the suggestions!
An idea should be to follow a tutorial from Qt official site, then import an example and use it, look the code, learn from there.
After migrate to Qt5, and after follow the tutorial for read video, after look at the example, you should be able to construct a little application for just read video with QMultimedia. (don't forget to incule multimdeiawidgets in the pro file also...).
there is also some example on youtube you can trust and follow for that.
After, do more than just read/record a simple video will ask more implication and maybe will be limited with just Qt without plugins.
But just for read video, you doesn't need phonon at all. Do it simple and easy first.
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.