QtBase 6.5.2: Wrong private header locations

  • Open
  • quality assurance status badge
Details
2 participants
  • Daniel Ziltener
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Daniel Ziltener
Severity
normal
D
D
Daniel Ziltener wrote on 27 Mar 11:59 +0100
(address . bug-guix@gnu.org)
0104d8bf-0215-4b2d-3319-9ffcbd5936af@lyrion.ch
The private header files of QtBase (and probably other Qt packages as
well) are placed in the wrong location. In my case, I am trying to use
qmetaobjectbuilder_p.h. The path for it is
/gnu/store/zywk3i6r200qd0w0fjizg3m5nwpkkzjs-profile/include/qt6/QtCore/6.5.2/QtCore/private/qmetaobjectbuilder_p.h
(expected would be
/gnu/store/zywk3i6r200qd0w0fjizg3m5nwpkkzjs-profile/include/qt6/QtCore/private/qmetaobjectbuilder_p.h),
which leads to issues when compiling, because qmetaobjectbuilder_p.h
contains an "#include <QtCore/private/qglobal_p.h>", which can then not
be found. It also means I cannot use any of the provided include path
env variables like C_INCLUDE_PATH.
M
M
Maxim Cournoyer wrote on 28 Mar 19:24 +0100
(name . Daniel Ziltener via Bug reports for GNU Guix)(address . bug-guix@gnu.org)
87il16i59a.fsf@gmail.com
Hi Daniel,

Daniel Ziltener via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

Toggle quote (11 lines)
> The private header files of QtBase (and probably other Qt packages as
> well) are placed in the wrong location. In my case, I am trying to use
> qmetaobjectbuilder_p.h. The path for it is
> /gnu/store/zywk3i6r200qd0w0fjizg3m5nwpkkzjs-profile/include/qt6/QtCore/6.5.2/QtCore/private/qmetaobjectbuilder_p.h
> (expected would be
> /gnu/store/zywk3i6r200qd0w0fjizg3m5nwpkkzjs-profile/include/qt6/QtCore/private/qmetaobjectbuilder_p.h),
> which leads to issues when compiling, because qmetaobjectbuilder_p.h
> contains an "#include <QtCore/private/qglobal_p.h>", which can then
> not be found. It also means I cannot use any of the provided include
> path env variables like C_INCLUDE_PATH.

If you have the chance, could you try on the qt-team branch? It has a
fresh Qt 6.6.2 version; perhaps something got fixed.

--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 70026@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70026
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch