Installing Qt5.10 on Raspbian
-
Hello,
i am experiencing some problems while using the./configurecommand. The whole command is:./configure -opensource -confirm-license -gui -widgets -dbus-linked -opengl es2 -pulseaudio -alsa -gstreamer -device linux-rasp-pi3-g++ -device-option CROSS_COMPILE=/usr/bin/ -vThe error is:
Note: Also available for Linux: linux-clang linux-icc Note: Disabling X11 Accessibility Bridge: D-Bus or AT-SPI is missing. ERROR: Feature 'dbus-linked' was enabled, but the pre-condition 'features.dbus && libs.dbus' failed. ERROR: Feature 'gstreamer' was enabled, but the pre-condition 'features.gstreamer_1_0 || features.gstreamer_0_10' failed. ERROR: Feature 'pulseaudio' was enabled, but the pre-condition 'libs.pulseaudio' failed.I feel like i already installed every repository on earth that matches with dbus gstreamer and pulseaudio and has a -dev at the end. Thats why i have really no idea how to solve this problem. Is maybe Qt4 easier to install or something?
Greets,
Xeno
-
Hello,
i am experiencing some problems while using the./configurecommand. The whole command is:./configure -opensource -confirm-license -gui -widgets -dbus-linked -opengl es2 -pulseaudio -alsa -gstreamer -device linux-rasp-pi3-g++ -device-option CROSS_COMPILE=/usr/bin/ -vThe error is:
Note: Also available for Linux: linux-clang linux-icc Note: Disabling X11 Accessibility Bridge: D-Bus or AT-SPI is missing. ERROR: Feature 'dbus-linked' was enabled, but the pre-condition 'features.dbus && libs.dbus' failed. ERROR: Feature 'gstreamer' was enabled, but the pre-condition 'features.gstreamer_1_0 || features.gstreamer_0_10' failed. ERROR: Feature 'pulseaudio' was enabled, but the pre-condition 'libs.pulseaudio' failed.I feel like i already installed every repository on earth that matches with dbus gstreamer and pulseaudio and has a -dev at the end. Thats why i have really no idea how to solve this problem. Is maybe Qt4 easier to install or something?
Greets,
Xeno
@Xenoshell
Although I cannot help you, I believe you are still doing this in order to sort out your "QCameranot working under Pi", aren't you? I am very sad to see that it is taking you anything like as long as this :( But you are persistent! -
@Xenoshell
Although I cannot help you, I believe you are still doing this in order to sort out your "QCameranot working under Pi", aren't you? I am very sad to see that it is taking you anything like as long as this :( But you are persistent! -
@JonB yeah well i am not giving up. I am just trying some stuff.. maybe i will also use something different then qt
@Xenoshell
Yeah, good for you, but I feel your pain!What about some alternative shortcuts to try to get at your problem:
-
The whole thing may not work because of something to do with your camera model!? That would be most frustrating! Can you borrow some completely different webcam from someone and see if it behaves any better?
-
Can you find some piece of non-Qt C++ code somewhere which shows how to address a webcam under Linux and try it? I have no idea whether that would be small code or what.
Else, what about starting (yet another) fresh post? I'm thinking of something like:
Calling all Qt experts. This includes sgaist, jsulm, aha_..., ravenworx... [and whatever "experts" you see around here; put a "@" in front of their names so they get notified].
I apologise for having to write a post like this. But I have had a problem and been working on it for over a month now and getting more & more stuck.
My basic original problem is any access to
QCameraunder Linux/Pi is hanging/crashing, as described in <this original post>.Since then I have tried all sorts of stuff, as per posts <...>. But I am getting nowhere.
Would some expert be really so kind as to review these posts to see where I'm at. I'm looking for a clue as to why a very simple
QCameracall could "hang" like this? (It seems to hang without even getting as far as accessing the actual camera, I'm not sure.)Could someone give me some indication, from the Qt source code, as to where this could possibly be happening. What do I need to do now to get anywhere further at all? What can I try, what approach should I take?
I know you guys are busy, and support here is voluntary, but I'd really be so grateful if someone could stick with this thread and help me out, because otherwise I'm getting nowhere. I like Qt but I'm on the verge of giving up, which would be such a shame, and I'm sure you wouldn't wish me to have to do that.. :)
-
-
@Xenoshell
Yeah, good for you, but I feel your pain!What about some alternative shortcuts to try to get at your problem:
-
The whole thing may not work because of something to do with your camera model!? That would be most frustrating! Can you borrow some completely different webcam from someone and see if it behaves any better?
-
Can you find some piece of non-Qt C++ code somewhere which shows how to address a webcam under Linux and try it? I have no idea whether that would be small code or what.
Else, what about starting (yet another) fresh post? I'm thinking of something like:
Calling all Qt experts. This includes sgaist, jsulm, aha_..., ravenworx... [and whatever "experts" you see around here; put a "@" in front of their names so they get notified].
I apologise for having to write a post like this. But I have had a problem and been working on it for over a month now and getting more & more stuck.
My basic original problem is any access to
QCameraunder Linux/Pi is hanging/crashing, as described in <this original post>.Since then I have tried all sorts of stuff, as per posts <...>. But I am getting nowhere.
Would some expert be really so kind as to review these posts to see where I'm at. I'm looking for a clue as to why a very simple
QCameracall could "hang" like this? (It seems to hang without even getting as far as accessing the actual camera, I'm not sure.)Could someone give me some indication, from the Qt source code, as to where this could possibly be happening. What do I need to do now to get anywhere further at all? What can I try, what approach should I take?
I know you guys are busy, and support here is voluntary, but I'd really be so grateful if someone could stick with this thread and help me out, because otherwise I'm getting nowhere. I like Qt but I'm on the verge of giving up, which would be such a shame, and I'm sure you wouldn't wish me to have to do that.. :)
@JonB You know all those problems existed on Ubuntu mate. Since i didnt advance further after recieving no answers on my posts anymore i just decided to wipe the microSD card and start new on raspbian and now i am encountering problems even on installing qt5...
-
-
Hello,
i am experiencing some problems while using the./configurecommand. The whole command is:./configure -opensource -confirm-license -gui -widgets -dbus-linked -opengl es2 -pulseaudio -alsa -gstreamer -device linux-rasp-pi3-g++ -device-option CROSS_COMPILE=/usr/bin/ -vThe error is:
Note: Also available for Linux: linux-clang linux-icc Note: Disabling X11 Accessibility Bridge: D-Bus or AT-SPI is missing. ERROR: Feature 'dbus-linked' was enabled, but the pre-condition 'features.dbus && libs.dbus' failed. ERROR: Feature 'gstreamer' was enabled, but the pre-condition 'features.gstreamer_1_0 || features.gstreamer_0_10' failed. ERROR: Feature 'pulseaudio' was enabled, but the pre-condition 'libs.pulseaudio' failed.I feel like i already installed every repository on earth that matches with dbus gstreamer and pulseaudio and has a -dev at the end. Thats why i have really no idea how to solve this problem. Is maybe Qt4 easier to install or something?
Greets,
Xeno
@Xenoshell What's the full output from the configure? Or more specifically, what is the output from the tests that are built to test for gstreamer and dbus?
That will help shed some light on your install issue. It sounds like even though you installed all the *-dev packages Qt isn't finding them properly.
