From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12906] New: qt PrefixPath is wrong on 2020.05-rc1
Date: Sat, 16 May 2020 10:39:13 +0000 [thread overview]
Message-ID: <bug-12906-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12906
Bug ID: 12906
Summary: qt PrefixPath is wrong on 2020.05-rc1
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jharjuma at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The PrefixPath is /. It should be /usr. For example QML modules are under
/usr/qml not /qml.
Head of 'qtdiag --no-gl':
Qt 5.14.2 (arm-little_endian-ilp32-eabi-hardfloat shared (dynamic) release
build; by GCC 7.5.0) on "eglfs"
OS: Buildroot 2020.05-rc1 [linux version 5.4.3]
Architecture: arm; features:
Environment:
Features: QT_NO_EXCEPTIONS
Library info:
PrefixPath: /
DocumentationPath: /doc
HeadersPath: /include/qt5
LibrariesPath: /lib
LibraryExecutablesPath: /libexec
BinariesPath: /bin
PluginsPath: /lib/qt/plugins
ImportsPath: /imports
Qml2ImportsPath: /qml
ArchDataPath: /
DataPath: /
TranslationsPath: /translations
ExamplesPath: /lib/qt/examples
TestsPath: /tests
SettingsPath: /etc/xdg
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-05-16 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 10:39 bugzilla at busybox.net [this message]
2020-05-16 12:07 ` [Buildroot] [Bug 12906] qt PrefixPath is wrong on 2020.05-rc1 bugzilla at busybox.net
2020-05-16 15:50 ` bugzilla at busybox.net
2020-05-16 16:12 ` bugzilla at busybox.net
2020-05-16 16:38 ` bugzilla at busybox.net
2020-05-16 20:41 ` bugzilla at busybox.net
2020-05-17 7:25 ` bugzilla at busybox.net
2020-05-17 7:41 ` bugzilla at busybox.net
2020-05-17 10:36 ` bugzilla at busybox.net
2020-05-17 19:27 ` bugzilla at busybox.net
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-12906-163@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.