github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #402] Build error: QDialog #317

New issue

Closed

opened 2026-05-05 06:01:45 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 06:01:45 -06:00

Owner

Originally created by @OneUp5hroom on GitHub (Aug 18, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/402

Hey I am new to Raspbian + Linux in general so this could very well be user error.
But when following the steps for setup from the wiki I get the following error on build.

Appreciate the help!

Operating Systems

Server: Windows10:1809
Client: Linux raspberrypi 4.19.58-v7+ #1245 SMP Fri Jul 12 17:25:51 BST 2019 armv7l GNU/Linux

Barrier Version

Current

Steps to reproduce bug

On build from new pull from repo, fresh OS build... etc.
Run Linux Procedure for building (from Wiki)

When running "sudo make install" the following error is produced.
[ 78%] Building CXX object src/gui/CMakeFiles/barrier.dir/src/AboutDialog.cpp.o
In file included from /home/pi/barrier/build/barrier/src/gui/src/AboutDialog.cpp:19:
/home/pi/barrier/build/barrier/src/gui/src/AboutDialog.h:23:10: fatal error: QDialog: No such file or directory
#include
^~~~~~~~~
compilation terminated.
make[2]: *** [src/gui/CMakeFiles/barrier.dir/build.make:63: src/gui/CMakeFiles/barrier.dir/src/AboutDialog.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:917: src/gui/CMakeFiles/barrier.dir/all] Error 2
make: *** [Makefile:152: all] Error 2

Originally created by @OneUp5hroom on GitHub (Aug 18, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/402 Hey I am new to Raspbian + Linux in general so this could very well be user error. But when following the steps for setup from the wiki I get the following error on build. Appreciate the help! ### Operating Systems ### Server: Windows10:1809 Client: Linux raspberrypi 4.19.58-v7+ #1245 SMP Fri Jul 12 17:25:51 BST 2019 armv7l GNU/Linux ### Barrier Version ### Current ### Steps to reproduce bug ### On build from new pull from repo, fresh OS build... etc. Run Linux Procedure for building (from Wiki) When running "sudo make install" the following error is produced. [ 78%] Building CXX object src/gui/CMakeFiles/barrier.dir/src/AboutDialog.cpp.o In file included from /home/pi/barrier/build/barrier/src/gui/src/AboutDialog.cpp:19: /home/pi/barrier/build/barrier/src/gui/src/AboutDialog.h:23:10: fatal error: QDialog: No such file or directory #include <QDialog> ^~~~~~~~~ compilation terminated. make[2]: *** [src/gui/CMakeFiles/barrier.dir/build.make:63: src/gui/CMakeFiles/barrier.dir/src/AboutDialog.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:917: src/gui/CMakeFiles/barrier.dir/all] Error 2 make: *** [Makefile:152: all] Error 2

gitea-mirror

2026-05-05 06:01:45 -06:00

closed this issue
added the
bug

build-infra

help wanted

linux
labels

gitea-mirror commented

2026-05-05 06:01:54 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 18, 2019):

I don't have a raspberry pi running raspbian at the moment, so I can't reproduce at the moment.

@AdrianKoshka commented on GitHub (Aug 18, 2019): I don't have a raspberry pi running raspbian at the moment, so I can't reproduce at the moment.

gitea-mirror commented

2026-05-05 06:01:55 -06:00

Author

Owner

@shymega commented on GitHub (Aug 18, 2019):

Not sure why you're building from source. There's a Flatpak for 32/64-bit ARM - you could try that for now.

Did you install Qt5 libs? You'll need the Qt5 Widgets library., Let me know what the output is, if at all, you get from this command: pkg-config --libs Qt5Widgets. Case is sensitive.

@shymega commented on GitHub (Aug 18, 2019): Not sure why you're building from source. There's a Flatpak for 32/64-bit ARM - you could try that for now. Did you install Qt5 libs? You'll need the Qt5 Widgets library., Let me know what the output is, if at all, you get from this command: `pkg-config --libs Qt5Widgets`. Case is sensitive.

gitea-mirror commented

2026-05-05 06:01:58 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 18, 2019):

The flatpak: https://flathub.org/apps/details/com.github.debauchee.barrier

@AdrianKoshka commented on GitHub (Aug 18, 2019): The flatpak: https://flathub.org/apps/details/com.github.debauchee.barrier

gitea-mirror commented

2026-05-05 06:02:00 -06:00

Author

Owner

@OneUp5hroom commented on GitHub (Aug 29, 2019):

Hey sorry for the delay, the Flatpak does work on my raspberryPI, but building from source does not.

For curiosity sake, I am going to try the Qt5Widgets to see if that fixes the building from source issue. But if not at least it is functioning now using the Flatpak.

@OneUp5hroom commented on GitHub (Aug 29, 2019): Hey sorry for the delay, the Flatpak does work on my raspberryPI, but building from source does not. For curiosity sake, I am going to try the Qt5Widgets to see if that fixes the building from source issue. But if not at least it is functioning now using the Flatpak.

gitea-mirror commented

2026-05-05 06:02:02 -06:00

Author

Owner

@OneUp5hroom commented on GitHub (Aug 29, 2019):

@shymega
Looks like I do not have the Qt5 libs installed, do you know where I can get them or what the apt package for them is called? I tried Qt5Widgets but it was not found.

output from pkg-config --libs Qt5Widgets is:

Package Qt5Widgets was not found in the pkg-config search path. Perhaps you should add the directory containing 'Qt5Widgets.pc' to the PKG_CONFIG_PATH environment variable no package 'Qt5Widgets' found

@OneUp5hroom commented on GitHub (Aug 29, 2019): @shymega Looks like I do not have the Qt5 libs installed, do you know where I can get them or what the apt package for them is called? I tried Qt5Widgets but it was not found. output from `pkg-config --libs Qt5Widgets` is: > `Package Qt5Widgets was not found in the pkg-config search path. Perhaps you should add the directory containing 'Qt5Widgets.pc' to the PKG_CONFIG_PATH environment variable no package 'Qt5Widgets' found`

gitea-mirror commented

2026-05-05 06:02:04 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 29, 2019):

@OneUp5hroom this should help: https://github.com/debauchee/barrier/wiki/Building-on-Linux#ubuntudebianraspbian-build-from-source

@AdrianKoshka commented on GitHub (Aug 29, 2019): @OneUp5hroom this should help: https://github.com/debauchee/barrier/wiki/Building-on-Linux#ubuntudebianraspbian-build-from-source

gitea-mirror commented

2026-05-05 06:02:07 -06:00

Author

Owner

@OneUp5hroom commented on GitHub (Aug 29, 2019):

@AdrianKoshka & @shymega
Thank you for being kind to a Linux noob :)

I must have fat fingered something at some point because I was following those instructions but it was not working. New day (and a lot less frustrated with my lack of Linux knowledge)... and it worked just fine.

The reason I was preferring to build it myself instead of using the flatpak was because (at least for what I can tell) the flatpak does not install/build the barrierc portion and I wanted to be able to have it launch and connect on startup so I don't have to plug in a mouse, launch it and then get going on every reboot.

Seriously appreciate the help!

@OneUp5hroom commented on GitHub (Aug 29, 2019): @AdrianKoshka & @shymega Thank you for being kind to a Linux noob :) I must have fat fingered something at some point because I was following those instructions but it was not working. New day (and a lot less frustrated with my lack of Linux knowledge)... and it worked just fine. The reason I was preferring to build it myself instead of using the flatpak was because (at least for what I can tell) the flatpak does not install/build the barrierc portion and I wanted to be able to have it launch and connect on startup so I don't have to plug in a mouse, launch it and then get going on every reboot. Seriously appreciate the help! - 1up

gitea-mirror commented

2026-05-05 06:02:09 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 29, 2019):

The flatpak does build the barriers and barrierc parts, but doesn't directly expose them, and it's generally more of a pain to use them from the flatpak. The flatpak is geared more towards GUI users.

@AdrianKoshka commented on GitHub (Aug 29, 2019): The flatpak does build the `barriers` and `barrierc` parts, but doesn't directly expose them, and it's generally more of a pain to use them from the flatpak. The flatpak is geared more towards GUI users.

gitea-mirror commented

2026-05-05 06:02:12 -06:00

Author

Owner

@shymega commented on GitHub (Aug 31, 2019):

@OneUp5hroom You're more than welcome. I'm glad you opened this issue, because I've now been able to add checks to the build system for the Qt 5 libraries, which it didn't have before; I hadn't considered it.

Anyway, now the checks have been added, similar issues to yourself, where it doesn't check for the required Qt 5 libraries, will be much easier to solve! 👍

@shymega commented on GitHub (Aug 31, 2019): @OneUp5hroom You're more than welcome. I'm glad you opened this issue, because I've now been able to add checks to the build system for the Qt 5 libraries, which it didn't have before; I hadn't considered it. Anyway, now the checks have been added, similar issues to yourself, where it doesn't check for the required Qt 5 libraries, will be much easier to solve! 👍

No labels

Rows
Columns