From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11401] Impossible do build a qt program using kf5-networkmanager-qt
Date: Tue, 16 Oct 2018 16:31:05 +0000 [thread overview]
Message-ID: <bug-11401-163-UYOlcapQJh@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11401-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11401
--- Comment #4 from Pierre Ducroquet <pinaraf@pinaraf.info> ---
I will try to investigate tomorrow. I did not test with a QMake project, only
with a CMake one. Could you try converting from qmake to cmake ?
The CMakeLists.txt would look like this:
cmake_minimum_required(VERSION 3.0)
find_package(Qt5 REQUIRED COMPONENTS Gui DBus)
find_package(KF5NetworkManagerQt REQUIRED)
add_executable(qt-network-manager main.cpp)
target_link_libraries(qt-network-manager Qt5::Gui Qt5::DBus
KF5::NetworkManagerQt)
This would help confirm the issue lies in the QMake files.
Thank you very much for your report
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-10-16 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 12:31 [Buildroot] [Bug 11401] New: Impossible do build a qt program using kf5-networkmanager-qt bugzilla at busybox.net
2018-10-16 13:21 ` [Buildroot] [Bug 11401] " bugzilla at busybox.net
2018-10-16 13:26 ` bugzilla at busybox.net
2018-10-16 13:29 ` bugzilla at busybox.net
2018-10-16 16:31 ` bugzilla at busybox.net [this message]
2018-10-17 6:15 ` bugzilla at busybox.net
2018-10-17 6:37 ` bugzilla at busybox.net
2018-10-17 6:39 ` bugzilla at busybox.net
2018-10-17 6:39 ` [Buildroot] [Bug 11401] Impossible do build a qt program using kf5-networkmanager-qt with qmake bugzilla at busybox.net
2018-10-17 6:57 ` bugzilla at busybox.net
2018-10-17 7:04 ` bugzilla at busybox.net
2018-10-17 7:11 ` bugzilla at busybox.net
2018-10-17 16:11 ` bugzilla at busybox.net
2024-06-15 14:48 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11401-163-UYOlcapQJh@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox